In relation to below question : https://answers.atlassian.com/questions/83519/updating-an-issue-s-status-via-the-rest-api .
I have below question on the same. i.e
While doing transition using rest api mentioned in the link will the ID to be transformed be uniform across different projects under JIRA. i.e. For example will mappings like below provided be same for all JIRA Issues across all projects.
id 141 for Closed , id 131 for Accepted like that?.
Please share your thoughts on the same. Thanks
The id of a transition is part of a workflow.
If your issues are configured to use the same workflow, then of course the transition will have the same ID, because it's the same workflow. If they're using different workflows, then no. (If you've copied workflows, similar transitions might have the same id, but you can not assume that - two workflows are likely to have different transition ids, even if they look pretty much the same)
Thanks for your help in understanding transition. One more clarification related to that I would like to inquire. Please share your thoughts on the same.
My Requirement is to update a Jira Issue (different project can exist) to the "Close" status via Rest API. i.e I want to implicitly change it's status to that of "Close" so that portal user will get to know that it is no longer needed to be worked up on.
But what I infer from your answer is that for each project they can define their own workflows and chances are there where they haven't configured a workflow equivalent to that of "Close".
Is my understanding correct? If so, is there a way we can know the transitions final workflow so that if "close" is not present I can set to that final workflow status.
Please let me know if my question is ambiguous to you. Thanks in advance.
Correct. You will need to read the workflow yourself to work out what the end states might be.
It's perfectly possible for a human to write a workflow that looks like "Badger -> Mushroom -> Snake". This example shows you a number of problems:
In short - you will need to read your workflows. You have to understand what you're coding for.
Over the next several weeks we'll be sharing some of our Getting Started guides here in the community. Throughout this series of posts, we'd love to hear from customers and non-customers ab...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs