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!


Update custom field when another field is edited, Automation Rule vs Scripted Field vs ?

We have 4 custom fields which have to be updated if a certain system field is edited (Transition issue, Edit Issue);

I know that this can be done via Automation Rules and I just read that this can also be done by scripted fields (Scriptrunner);

which one is the better solution or is there another possibility?

1 answer

0 votes
Andreas Knecht
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 28, 2022

So with Automation you can setup a simple rule like this:

  • Trigger: Field value changed (and select your system field)
  • Edit issue action: And add your 4 custom fields 

This can be edited via the UI and will trigger for edit issue and transition issue.

I can't really comment on what's the better solution (between scripted field vs automation).  Scripted fields do probably allow for more power, but are probably somewhat harder to get going with. Automation is much easier to start with (simple point and click UI), but may not be able to support really advanced use-cases. Really depends on your comfort level with scripting and on your particular use case.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events