Hello - I just added a new status and transition from Open (in total have 4 possible transitions) and now I have 2 Assign fields. How do I remove one?
I prefer to have everything in the workflow dropdown.
Yes - I wanted that as part of our workflow. To be able to get users used to working through the workflow instead of just hitting assign button all the time and bypassing the workflow.
Once someone hits Assign, they can assign a developer and the JIRA goes to Analysis status.
Try this one
If you want it removed for all users, then you can disable View ops bar assign link.
On Cloud, you can raise a support request at https://support.atlassian.com/contact and ask them to change the default number of items to keep on screen. If they set it to (say) 5, then up to 5 workflow actions will show before 6 and above get shoved into the "workflow" drop-down.
Yes, workflow transitions have "properties", one of which you can add is "opsbar.sequence". When drawing up the workflow options, Jira adds them to the list in low-to-high order. (Where it has no sequence, it uses the transition id)
If you're going to use this (and I would), then give yourself some gaps - use numbers like 10010, 10020, 10030 etc, so that you have some wiggle-room later, and can add 10012 and 10016.
Thanks - I did contact support and they said they can't add the number of items in the workflow dropdown and only option is to do what you said to move things around... I have created a feature request for this and hopefully there'll be enough votes so we can configure either hiding the default Assign button or adding the number of items in the workflow dropdown.
Thanks for your help,
Just heard back from Customer support and they state that "I'm afraid removing default Assign button is not possible at this time. There is an existing feature request regarding this matter, the Ability to remove "Assign" button from issue header bar and "Assign to Me" links".
Note the support ticket was opened in 2014, so i don't expect any fixes to land any time soon.
Dang that’s unfortunate... having that defeats the purpose of trying to implement a good workflow - in our shop it’s hard to get everyone to follow the flow properly.... Serena’s Business Manager allowed us to configure security so only managers can go outside the flow and re-assign ... hope they take it under consideration....
Thanks for the update!
The problem is the person transitioning to the next status would assign someone but if they can just go ahead and assign, they forget to transition to the next person. That's what's happening now so they just keep changing the assigned and the JIRA is not in the correct status... The Assign should be within the transition to ensure the workflow is flowing properly.
I disagree, the software is designed to be used by humans, and it is known that humans will generally take the easiest option (in this case clicking on the assign button). This is not a new thing and certainly predates the existence of Jira, as such it is a design flaw in Jira UX to know expect normal human behavior.
The better way to fix it would be to simply allow the removal of the button. finding/writing a listener is a way, but certainly not a better or easier way.
I disagree again. There are many cases where you need to assign without transition, and where you need to transition without assign.
In the overwhelming majority of systems, you'll find reasons for both. And your users just clicking "assign" and not moving things on screams that they don't really understand what they're doing. That's not always a bad thing, but when it's a problem, automation is the answer, not "removing useful options and bludgeoning the user"
I've been working on workflows for a long time and just not having the option of removing that Assign button is just causing issues for us.
Yes human error but should be configurable to fit the situation and not forced to have it there. Need the flexibility to force a workflow so the status is clear and who the owner is. My previous workflow (agree to my management) was that the resource or development manager/supervisor was the only one who should be able to bypass flow and can move to any status or assign to anyone. This provided accurate reporting to upper management and made it much easier for users so it's not so confusing with options.
If you took out the default Assign button and we need an assign transition, we can always add a transaction with restrictions from and to its own status to be able to do so, so we don't need that mandatory button there always.
Anyhow, hoping Atlassian would consider making this more flexible to fit different scenarios for different clients.
I agree the option of the button should be there, I just think that it should be able to be removed if the admin wants it to be, as i currently want it toi be as do all the other people that have asked this exact question since 2013. this way we are not "bludgeoning the user" with 2 or three different ways to apparently do the same thing which does get confusing. that i can say from experience as i was a jira user for a couple of projects some 4-5 years ago and the admins had designed a nice workflow that kept everything in the right place, but as there were ways round the workflow it was a mess for the admin and confusing for me and other users as there were 2-3 ways of apparently doing the same thing.
it is only now i am setting up my own system that i realize what a pain it can be and why that admin wanted to leave Jira altogether.
This all smacks of a broken and misunderstood process where people are working on a "not my problem" basis instead of understanding what they are doing.
The vast majority of Jira users simply don't have this problem. In fact, there was an option to remove the assign link back in Jira 3.something (if memory serves). It was dropped in pretty much the next release because of the howls of derision.
In cases where you're finding your users are repeatedly making mistakes, training, and then automation are the right approach, not bludgeoning them by removing useful functionality.
I've been working on workflow and automation since 1990 lol if the workflow is designed well, it's seemless, easy for new users and developers who want minimal options. You can train all you want but you'll always have handful of people that bypass. Just say'n :) I'm with Scott on this. Just asking for flexibility that's all - we're forced to use this and have to do a workaround. But yes, will have to respectfully agree to differ.
yep, that is exactly what i am doing. essentially anyone can add an issue to the backlog, but the next transition is it gets assigned to a dev (as well as some time estimations and other things) which puts it in the dev's task list.
to be honest i am surprised that the assign button is there by default.
Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot