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

Object Schema automation rule still running after being deleted

David Strahle
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Mar 28, 2023

Please note this automation is in Object Schema not project or global automation.

We have created a workaround for a workaround where an automation rule will copy the Assigned user to a new field in order to export from Jira.

Rule is set on a schedule,

Matches AQL for Computers

Then updates an attribute.

The problem we are facing is there are over 25000 records, and this automation is taking a long time to execute.

We are looking at possible ways to stop this automation if something were to happen to our production system during business hours.

We have over 15000 staff who can potentially use this software during the day and about 2000 staff who use this software all day.

Alternatively, is there a way we can speed up this automation as we only need to run it once and we can perform this out of business hours.


Thanks for your help



Log in or Sign up to comment