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; } } }

Buttons on Jira Cloud both ways going

Jan Šimek_zu1qlq

Hi, I would like to ask if you know how to manage if we need to have a buttons for moving through transitions and to look good, but we also have 2 statuses which have to be allowed everywhere and also we have got always possibility to go one step back - in case of failures.

I have found out, that you can make buttons, but in any property you have to sort it according to value, which is actually not making sense for us, as we need these step back, just in case.

Do you guys have any suggestion, how to approach this?

Also is there a way how to create some nice graphic for the buttons?

Thanks

Accepted answers

Ste Wright

Hi @Jan Šimek

I assume you're using a Company-managed Project, where these types of transitions are possible?

Then to clarify...

You have a set of Statuses and Transitions in a Workflow
Some Transitions are closed (Status A can transition to Status
Some are open (you can transition to Status Z from any Status)
You need single reversals (you can transition back to Status A from Status

Is this correct?

I'm not sure what you mean by the buttons though in Cloud - can you clarify? A screenshot would be ideal here!

In general terms, I'd consider if this is too much complexity first.

If some Statuses can be transitioned to from anywhere, and you need reversals, why not just let all Statuses transition to all others? Is there a specific reason not to do this?

Ste

All comments

Ste Wright

Hi @Jan Šimek

I assume you're using a Company-managed Project, where these types of transitions are possible?

Then to clarify...

You have a set of Statuses and Transitions in a Workflow
Some Transitions are closed (Status A can transition to Status
Some are open (you can transition to Status Z from any Status)
You need single reversals (you can transition back to Status A from Status

Is this correct?

I'm not sure what you mean by the buttons though in Cloud - can you clarify? A screenshot would be ideal here!

In general terms, I'd consider if this is too much complexity first.

If some Statuses can be transitioned to from anywhere, and you need reversals, why not just let all Statuses transition to all others? Is there a specific reason not to do this?

Ste

Jan Šimek_zu1qlq

HI,

thanks for reaching out to me. So what we have got is closed transitions and on every transition is a reverse one - in case of failures. There are also at least 2 statuses, which would result in request DONE from anywhere. The thing is, that if you need to move from one status to another - or lets say go back - it looks awfull, so that is why I would like to create these buttons, so that it would be visually appealing and it would not set a possibility for a failure. But I do not know how to make them, so ... yeah. What I ment by Cloud is, that we are in JIRA CLOUD and since there are differences between cloud and server JIRA I am not even sure if Cloud supports these buttons or if you can graphically change them to your needs or if they are just basically static...

In attachment there you can see our workflow and the mess when you try to change the status.

Ste Wright

Hi @Jan Šimek

Natively, you can't modify the way transitions are displayed in Jira Cloud - they show in the list provided in your screenshot.

Your Workflow does look quite complex though. I'd consider if...

On Hold: Could this be represented by flags, so you can highlight when something is on hold, and at what stage?
Resolutions: Using these in place of multiple "Done" Statuses - the resolutions might be Lost, Declined, etc. This could remove 4-5 Statuses
Remove direct Lost/Declined Transitions: If you can transition to these from anywhere, why do you need to transition from "In Negotiation" directly? It creates confusion, given you have the option to transition to each status twice in your screenshot list
Join D/M: Use a field or component to identify different types, and set conditions to allow "Testing" to be available for one and not the other
Test Success/Failure: Is Test Success the end of the Workflow? If yes, this could be a resolution. Is Test Failure classed as done? If not, consider leaving them in just Testing unless there's a specific reason to call this out
Information Delivered: Join these together as one resolution, with Join D/M taking care of the need to split the data

Simplifying your Workflow would make the list smaller, and thus make it less messy - but should also make your system simpler to use

Ste

Jan Šimek_zu1qlq

Hi,

thanks for all these answers :-) I know it is a bit messy as we are still adding new things as our needs demand. So:

- On Hold: - Not sure what you mean by flags? This status is there just only because of one person, which needed to have extra status for special cases.

- Resolutions: Not sure about the difference between resolution and DONE status? I though, that when issues are in DONE status, they are always resolved?

- Remove direct Lost/Declined transitions: Good point there. Thanks

- Join D/M: So you are suggesting to create a fields which will determine whose request goes to testing and then by filters separating them?

- Test Success/Failure: Test Failure and Success is a DONE status, which basically says, that the request ends there, but in case of Success creates a new one, which have to go all the workflow again. The reason they are separated like this is because we want to monitor which one have been successfull and which not.

- Information Delivered is there basically just only because sales guys wants to separate either cases by their name and also because they have to confirm, that they have started their cooperation with partner.

So if I summarize it buttons are not possible to set in JIRA Cloud?

Thanks for help

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

status

button