Yesterday we discovered that we can't inline edit the issue types in a project. First, we thought this a difference between JIRA Software and Service Desk.
This morning we realized, that in a different project of the same type inline editing of issue types is possible. Unfortunately we are unable to detect the cause. After a bit of researching we found out, that it's neither the permissions (same in both projects) nor the Issue Type Screen Schemes as described here:
https://answers.atlassian.com/questions/330505 (Type field is also on the edit screen of both projects)
Does anyone have an idea what else can it be?
Thanks in advance.
The issue type is not really a "field" like most of the other things you find on an issue. It's a structural item which configuration hangs off.
You can use simple edit to change the issue type, but only in certain circumstances. Permissions don't matter here (you can either edit an issue, or not, permissions don't apply to most fields). You are right about the inline editing - it must be on screen. But for issue type, there is a third point - the configuration of the issues.
The issue type determines all the other fields available, and the workflow for the issue (and other config including screens). If you change the issue type, it's possible that the fields or workflow for the issue might change, and if that happens, JIRA needs to check that the data for the issue will still fit with the config for the new type after the change.
It doesn't let you directly edit the issue type unless the configuration for the source and target type is identical, meaning using the same schemes. If they're not, you need to use "move" to change issue type.
So, my guess is that when you are seeing "no inline edit", your issue is currently of a type that has different workflow and/or fields to the other issue types in the project.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
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