-
Bug
-
Resolution: Timed out
-
Medium
-
7
-
Severity 3 - Minor
-
Issue Summary
Team-managed (formerly next-gen) projects - Changing the issue type triggers the bulk edit action.
Steps to Reproduce
- Create a team-managed (formerly next-gen) project.
- Create two issue types with the same fields.
- Create a new issue.
- Try to change the new issue's issue type.
Expected Results
You can easily switch between two different issue types.
Actual Results
The bulk edit action is being triggered.
Notes
On company-managed (formerly classic) projects, we can switch between issues types if those issue types are part of the same workflow.
On team-managed (formerly next-gen) projects, we were able to switch between issue types since all issue types are connected to the same "workflow".
Workaround
Perform the bulk edit action.
Root cause:
The bulk move has been triggered due to the mismatch in the backend in terms of the number of required fields between the source and designated issue types. The mismatch happens due to a bug we had in the past which accidentally un-require a field which by default should be required.
[JSWCLOUD-18162] Team-managed (formerly next-gen) projects - Changing the issue type triggers the bulk edit action.
I found a related feature request but for Classic projects https://jira.atlassian.com/browse/JRACLOUD-40889.
The switching of an issue type used to take mere seconds because it was done in the context of the project I am currently viewing. As a Product Manager, forcing me to go into a bulk process when I have no need and did not signal that I need to change more than one issue's type is inefficient. It now takes five actions at a minimum to do what used to be a single action.
This bulk upload bug is so frustrating! It's so time consuming that it's faster for me to create a new issue, copy and paste info, and delete the old one. I'm also surprised that this is low priority when the most recent changes I've noticed is UI hints that you now support emoji and shortcuts for description formatting? I mean, those are great things, but the time I save in formatting more quickly gets eclipsed by the time it takes to change an issue type.
Note: This is such a heavy part of our day-to-day it can throw off a group session several times to go through the bulk flow for a single issue to change it's type.
This isn't feature parity w/Classic, it's a regression from functionality that Next-Gen used to have.
Thanks
Bummed this is prioritized as low considering it affects so much of my and my team members' days. The bug just showed up randomly and hoo-boy is it annoying.
Hi all,
Thank you for raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved.
To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.