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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,554,250
Community Members
 
Community Events
184
Community Groups

Is it possible to do a bulk change to run automation rules?

Now there may be a better way around this and im pretty new to Jira so bare with me if this is a stupid question.

We have recently changed a number of automation rules in Jira Service Desk - the rules run when ticket is created that set field values (ie when reporter in a certain group, set certain other fields to other values) which has worked great for any new tickets that are created.

We want to apply this to existing open tickets and then be able to apply to legacy tickets (all resolved and closed) 

Is this possible, or is there another way to do it?

2 answers

2 accepted

2 votes
Answer accepted
Fabian Lim
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 19, 2022

Hi @Jon Bowes

Yes, it's possible.

In the global administration rule create a rule with a schedule trigger and use a JQL to pick up the tickets you want to update. Then run it manually.

We had a client where they had to update change the values of resolutions for existing closed tickets and this ran smoothly.  

Regards,

Fabian

I'm trying to change all the subtasks' priorities to the same as their parent priority, so I tried this method, but it didn't seem to work.

0 votes
Answer accepted
Dave Mathijs
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 19, 2022

Hi @Jon Bowes welcome to the Atlassian Community!

Depending on the trigger, you can copy the automation rule and configure it to run manually, then save it as a new rule. Then, you can run it manually on the legacy tickets. You won't be able to do that in bulk though.

For bulk actions, I would create one or more filters (f.e. 1 filter per group) and then perform the bulk update to change those fields.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events