nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why is there a transition button showing next to the status and how do we configure it?

Nathan Given_43rz48

We woke up today to the Jira UI being different. In the new UI on the right hand side, we used to see the current status and a dropdown that allowed us to transition the issue to the other available statuses.

Now we see one of the statuses that used to be in the drop down now show up next to the status:

I9F8l1X

How do we configure this so that we can either:

1) Turn this off so that all transitions show up after we cluck the dropdown button

2) Configure which transition shows up next to the current status?

I've already looked at the "opsbar-sequence" property on the various transitions... some have the property, most don't, and I can't find any relation between the opsbar-sequence and what I see in the UI.

I also have noticed that some of my transitions are italicized:

But there diesn't seem to be any explanation (that I can find) for that.

So, I'm stumped. How can we configure the transition that shows up next to the current status?

Accepted answers

All comments

Joseph Chung Yin

@Nathan Given -

Hi Nathan:

You need to ensure "obsbar-sequence" property setup is applied to all the outgoing transitions from the "In Progress" status in the desired ordering. Afterward re-publish the WF. The "obsbar-sequence" property controls the display ordering of the transition buttons/listings

Once it is done, then it should work as you expected.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

Nathan Given_43rz48

Hi @Joseph Chung Yin ,

Thank you for your suggestion.

Unfortunately, it didn't work. I verified that every outgoing transition from "In Progress" has an opsbar-sequence value that is an integer, ranging from 10 to 500.

The transition that has the lowest opsbar-sequence is "Need Info":

But after publishing the workflow the transition button next to the current status remains unchanged:

FYI: "Post Incident Review" has an opsbar-sequence of 400 (which comes 5th in the list of transitions).

Nathan Given_43rz48

Something to note: "Post Incident Review Needed" is a loopback transition: the origin and destination are both "In Progress".

I wonder if that has anything to do with it?

Nathan Given_43rz48

Okay, I just removed the "Post Incident Review Needed" loopback transition and now the "Post Inicdent Review Needed" button is gone

and

Dropdown honors opsbar-sequence.

Thus, it would appear that if there is a loopback transition, opsbar-sequence is ignored and the loopback is showed as a button directly to the right of the status button.

Hmm.

Dan Brockwell_1pqfcb

Hey Nathan, I'm an Associate Product Manager in Incident Management for Jira Service Management.

We're currently looking to better understand how teams conduct their post incident review (PIR) / postmortem process and their key pain points / user needs.

Came across your feedback and would love to set up some time to learn more about how your team runs PIRs. Feel free to shoot me an email on dbrockwell@atlassian.com if you'd be open to having a chat

unknown

Was there an answer as to why the button appears and how you could instead have it in the drop down?

Jonathan Cunliffe

I'd appreciate any input to the OP's question please.

Why, in my case only for loop back transitions, is the transition appearing as a button with the other transitions from that status in the drop down?

How can all of the transitions be exclusively in the drop down?

Thanks,

Jonathan

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management