Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Bulk transition to "CLOSED" without changing "Resolution"

How can issues be transitioned in bulk to "CLOSED" without changing the "Resolution"?

The field was set when they transitioned to "RESOLVED" so we shouldn't be altering again when it transitions to "CLOSED".

Screenshot 2020-04-17 at 09.48.32.png

1 answer

0 votes
John Funk Community Leader Apr 17, 2020

Hi Sean - Just make sure that the transition to CLOSED does not include any post functions that update the Resolution field. 

That doesn't appear to be the problem.

We can manually transition from RESOLVED to CLOSED without setting anything.

And we managed to use "Project Automation" to hack a "Bulk Operation":
- Scheduled for a specific time, provided the JQL with the action to transition from RESOLVED to CLOSED

Which identifies this as a problem in Bulk Operations.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events