It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Why do I see transition names before the status name in the status dropdown?

Hi,

I have been configuring a new workflow starting from scratch.

I am used to see the dropdown to make a status transition in the new issue view looking something like this:

Screenshot 2019-09-10 at 23.57.34.png

however, with the newly defined workflow it looks like this:

Screenshot 2019-09-10 at 23.58.59.png

So it shows the transition name before the -> and the status name after it. I would like to know how I can get this to look the one above, being only displaying the status names.

I have tried many things, from changing the transition names to match the status names (what you see above) to playing around with transition properties like jira.i18n.title (which are for as far as I can tell rather poorly documented), no success. Also looking up the community for similar cases did not bring me very far.

Any help is greatly appreciated, thanks in advance!

2 answers

1 accepted

0 votes
Answer accepted

As it turns out, this is normal behaviour once you start creating a workflow that limits the possible transitions between statuses, as in it is not designed to allow all statuses to transition into any other status.

This is the answer I got from the Atlassian Support:

Thanks for reaching out to Atlassian Support! Examining your question, the reason you see a transition name preceding the Status name, is because your "Workflow" has a Transition flow across each status with an Incoming and outgoing transition link. Furthermore, the reason why the Transition to the "Open" Status has the 'Transition to' name is because it has an "Allow all statuses to transition to this one" configured to the Status.

In order to achieve the "without transition names" image illustration, you will need to create a workflow that doesn't have a "Transition Flow" between each Statuses. i.e. Having an Incoming and outgoing transition link between Statuses.

Then Configure each Statuses to have the "Allow all statuses to transition to this one" configured to the Status. That way you will only see the Status name without the Transition name. See more details on Working with workflows for more insights.

0 votes
Jack Community Leader Sep 10, 2019

i think it is simply a UI change that was made to 'improve' the clarity by showing the transition action and the resulting status. In the older issue view the buttons at the top were the Transition names and the status was shown separately. in the new issue view they have combined these into one and I suspect folks that liked the old view missed the transitions. All in all, I personally like this part of the new issue view while there are things I definitely have not warmed up to just yet.

Hi Jack,

thank you for your answer.

I'm not sure it's a difference between the new and the old UI, the two screenshots you see are actually both taken from the new view.

What is changing the behaviour is really which workflow I am using for a given issue type: I see the difference even between issues with different workflow that belong to the same project.

The problem is that I cannot tell what I did in creating my workflow that results in the different UI behaviour...

Jack Community Leader Sep 11, 2019

Understood. I was just using the old issue view as a reference about why the new view may have changed. Given the frequent changes in cloud im unsure what the proper answer is TBH. You might reach out to Atlassian Support for an official answer. I don’t think it is associated with any workflow config but certainly could be mistaken here.

Like filippo likes this

@Jack FYI, see the answer from Atlassian Support on the matter.

Jack Community Leader Sep 16, 2019

Ah I see. Makes perfect sense. Thanks for sharing. 

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

365 views 1 3
Join discussion

Community Events

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

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you