Automation to automatically align target start and end date with sprint start and end date

[Scott Federman]

Im trying to find an automation where if i have a story that is assigned to a sprint and the sprint goes active, the the ticket would assume the sprint start and end date based in the target start and end date fields. Is this possible? 

[Trudy Claspill]

Hello @Scott Federman 

You can do this with an Automation Rule.

If you use the Sprint Started trigger you can get access to that sprint's start and end date/timestamps using the smart values

{{sprint.startdate}}

{{sprint.enddate}}

Those are date/time values in UTC (all date/times are stored in UTC in Jira). You would need to use format commands to get just the date portion of the information.

In your rule you can use a branch for related issues "Issues in sprint" to cycle through the issues in that sprint and update the start and end dates in each issues to match the sprint dates using smart values like {{sprint.startdate.jiraDate}}

Something to consider, though, is how to handle the scenario of issues that carried over from a previous sprint. Do you want to overwrite the Start Date in an issue when work was actually started in a previous sprint?

[Scott Federman]

@Trudy Claspill this should work. How would i edit that target start and target end field in automation. Those fields a from plans and don't appear as options when i try to edit fields and look at the dropdown. 

[Trudy Claspill]

If you have added the fields to the Screens for the issues in the relevant projects and the fields are not showing up in the field list in the Edit Action in the automation rule, then you will have to use the Advanced Field Editing with JSON option to modify the values.

https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/

[Scott Federman]

@Trudy Claspill I am brand new at JSON. This is what I put. 

{
"fields": {
"Target start": "{value: {{sprint.startdate}}"},
}
}

This is the error i get:

Any ideas?

[Trudy Claspill]

Hello @Scott Federman 

Please show us the entire rule you constructed and the details of each step.