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,551,698
Community Members
 
Community Events
184
Community Groups

How do you apply a retroactive calculation + new custom field to existing tickets?

Hello There -

Halp! Padawan Jira admin here.

I created a new custom field that calculates the TAT in weeks for a project that uses automation (which worked for the new, succeeding tickets. Whew!)

That same calculation needs to be applied to tickets from a specific period so I created another automation using the same logic with a slight modification: the addition of a range filter (Expected action: All tickets created after 12/31/2022 should show the TAT + new custom field). See below:

JiraQ.jpg

The rule ran BUT no fields or calculation was created. **faceplam**

What could be a better approach here? Are new fields not applied retroactively even if it is applied to the existing screen?

Thank you in advance for sharing your expertise.

:)

1 answer

1 vote
Karim ABO HASHISH
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 04, 2023

hi @Mary 

I would suggest the below approach.

  1. Create a Rule with Manual trigger


    Manual Trigger.png
  2. Add a new branch of type Branch Rule / related issues

    L4g0LC1UJ0.png
  3. put your JQL to get all historical tickets needed (it will be like looping over the tickets retrieved from the JQL to perform some actions on each one of them).

    fGHezF4mnJ.png
  4. all the remaining steps is the same like the first rule you have configured for the new tickets.
  5. Please pay attention to add your component/actions inside the branch not outside the branch to make sure that it will apply for all (check below)

    KeqbSrvaA2.png
  6. Finally after competing all remaining steps, save and run manually.

 

Good Luck and let me know how it went for your or if any further help is needed.

Cheers,

Karim

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