Automation to allocate Planned Start and End Dates from Sprint Dates

[Andy Nabbs]

Has anyone created an automation that can be controlled via Category (as in all projects that fall within it) to run a rule that as soon as a Sprint Starts, select the Planned End Date and use the {{Sprint.Startdate}} etc.

The issue I have found is that you have to select a board, but you can only do that on one project (*required) thought about doing it at Status change to Added in Sprint, as this can be applied to a group of projects, but not working.

Any Help?

[Bill Sheboy]

Hi @Andy Nabbs 

A workaround for using a global rule to span different projects with sprints starting is to use an Incoming Webhook triggered rule, although this may be challenging to initially get set up:

• Create a rule with an Incoming Webhook trigger, saving the URL and Secret (Here are the recent updates to use secrets.) The Sprint ID will be passed as a parameter, so use that to make the decisions for the project, work items, etc.
• Work with your Jira Site Admin to set up a system webhook for "Sprint Started", entering the URL and Secret.
  • Pass the sprint ID as the parameter at the end of the URL
  • FYI - My test site was unable to pass the Secret in the designated field for the system webhook, and instead I had to add it to the URL...as described in the linked article above.  It appears the system webhook is not passing the correct header after those changes.  For example:
    • webhook URL/secret?sprint={sprint.id}

The webhook will fire and trigger the rule for all sprints started, and so your rule needs to check for the ones you want.

Kind regards,
Bill

[Ankit Srivastava]

Hi Andy,

I hope you’re having a great day!

For the automation rule to function correctly, your scrum board must include all project issues which is required or that align with your filter query, and the automation rule should be set up for that specific scrum board.

As you may know, when a sprint is created, Jira automatically designates that board as the original sprint board.

If you have multiple boards using the same filter query and a sprint has already been created on the original board (used in Automation), starting that sprint from any of the boards will trigger your automation. However, if you do not have a future sprint created on the original board and you close the sprint from another board, then create a new sprint from that board, the automation will fail when you attempt to start the sprint from the original board or any other boards. You will receive a message stating, "Sprint does not belong to the required board."

I hope this information helps you effectively plan your scrum board sprints and the associated automation.

Thanks,
Ankit Srivastava

[Gor Greyan]

Hi @Andy Nabbs

You have raised an important question, which I have faced already :) 

When using the "Sprint Start" trigger, Jira requires a board to be selected, and the rule becomes limited for that project.
You cannot currently apply a "Sprint Start" trigger to Project Category.

You can use the following Workaround if it suits you.

Instead of using the "Sprint Start" trigger, use the "Schedule" trigger.

Then set the following condition.
Sprint in openSprints() AND "Planned End Date" is EMPTY

Do the following action.

Planned Start Date: {{sprint.startDate}}
Planned End Date: {{sprint.endDate}}
Sprint Name: {{sprint.name}}

Let me know if you have any questions.

[Andy Nabbs]

unable to see schedule in triggers, is this a JQL trigger?

[Gor Greyan]

Hi @Andy Nabbs

You can set just the Schedule Issue Trigger, which will be simply run with condition.

Then you can set the conditions that I have provided.