-
Bug
-
Resolution: Fixed
-
Low
-
None
-
Severity 3 - Minor
Issue Summary
Recently added an option to hide headers in 'Send web request' component in Jira Automation.
https://jira.atlassian.com/browse/JSWCLOUD-22729
Unfortunately, this doesn't work right for any nested 'Send web request' component, e.g. under If...Else conditions, because any time the rule is edited those hidden headers will get overwritten with stars: "******" replacing the original value.
It doesn't do that for non-nested 'Send web request' components.
Steps to Reproduce
- Create a automation rule with web request and use the nested if else block
- Run the rule manually from any of the tickets
#The payloads get sent to the endpoint with 'x-api-key' headers having correct values
#Now edit the Automation Rule with any change which requires saving and publishing it again
#Run the rule again and check the incoming payloads: the one where the component is nested will have the value of 'x-api-key' replaced with "*" instead of the value. The other one will be correct.
Expected Results
Hidden header values should never be replaced, otherwise it makes any edits of the rules very problematic and time consuming.
Actual Results
value of 'x-api-key' replaced with "*" instead of the value
Workaround
Currently there is no known workaround for this behavior.
- mentioned in
-
Page Failed to load
[AUTO-192] Broken 'Hidden' header option for nested 'Send web request' component in Jira Automation
| Remote Link | New: This issue links to "Page (Confluence)" [ 818199 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Short Term Backlog [ 12074 ] | New: Closed [ 6 ] |
| Component/s | Original: Automation [ 68402 ] | |
| Component/s | New: Action - Send web request [ 71596 ] | |
| Key |
Original:
|
New:
|
| Support reference count | Original: 2 | |
| Project | Original: Jira Software Cloud [ 18511 ] | New: Automation [ 22610 ] |
| Support reference count | Original: 1 | New: 2 |
| Status | Original: Needs Triage [ 10030 ] | New: Short Term Backlog [ 12074 ] |
| Support reference count | New: 1 |
| Description |
Original:
h3. Issue Summary
Atlassian recently added an option to hide headers in 'Send web request' component in Jira Automation. https://jira.atlassian.com/browse/JSWCLOUD-22729 Unfortunately, this doesn't work right for any nested 'Send web request' component, e.g. under If...Else conditions, because any time the rule is edited those hidden headers will get overwritten with stars: "******" replacing the original value. It doesn't do that for non-nested 'Send web request' components. h3. Steps to Reproduce # Create a automation rule with web request and use the nested if else block # Run the rule manually from any of the tickets #The payloads get sent to the endpoint with 'x-api-key' headers having correct values #Now edit the Automation Rule with any change which requires saving and publishing it again #Run the rule again and check the incoming payloads: the one where the component is nested will have the value of 'x-api-key' replaced with "*" instead of the value. The other one will be correct. h3. Expected Results Hidden header values should never be replaced, otherwise it makes any edits of the rules very problematic and time consuming. h3. Actual Results value of 'x-api-key' replaced with "*" instead of the value h3. Workaround Currently there is no known workaround for this behavior. |
New:
h3. Issue Summary
Recently added an option to hide headers in 'Send web request' component in Jira Automation. https://jira.atlassian.com/browse/JSWCLOUD-22729 Unfortunately, this doesn't work right for any nested 'Send web request' component, e.g. under If...Else conditions, because any time the rule is edited those hidden headers will get overwritten with stars: "******" replacing the original value. It doesn't do that for non-nested 'Send web request' components. h3. Steps to Reproduce # Create a automation rule with web request and use the nested if else block # Run the rule manually from any of the tickets #The payloads get sent to the endpoint with 'x-api-key' headers having correct values #Now edit the Automation Rule with any change which requires saving and publishing it again #Run the rule again and check the incoming payloads: the one where the component is nested will have the value of 'x-api-key' replaced with "*" instead of the value. The other one will be correct. h3. Expected Results Hidden header values should never be replaced, otherwise it makes any edits of the rules very problematic and time consuming. h3. Actual Results value of 'x-api-key' replaced with "*" instead of the value h3. Workaround Currently there is no known workaround for this behavior. |
| Priority | Original: Medium [ 3 ] | New: Low [ 4 ] |
| Attachment | Original: Screenshot 2022-11-03 at 4.53.28 PM.png [ 429725 ] |
| Attachment | Original: Screenshot 2022-11-03 at 4.53.58 PM.png [ 429726 ] |