search

sbonnick / node-red-nodes

Apache License 2.0
1 stars 0 forks source link

only 1 JQL query can be made without redeploying in NodeRED #1

Closed symon-skelly closed 3 years ago

symon-skelly commented 3 years ago

With a functioning JIRA Connection, if a function block preceding the JQL block assigns the msg.query a string that contains an issueKey that exists ("issueKey = QAC-37") and the subflow is activated, the JQL block responds correctly, however upon activating the flow again with any other issueKey, the previous issueKey is used for the 2nd activated flow, the response msg.payload is identical to the first activated flow, even though the msg.query is different.

redeploying the subflow with any change (even just moving a block from one position to another) will cause the next JQL query to respond with the correct data, but any subsequent JQL queries will have the same issue until redeploying again.

first activation (working)

second activation (broken)

sbonnick commented 3 years ago

Taking a look at it now.

sbonnick commented 3 years ago

This should be fixed now in release: node-red-contrib-jira-streams@0.1.15

symon-skelly commented 3 years ago

Hey @sbonnick, Thank you for fixing this, however we were forced to use a different plugin because of this issue and have since completed the project. I'm sure that someone else in the future will appreciate the work you put in. :)