Is it normal to have a workflow status with many IDs ?

[Fabio Maia]

I ran rest api comand to get all ID status. I ran the comand:  https://your-domain.atlassian.com/rest/api/3/status'.

For my surprise I found for the same status name "Em Andamento" more than 10 IDs. And it is not the statuscategory. I know there are many status whose statuscategory is "Em Andamento", but it is not the case.  

So, I would like to know whether it is normal or is a bug? When I saw the status on Jira, I only can see one status "Em Andamento".  Why internaly it has many?

[Fabio Maia · Accepted solution]

Thanks all of you for the answers. The situation was because next generation projects. I was confusing because I didnt know how to know whether the id status was for wich project. So, after the explanation and with some investigation I discovered that in JSON returned by the .../rest/api/3/status now it has a scope part, like in the example below.

{
"self":"[URL Jira instance]/rest/api/3/status/11507",
"description":"",
"iconUrl":"https://[URL Jira instance].atlassian.net/",
"name":"Concluído",
"untranslatedName":"Done",
"id":"11507",
"statusCategory":{
"self":"https://[URL Jira instance].atlassian.net/rest/api/3/statuscategory/3",
"id":3,
"key":"done",
"colorName":"green",
"name":"Itens concluídos"
},
      "scope":{
       "type":"PROJECT",
      "project":{
       "id":"14589"
        }
}
},

Whether the status belongs to a NEXT-GEN, so the JSON has the scope part with a list of IDPROJECTs which the id status belongs for. If the status belongs to a global scope we will not have the scope part. Like example below:

{
"self":"[URL Jira instance]/rest/api/3/status/11507",
"description":"",
"iconUrl":"https://[URL Jira instance].atlassian.net/",
"name":"Em produção",
"untranslatedName":"In production",
"id":"11000",
"statusCategory":{
"self":"https://[URL Jira instance].atlassian.net/rest/api/3/statuscategory/3",
"id":3,
"key":"done",
"colorName":"green",
"name":"Itens concluídos"
},

[Petter Gonçalves · Accepted solution]

Hello @Fabio Maia

Thank you for reaching out.

Just to give more context about the explanation provided by @Nic Brough -Adaptavist- 

You can indeed create multiple statuses with the same name for Jira Classic Projects, however, this behavior is not created by the application itself. In other words, you would need to explicitly create other statuses with the same name, otherwise, the same status (or new statuses using a different name) would be shared with your newly created projects. 

Since you mentioned that the duplicated statuses are not being displayed for you under Settings > Issues > Statuses, I believe the behavior above is not the one you are facing. Instead, I believe the creation of multiple Next-gen projects would be the root cause of your question.

Next-gen projects use a different architecture than Classic projects, creating unique entities for each project you have (Priorities, Statuses, etc) instead of using the same statuses across all projects. That causes new statuses with the same name to be created for each new next-gen project you have. Basically:

• In Next-gen projects -> Each project has its own statuses, usually with the same name
• In Classic Projects -> The statuses are usually shared between all the projects, although you can manually create duplicate ones.

Additionally, Next-gen statuses does not appear under Settings > Issues > Statuses, once they are not applied globally but only to their related project.

To know what is the ID related to the status in your Next-gen project, you can run a simple REST API search and check the status ID displayed in any issue of the Next-gen project:

https://yourdomain.atlassian.net/rest/api/3/search?jql=project=Nextgenprojectkey

To know the ID of the status related to your Classic projects, you can run the same REST API above or go directly to Settings > issues > Statuses > Click to edit the status and check the ID at the end of your browser URL.

Let us know if you still have any questions.

[Fabio Maia]

Hi, thanks untill now.

Yes, we have in the same Jira with both types of project - classic and nextGen. But

But, the Jira is the same and show me only one status. 

Even if I did it - _go directly to Settings > issues > Statuses > Click to edit the status and check the ID at the end of your browser URL - Jira would show just one ID, but Jira has many Ids in back end. 

It seems that there is another table that relate ID Status with a specific workflow. If doesn't, how could Jira to know what ID to get.  For example, I have found two issues from diferent projects - both classic projects - in the same status, but  when I took the data with - https://[URL]/rest/api/2/issue/[id issue]" I have found diferent ID in each.

My question is: Since that in my Jira instance I have many IDs for the same status, how does Jira choose the ID Status to put in records of the issue?

[Petter Gonçalves]

Hello @Fabio Maia

Please, allow me to clarify some details:

Even if I did it - _go directly to Settings > issues > Statuses > Click to edit the status and check the ID at the end of your browser URL - Jira would show just one ID, but Jira has many Ids in back end. 

Just I mentioned before, this is expected behavior. The global view of the statuses under Settings > issues > Statuses only display the status/ID related to Classic Projects. The statuses of Next-gen projects are related only to a single next-gen project, so it does not make sense to display it in that global view.

It seems that there is another table that relate ID Status with a specific workflow. If doesn't, how could Jira to know what ID to get.  For example, I have found two issues from diferent projects - both classic projects - in the same status, but  when I took the data with - https://[URL]/rest/api/2/issue/[id issue]" I have found diferent ID in each.

I must confess that I never experienced the behavior above for two Classic projects. If the statuses used in both projects have the same name, the same status ID should be displayed for both projects (Just tested the REST API call in two different projects):

That being said, can you double-check if the statuses have the exact same name and it was tested in two Classic projects? Also, doublecheck if these both statuses (With different IDs) are not displayed under Settings > issues > Statuses and that you are looking to the expanded status field ID in the REST API.

My question is: Since that in my Jira instance I have many IDs for the same status, how does Jira choose the ID Status to put in records of the issue?

Actually, I believe the correct statement is that you have many statuses with the same name. For classic projects, all the Statuses/IDs should be displayed under Settings > issues > Statuses. For next-gen, each project will have a different status id.

Please, provide us with some screenshots if you find a different behavior from the mentioned above, making sure you've hidden any sensitive information from them.

[Fabio Maia]

Really Thank you for the answers. 

For Sure, I will check again with your insights in mind.

[Nic Brough -Adaptavist- · Accepted solution]

A status is really not much more than a label - something to display to a human when an issue is on step X of a workflow.  In the database, they're not much more than a key (id) and the display name (plus translations)

Yes, you can now have many status with the same name.  This allows different worklows to be independent of each other while still using some of the same words for their status. 

[Fabio Maia]

Hi, 

Thanks for the answer until now.

Do you know which version of Jira Cloud it started?

And how can I know which of this IDs are used by the issue? 

It sounds weird, because if I got to Jira to manage the status, I can't see many status. I can see only one.

And if I use IDs to get issues with a specific status, have I to use all of this ids? How can I know which id status is used by each workflow?