Bulk change to transition an issue type from one status to another

[jdreizler]

I have several workflows in my project with different issue types.  I am trying to do a bulk change using transition issues and i am getting:

N/A

Transition Issues

NOTE: You do not have permission to perform a bulk transition on the selected 1 issues.

Only on one of the issue types on my project, the others are working just fine so i know it isn't a permissions thing.  What do I need to do to the one issue type to allow bulk change transition???

[Nic Brough -Adaptavist-]

I'm afraid there's no easy way to do this.  You'll need to search the list of issues for ones that are different.

First, if there is a spread of projects and issue types, your blocked one could be on a different workflow, and hence have different conditions.  Do you have one issue that stands out?

Second, look at the workflow(s) for the issues you want to transition - are there conditions on the transition you are trying to make?  Do you meet all those conditions for all of the issues?

Last resort is brute force.  Try to bulk-edit half the list.  If you can, great, you've halved the number of issues you have to search through.  If you can't then you've halved the number of issues from you list you know contain the problem.  You can iterate this down to the problem issues.

(My basic statistics understanding strongly suggests that a 50:50 split is going to be the slowest way to do it - a 2/3 split is likely to be faster, but don't quote me on the numbers, it's been a long time since I did any real work in that area)

[jdreizler]

It's a new workflow and the only condition i have is that on the transition to "Done" the issue is resolved.  So what i was trying to do is to bulk change the status from done to done to get them to resolved.  I have done this before in the past on a diff proj and it worked fine.  I tried one at a time multiple and all and nothing works.  Very odd that other issue types/diff workflow works fine.

[Nic Brough -Adaptavist-]

If you can't find the condition on the transition to done that is blocking you (or, as you've tried done-to-done, that transition too), I'm afraid you'll have to go down the route of eliminating blocks of issues, narrowing it down to the one that is stopping it.

There may be one other thing - if you are trying to transition 1,000 issues, that's not a short task.  I would want to look at how long it takes before it throws the error.  If it's a couple of seconds, it is almost certainly a condition, but if it's thinking about it for a minute, then I would also want to check the validators on the transition.

[jdreizler]

The following will be processed after the transition occurs

1. The Resolution of the issue will be set to Done.

thats the only condition on the transition it is a Post Function.

I tried each issue separately and it doesnt work.

[Nic Brough -Adaptavist-]

No, sorry, that's a post-function, not a condition.  And it's not the only one, there's at least four more there.

Look back at the transition settings, we need to be looking at conditions, not post-functions.

I know this is Jira-speak (a jargon specific to the Atlassian ecosystem), but I am not sure how else to point you at the right place.  You found the post-functions, so you must have been close - they're on the third or fourth tab in the pop-up, conditions are first or second.

[Nic Brough -Adaptavist-]

Post functions don't matter here.

There is a "hidden" condition in workflows - "transition issue".  This is implemented at a project level and is based on permissions.  You should check all the projects that the issues are in - do you have "transition issue" in all of them?

There's also one other thing to check - as a system admin, go to Admin -> Integrity checker and run the workflow-related checks.

There are times when Jira can lose track of an issue's place in the workflow.  It stores it in two places in the database, and if they go out of kilter, Jira can't work out what transitions to offer, so it offers none.  The integrity checker can correct these, so give that a run (it has to read everything, so you might be there a while), and then click "yes" if it says "I found some, do you want me to fix them".  There's no need for backups or anything, the check can't do any damage.

[jdreizler]

• Triggers0
• Conditions0
• Validators0
• Post Functions6

[jdreizler]

here are the 6 post functions:

The Resolution of the issue will be set to Done.

Set issue status to the linked status of the destination workflow step.

Add a comment to an issue if one is entered during a transition.

Update change history for an issue and store the issue in the database.

Re-index an issue to keep indexes in sync with the database.

Fire a Generic Event event that can be processed by the listeners.