nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Issue with workflow transition permissions and moving issues

Neil Taylor

I'm assuming I am not the first to see this, but I couldn't find anything by searching on this specific issue. I have several workflows that require approvals and have conditions set up to only allow users in a role to make the transition happen. I recently saw someone create an issue in the project with a different issue type (Task) and then they moved the issue to being the issue type that requires an approval (Access Request). They were able to specify that they wanted the issue to be in "Approved" status on the move instead of "New", even though if they had created the issue correctly in the right issue type to begin with, they would not have been able to execute that transition. Has anyone seen this and if so are there any answers to lock this down?

Thanks!

Accepted answers

All comments

unknown

When they were asked for that "Status", did they try to change the initial status? Did JIRA allow? AFAIK, it won't because of the permissions.

Neil Taylor

They never changed the initial status - when they were able to change the status was during the move - on the move screen it gives the option to change issue type and then asks which status in the new issue that this ticket should be in and provides a drop down list of all statuses in the workflow that they are entering.

unknown

And what happens when they select other than the initial status from the dropdown? Does JIRA allows it?

Neil Taylor

Yes, JIRA allowed them to put it into "Approved" status instead of the initial status for the flow, "New" - there is a condition on the workflow to go from New to Approved that they must be in a certain role - this works as expected when going through the workflow. It's just the loophole with Moving an issue from one type to another

Sune Edmund Pedersen

Yes, the Move function enables the user to move between status without any of the triggers and validatrors configured in the workflows. This is a serious concern when relying on JIRA for controlled workflows.

I have tried to find ways to circumvent this as I like users to be able to move issues to other project if they have created them in the wrong project (happens quite often i my organisation).

I have found no solution and have disabled move for anybody but the project manager.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration

jira-core