Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Storing original sprint value in custom field

Hi All,

I am trying to find a way so that I can store the value of original sprint when a ticket is tagged to sprint for the 1st time in a custom field. Is there any possibility to do so?


2 answers

2 accepted

3 votes
Answer accepted
Jack Community Leader May 17, 2021

I would use automation but I would do it slightly different. I would have a custom field where you can restore the original sprint value. Then I would have a condition that checks if the custom field is empty when the sprint is field is updated (trigger). If it’s empty it would be the first time through and you would copy the original value from the Sprint field into your custom field if it was not empty it would do nothing. 

Okay, I had the same solution but what should be the data type of of the field, text?

Jack Community Leader May 17, 2021

Good question to be honest I’m not exactly sure as I have never attempted to copy a sprint field to another custom field. It might be fine just using a text field depends on how you want to use it as well. 

So Jack I chose a advanced field type of TEXT FIELD ( read only) 

2 votes
Answer accepted

Hi @Ankita Chattopadhyay  

You can do this using the built-in Automation, located in project settings under "Project Automation" for service desk projects, or just "Automation" for other projects.

You would need to 2 different rules to capture both transition types. The first rule for example would look like:

Trigger: Issue Transitioned
Action: Edit Issue
- Select Start field from "Fields to set" and add in  {{}}


Thank you so much Vikrant, it worked like magic :) 

I had few question around enhancing the automation rules so that the number of runs can be brought down as it is eating up the limits for a month. Any idea how the rules can be made more effective?

Like Vikrant Yadav likes this
  • Reducing the interval at which a scheduled rule executes. For example, only execute a rule every hour instead of every 5 minutes.

  • Restricting your JQL query to only search for the issues you care about. For example, check that the updated time of the issue is within a certain range (updated > -1w to include only last week's issues).
    check prevention method give in above link :- 

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

296 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you