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; } } }

Jira Automation Smart value sprint dates and assign dates to fields

Tina Park_ydioio

Is it possible to get a future sprints start and end date and then edit fields in the issues that were assigned to that sprint?

Sprint example

Name: "Sprint A (Feb 27 - Mar 5)"

Sprint start and end date: input date in fields

When sprint is created

Scenario 1: start date

IF {{sprint.name}} contains regex [sprint]

AND find the issues that belong in that sprint

Edit the issue field "start date" with that Sprint start date

Scenario 2: end date

IF {{sprint.name}} contains regex [sprint]

AND find the issues that belong in that sprint

Edit the issue field "end date" with that Sprint end date

Accepted answers

Bill Sheboy

Hi @Tina Park

I am a bit unclear on your use case...when a sprint is created it has no issues assigned to it, so the Sprint Created trigger could not be used as you note.

Perhaps an alternative would be a rule triggered on Sprint Started...as sprint planning has probably occurred by that point and so the issues could be updated:

trigger: sprint started
branch: on JQL to find the assigned issues with sprint IN {{sprint.id}}
- action: edit issue to set Start Date to {{sprint.startDate}} and Due Date to {{sprint.endDate}}

I assumed that you meant Due Date rather than End Date. If you have a custom field named End Date plus adjust accordingly. Thanks!

Kind regards,
Bill

All comments

Tina Park_ydioio

oops accidentally answered myself with an addendum and now I don't know how to delete this post

Fabian Lim

Hi @Tina Park

Post your solution and we can accept the answer for you.

Tina Park_ydioio

I don't have the solution. I replied to my post not knowing it will be classified as an "answer". I don't know how to solve this yet

Bill Sheboy

Hi @Tina Park

I am a bit unclear on your use case...when a sprint is created it has no issues assigned to it, so the Sprint Created trigger could not be used as you note.

Perhaps an alternative would be a rule triggered on Sprint Started...as sprint planning has probably occurred by that point and so the issues could be updated:

trigger: sprint started
branch: on JQL to find the assigned issues with sprint IN {{sprint.id}}
- action: edit issue to set Start Date to {{sprint.startDate}} and Due Date to {{sprint.endDate}}

I assumed that you meant Due Date rather than End Date. If you have a custom field named End Date plus adjust accordingly. Thanks!

Kind regards,
Bill

Tina Park_ydioio

Ah! yes, great catch. The trigger would definitely not work with sprint created. I think perhaps a manual trigger would work better for me in this case as I'm trying to prevent manually updating the target dates for each ticket in a roadmap view.

Thank you for the instruction re branch: find assigned issues! This was the missing bit.

I'll test this out later today and will accept answer with my adapted solution!

Tina Park_ydioio

works like charm, took some debugging as my company has A LOT of custom fields with the only difference in most being lower case vs upper case in the field.id. :T Also, some date parsing error and had to add ".jiraDate" to the end of the smart value per this post. ie. {{sprint.startDate.jiraDate}}

Screen Shot 2022-03-01 at 11.07.23 AM.png

Guaraci Nakamura

@Bill Sheboy I would liek to automatically fill the Start Date and End Date fields with the Sprint dates.

I am trying to follow the steps above but it shows an error. could you please help me on this?

When: Sprint initiated --> selected the only board available in the project
If: JQL --> sprint IN {{sprint.id}}
Action: Edit item's field --> End Date field --> {{sprint.endDate}} PS: in the image below i changed the startDate for endDate in the JQL.
Error:
ERROR: “The rule was defined with components that require the items to be available by the trigger. To run these components, you must add a branch to that sprint or JQL. The following components require items: JQL Condition, Edit Item”

Apresentação sem título.jpg

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-software

atl-gruland