nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to automatically assign to a ticket the start and end dates of the sprint to which it belongs ?

Aline Veyradier

Hello,

I've searched in automation but I can't manage...

How can we automatically assign to a ticket the start and end dates of the sprint to which it belongs, in the fields "Start date" and "Due Date" ?

{{sprint.startDate}} => Start date

{{sprint.endDate}} => Due date

Thank you for your help !

Best regards

Aline

Accepted answers

Marc -Devoteam-

Hi @Aline Veyradier

See this automation. adjust the field to you field names

All comments

Marc -Devoteam-

Hi @Aline Veyradier

See this automation. adjust the field to you field names

Aline Veyradier

Thanks you for your answer, Marc, but it doesn't work :

"Error when editing tickets
TSS-1 (duedate must be in “yyyy-MM-dd” format (duedate), Start date must be in “yyyy-MM-dd” format (customfield_10015))"

... a problem with the date format

Aline Veyradier

The rule below works, but only when a sprint has been started.

2025-01-14 17_57_01-Générateur de règles - Automatisation - Test sprints Swanly - Jira et 5 pages de.png

(hope you're fluent in french ;o) )

Bill Sheboy

Hi @Aline Veyradier

Adding to the suggestions from Marc...

Please note an issue's Sprint field is a list of values. Thus when an issue "carries over" as incomplete from a prior sprint, the field now contains at least 2 sprints.

Thus it will help to know when you want to set the Start Date and Due Date values, and what they should contain:

triggering the rule on the Sprint Started trigger will ensure they contain the values for the active sprint, as your rule shows
any other scenario requires parsing the values, such by filtering the values in the {{issue.sprint}} field or finding the maximum dates

For example, if the rule trigger was not Sprint Started, you could set the date values for the issues in the sprint using these expressions:

{{#issue.sprint}}{{#if(equals(state, "active"))}}{{startDate}}{{/}}{{/}}

{{#issue.sprint}}{{#if(equals(state, "active"))}}{{EndDate}}{{/}}{{/}}

Or, if you assume the needed sprint is always the one with the latest dates, these would work:

{{issue.sprint.startDate.max}}

{{issue.sprint.endDate.max}}

Kind regards,
Bill

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud