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

Automation Rule Links Seem Broken on Template Library

John Erickson_yept0y

When clicking on 'Go to rule' for any rule found in Jira automation templates for software teams it takes me back to the Jira automation template library and not the rule itself. For example, I wanted to look at the 'Send email reminder when task is near due' and rather than take me to the rule itself it just takes me back to the Jira automation template library. I'm assuming something is broken with the links as this happens with multiple rules. Anyone have a direct link to this rule so I can view it?

Accepted answers

Bill Sheboy

Hi @John Erickson -- Welcome to the Atlassian Community!

One challenge with the original, automation template library is the names / IDs of the rules have evolved over time and the links were not updated accordingly.

That specific rule was renamed to be more trigger-oriented: "When a task is near due → send email reminder"

My suggestion is to go to the full list and browse / search for what is needed:

https://www.atlassian.com/software/jira/automation-template-library/rules#/rule-list?systemLabelId=all&page=1&pageSize=20&sortKey=name&sortOrder=ASC

Better still: many of the template rules now exist in each project, and the list updates based on the project type: Jira, JSM, etc. To find them, navigate to your project's rule list, select Templates, and then search for the one needed. That same rule is present in the templates for adding to the project.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @John Erickson -- Welcome to the Atlassian Community!

One challenge with the original, automation template library is the names / IDs of the rules have evolved over time and the links were not updated accordingly.

That specific rule was renamed to be more trigger-oriented: "When a task is near due → send email reminder"

My suggestion is to go to the full list and browse / search for what is needed:

https://www.atlassian.com/software/jira/automation-template-library/rules#/rule-list?systemLabelId=all&page=1&pageSize=20&sortKey=name&sortOrder=ASC

Kind regards,
Bill

John Erickson_yept0y

Thanks @bill. I'm helping a group of Product Owners better work with their DEV teams. I was more so looking to send one email to the Product Owners highlighting work not currently done in a active Sprint where the Sprint will end in 3 days or less. I'm new to Jira Automations, so I'm working through this. I'll take a look at the link you provided and reach out if I have additional questions. Feel free to point me in the right direction pending you have an idea on what template I can use.

Bill Sheboy

The rule you describe using Sprint end date information is slightly different as it needs to find that information to decide when to send the notification. There is no built-in template rule for it...

First thing: in my opinion, reminder rules like this are a "smell" of a root cause / problem, as the team's daily scrum (i.e., standup) will keep everyone aware of progress. Perhaps having teams perform a 5-whys (or other RCA) during the retrospective will reveal why it is believed a reminder email is needed. Please discuss this with the team's scrum master / agile coach to learn more.

Regardless of that, an outline for rule like this for a single project would be:

trigger: scheduled daily, with no JQL
action: lookup issues with JQL to find incomplete issues in the current, active sprint

project = yourProject AND sprint IN openSprints() AND statusCategory != "Done"

smart values condition: only proceed if issues were found
- first value: {{lookupIssues.size}}
- condition: greater than
- second value: 0
action: create variable, to get the active sprint's end date
- name: varSprintEndDate
- smart value:

{{#lookupIssues.first.sprint}}{{#if(equals(state, "active"))}}{{endDate.jiraDate}}{{/}}{{/}}

smart values condition: compare the days remaining in the sprint to your target
- first value: {{now.diff(varSprintEndDate.toDate).days}}
- condition: less than
- second value: 4
action: send the notification email with the issues from the lookup results

The created variable works by iterating over the sprints in the first issue, extracting the end date for the "active" one. This approach is needed because issues could carry-over, and so the sprint field contains multiple values.

Welcome!

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

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

cloud

automation