Preventing User From Changing Issue Type During Move Operation

[Vasily Prokhorov]

Hey folks,

In our company we have specific issue types that we don't want our users to change when using the Move functionality (natively through the More -> Move menu or using the BulkClone Professional plugin's bulk edit) to move the issue from one project to another.

For example, if a user tries to move a Bug issue, we want to prevent them from changing it to a Story.

[Fabio Racobaldo _Herzum_]

Hi @Vasily Prokhorov ,

move allow users to move issues across projects or issue types. You can't prevent that.

Hope this helps,

Fabio

[Radek Dostál]

While there are ways or workarounds to hide the More -> Move option (https://docs.adaptavist.com/sr4js/latest/features/fragments/built-in-fragments/hide-ui-element-built-in-script comes to mind, and without SR it could be done with js/jQuery), there will always be the bulk edit option that I doubt you would be able to modify in any way (there shouldn't really be any underlying data in browser to tweak with in there).

Can't speak for bulkclone that much but as far as I know it doesn't provide any "conditionally disable/hide something".

All in all at most you could attempt to do some javascript magic (which I doubt can cover all browser angles either), but there will always be REST or Java API that will bypass it.

So all in all, I don't think that there is a way to really restrict issue move entirely, Jira doesn't have any such a thing natively and workarounds can only go some way but not the complete way.

Edit: You might try to set 'jira.permission.move.denied' on all statuses of the Bug workflow, as described here - https://confluence.atlassian.com/adminjiraserver/workflow-properties-938847526.html - but I have not tried this, don't know if it applies to bulk edit or bulk clone, plus it would be really bothersome to do, maintain, find, add to any new statuses, etc.

[Vasily Prokhorov]

Thanks Radek.

I'll take a look at the suggestions.

Respectfully,

Vasily