-
Bug
-
Resolution: Timed out
-
Low
-
2
-
Severity 3 - Minor
-
Issue Summary
This is reproducible on Data Center: Yes
Steps to Reproduce
- Open a roadmap and create a base level issue type
- Click on the issue type icon and observe the list of issue types given
- Repeat steps 1 and 2 in a different plan
Expected Results
The list of issue types displays in the same order every time
Actual Results
The list of issue types displays in different orders for different plans
| Plan 1 | Plan 2 |
|---|---|
 |
 |
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
-
- Gathering Impact
-
- relates to
-
JPO-20510 Loading...
[JRACLOUD-88547] When creating an issue and changing the issue type, the list of available issue types displays in random orders
This is affecting our team as well. The Issue Type Scheme and default issue type should be respected.
We ran into this as well on our Datacenter instance. This bug appears to be Cloud-centered and the link to JPO project is blocked by authentication. Is there a Datacenter version of this bug and can it be cross-linked here?
What is supposed to determine the order that the issuetypes are displayed in? We noticed, it is not following the order in the issuetype scheme, nor is the default issue type at the top of the list.
Hi everyone,
Thank you for previously 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.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!
Jira Cloud team