The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello!
I have a jira automation for issues, which uses web request action. I'm trying to send HTTP request to my endpoint with web request body in jira automation format, which looks like this:
{
"self": "https://sportsru.atlassian.net/rest/api/2/92165",
"id": 92165,
"key": "SF-2876",
// ...
}
The problem that is url provided in self are not valid: it's missing part about issue. The valid one should look like this:
https://sportsru.atlassian.net/rest/api/2/issue/92165
However, when I'm validating request via automation editor, I receiving payload with correct url.
Is this a bug or am I doing something wrong?
Hi Anton,
You seem to be trying to call the Jira REST API from an automation rule.
If that is correct, please take a look at this how-to article for calling the REST API from a rule:
And, please confirm you are calling the REST API function with the correct parameters/URL:
https://docs.atlassian.com/software/jira/docs/api/REST/1000.824.0/#api/2/issue-getIssue
Kind regards,
Bill
Hello Bill, thanks for the answer!
I'm sorry, seems like I inaccurately described the problem, what you are recommending to me is not quite what I'm looking for.
What I have Is Automation action called "Web request", which is making a HTTP request to my endpoint with issue data in Jira automation format as payload. Then, in my endpoint I'm expecting that received payload will contain a field called self, which should contain Jira REST API url to the issue. The problem is that provided url in self field is incorrect and points to the 404 page instead of issue.
In other words, I expect this url in payload:
https://sportsru.atlassian.net/rest/api/2/issue/92165
but instead I receiving this:
https://sportsru.atlassian.net/rest/api/2/92165
The issue part of the path is missing.
Hope this explanation will make my problem more clear!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for clarifying, Anton.
I suggest trying to diagnose this from one end to the other...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.