Copy the sprints dates to custom field issue on different project

[Wouter Spaans (Planning)]

Hi,

I want copy the sprint dates from Development Project 1 to an Epic issue in Projct Management.

How can I ceate this in Automation?

Thanks!

[Bill Sheboy]

Hi @Wouter Spaans (Planning) 

The smart values you want to use for this are: {{issue.sprint.startDate}} and {{issue.sprint.endDate}}

Please consider when you want this to happen, such as at the start of the sprint, or some other event.  That will determine the trigger for your rule.

And...as an issue can be in multiple sprints, due to carrying over between sprints, you will need to consider how you want to handle this and any other edge cases.

Using automation rules requires learning and experimentation, and so I recommend you try to create the rule, and if you run into challenges to post images of your rule and explain what is not working as you expected.  That will provide context for the community to help.

To get you started on creating your rule, please refer to these documentation and example sources:

• https://www.atlassian.com/software/jira/guides/automation/overview#what-is-automation
• https://www.atlassian.com/software/jira/automation-template-library#/rule-list?systemLabelId=all&page=1&pageSize=20&sortKey=name&sortOrder=ASC
• https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/
• https://support.atlassian.com/jira-software-cloud/docs/use-advanced-search-with-jira-query-language-jql/

Kind regards,
Bill

[Wouter Spaans (Planning)]

Thanks Bill for responding.

The sprint dates i want use is for Epic issue from another project.

I create two custom fields for this Epic issue; Sprint Start and Sprint End. After a Sprint is created the sprints dates must be copied to this custom fields. 

My knowledge about using Automation is very basic, so i hope you can give me a example of how this works for me?

So my situation is:

Jira Project 1: Sprint A (with the start and end date)

Jira Project 2: Epic issue with custom field Sprint Start and Sprint End -> copy the Sprint date in to it.

Thanks!

[Bill Sheboy]

This is not a simple automation rule, as it may require multiple, multi-project scope rules, one triggering the other.  I recommend partnering with a more experienced site admin at your company to help you create and test these rules.

• One rule, triggered on sprint started, would identify the epics impacted, and add an indicator (or add a comment) to them
• The second rule, triggered on the indicator from the first rule, would then update the individual epic

The solution could be simpler if you have the epics and child issues (e.g., Story or Task) in a single project.  But even with that, if the issues have been carried over between different sprints or planned for multiple sprints, the rule becomes more complicated.