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,558,853
Community Members
 
Community Events
184
Community Groups

How to create an automation trigger on a sprint date that changed?

Hello, 

I have created a custom field called "Sprint end date" that is populated when the Sprint is started. 

Trigger: Sprint Started

Branch rule/Related issues: For issues in the Sprint 

Then: Edit Issue fields

  • Sprint end date 
  • {{issue.Sprint.endDate.jiraDate}}

If the Sprint end date changes during the active sprint, does anyone know how I could use automation to copy the new sprint end date into my Jira custom field?  

Thanks!

1 answer

1 accepted

3 votes
Answer accepted
G subramanyam
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 12, 2023 • edited

Hi @Jenny Severin welcome to the Atlassian community.

You should consider the below edits:

  • Create a new rule and set the trigger as "Issue Updated" Or "Sprint Changed" (please try with either one of the triggers).
  • In the Branch rule/Related issues section, add a condition to check if the issue's Sprint field has changed.
  • Note: You might need to add another condition to check if the issue is currently in an active sprint.

Thanks for the inspiration.  

I actually got it to work by using the "Scheduled" trigger with a JQL search "sprint in (openSprints())"

I added a condition to compare two values:

  1. The actual sprint end date 
    • {{issue.Sprint.endDate}}
  2. Custom field I created named "Sprint end date"
    • {{issue.Sprint end date}}

New action: Edit the fields to update "Sprint end date" with {{issue.Sprint.endDate.jiraDate}} if the two values didn't match.

sprint end date.jpg

Like G subramanyam likes this
G subramanyam
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 16, 2023

Thank you @Jenny Severin for sharing the automation rule. It will help lot of users who have similar query.

Like Jenny Severin likes this

Suggest an answer

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

Atlassian Community Events