Issue Type Change

[Fabio Santos]

I’ve been noticing that some users are changing issues of type BUG to SUB-TASK and this breaks some automations.

Consulting the permissions of the project I saw that the user who made the change does not have the "move issues" permission in "issues Permissions" and yet the user is making this change.

I would like to know how to block this kind of change. No unauthorized user should be allowed to change the type of Issue primarily to SUB-TASK or TASK.

[Mark Segall · Accepted solution]

Hi @Fabio Santos - The Move Issues permission is for actually moving issues to another project.  This comes down to the Edit Issues permission.

The easiest route is to make the field view only for everyone:  It is likely that you're using a default screen scheme config which uses the same screen for Create/Edit/View actions.  You'll want to split this out by creating a new Edit version of the screen that does not include the Issue Type field.  Then set that new screen as the Edit action on the screen scheme.

If you still need a select group to have access to change the issue type, they could either do so by bulk edit or creating a "loopback" transition in the workflow with a transition screen that includes the Issue Type field.

Hope this helps.

[Fabio Santos]

Thank you @Mark Segall !👏

I removed the kind of problem from my scheme and now nobody changes that field.

I created a loop transition in the workflow and a screen to change the type of problem, but it didn’t work. The transition opens the screen and the problem type field does not enable the field for editing.

1 - Transition in workflow:

2 - Run transition in issue:

3 - The Issue Type field does not enable editing:

What should I do to enable this field...?

[Mark Segall]

Apologies for not clarifying in my previous message, but the loopback transition only works if issue types share the same workflow.  According to the message in your last screenshot, the Bug issue type has an isolated workflow.  In this case, you would need to perform a bulk edit (move) action.  This requires granting select users the global bulk edit permission.

[Fabio Santos]

That’s right!
That already helps to solve my situation.
Thank you very much again.

[Trudy Claspill]

Hello @Fabio Santos 

The Move Issue permission is not required to convert an issue to a subtask.

There is a change request to add a permission option for conversion of issues to subtasks and subtasks to issues. You can vote on it here:

https://jira.atlassian.com/browse/JRACLOUD-77335

I think the only way to prevent conversion to subtasks would be to remove the option to create subtasks entirely from the project.

[Fabio Santos]

Thank you @Trudy Claspill