Hello
I have a web response that validates correctly
The payload returned is:
{ "access_token": "<snip>", "refresh_token": "<snip>", "scope": "useraccount", "token_type": "Bearer", "expires_in": 1799 }
I do have "Delay execution of subsequent rule actions until we've received a response for this web request" checked
I have another send web request that needs to use the access_token in its Authorization header value like so:
The full value is Bearer {{webResponse.body.access_token}}
Thus far I have not been able to successfully build this string :( and validating the second request returns authorization failed. I have tested copy/pasting the access_token into the header and it does work
UPDATE ***
I believe the token is being passed at this point (after testing) however now it seems like the Web request URL isn't accepting the custom field value
https://some/api/endpoint?number={{issue.customfield_123456.value}}
Any help is appreciated
Looks like I've been able to answer this myself
The custom field value is text so it looks like in both cases all I had to do was remove the .value
{{issue.customfield_123456}} worked.
Can I know from where this value is retrieved : {{issue.customfield_123456}} ?
Isn't adding Bearer followed by {{webResponse.body.access_token}} working still ?
Because I need same value to insert in my headers section for another webrequest to trigger, please help. Even adding {{webResponse}} in audit log also not helping/displaying any value.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's working, smart values are working. What I was missing is didn't change any value on the field value of Jira story as we created automation rule for webhook for story point estimate.
As soon as I change value on the field "story point estimate" from existing value to the other, then my automation rule invoked webhook with authorization.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.