If you have the issue key, then you can use that to get the project and issue type, then use the calls in that doc to workout which workflow it is, then fetch the properties of the transition from that.
However, I question why that information is of any use for you at an issue level. What are you using it for?
Please, read the comments again.
You can't do issue -> transition properties in one go because it is utterly useless, and hence not worth coding for.
Could you please explain what you are actually trying to do? Of what possible use is the call you are asking for?
I would like to use the transitions properties to map Jira status with the status of the external system. It’s a task of integration. Integration with another system. The external system would like to do ONE api call: all possible transitions WITH properties starting by issue key. One call.
Thanks for the explanation, but it raises more questions and suggests more problems than I expected. The core of this is probably
"use the transitions properties to map Jira status with the status of the external system"
This makes no sense to me.
A transition in Jira is not a status. It is a link between steps (status) in a workflow. The properties of a transition have no relationship to status.
If you are trying to map Jira-Status to External-Status, why are you looking at transitions? Why are you not looking at the Jira Status?
I’m looking for transitions because I can use 1 API call that retrieves all the possible transitions starting by the issue key. 1 API call. One. Into that API call I can map the status of the external system to jira transition(link). It is a workaround. Do you know another way to reach the goal? The goal for the external system is the following one: starting by the issue key and its target status GET the transition ID to be used for the issue status change in ONE call. The external system wants to read in the response of a single api call the transition ID and the reference to ITS status. ITS status = the status into the external system. For example into the external system the status is called “annullato” and into Jira the status is called “annullato2”. Do you have other ideas? It is a workaround for the integration between the two systems.
Most of that wall of text makes no sense to me.
The one bit that does make sense right is that you want to have a 1:1 relationship between a Jira issue's status and your external system's item's status.
The mapping between Jira-Status and External-Status should be 1:1 and I really cannot discern why you are looking at transistions to do that, let alone transition properties.
My "workaround" for this is for you to tell your external system that "status X in Jira means status Y for you".
Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event