Automation to set ticket dates to currently assigned sprint dates

[Kieran McShane]

I use the timeline feature in project boards to quickly move tickets to different 2 week sprints. 

Sometimes tickets sit in old sprints that have completed, and they need to get moved to active sprints or future sprints. They need to move freely between the 3 states.

I want to set up an automation so that the start date and due date of an issue is automatically set to the currently assigned sprint. 

However, in the rule building- there seems to be no easy way to pull the currently assigned sprint. I just returns a massive list of all the sprints that have ever been assigned. While I just need the latest.

{{#issue.fields.sprint}}{{startDate.jiraDate}}{{/}}

What can I do?

[Bill Sheboy]

Hi @Kieran McShane -- Welcome to the Atlassian Community!

There are several ways to do this, depending upon when you want to do it:

• When the sprint starts
  • Use a rule triggered on Sprint Started, and that will provide the single smart value {{sprint}} with its date attributes
  • Grab those dates to save them in created variables, to avoid smart value confusion later in the branching
  • Branch over the work items in the sprint, setting your dates to the variables
• Some other time
  • As you note, the Sprint field is a list of all the sprints the work item has been assigned to
  • That list's smart value may be filtered to get the specific one which is "active"
    • {{#issue.sprint}}{{#if(equals(state, "active"))}}{{startDate}}{{/}}{{/}}
    • {{#issue.sprint}}{{#if(equals(state, "active"))}}{{endDate}}{{/}}{{/}}

Kind regards,
Bill

[Kieran McShane]

Thank you for the fast reply Bill!!

• I need to be able to do this "some other time"
• I think you solution may only work if the currently assigned sprint is active, correct?
• I need to be able to pull the currently assigned sprint's dates, regardless if the currently assigned sprint is active, future, or complete. The issue I'm facing is many of my tickets have been in previous sprints. And #issue.sprint and #issue.sprint.last do not pull the currently assigned sprint (or most recent sprint). These return large lists of previous sprints.

If there is some way to pull specifically the most recent and currently assigned sprint of a ticket, regardless of sprint state, I believe that would provide a solution. It will need to work if that ticket has a history of other sprints assigned to it.