Automation For Jira - How to create a rule that sends list of opened and closed stories from an on-going Sprint

Still need help?

The Atlassian Community is here for you.

Ask the community

robotsnoindex

 

Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.

Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

This article describes how to create an Automation Rule using the Lookup Issues action (available in Automation for Jira from the version 9.0.1), which will send a daily email to a group of users, including the list of opened and closed stories from on-going sprints.

(info) Note that this solution is only valid in the case where parallel Sprints are disabled in Jira (there is only one on-going Sprint per backlog).

Environment

  • Jira Data Center Only (This article does not apply to Jira Server licenses)
  • Applicable Jira / A4J (Automation for Jira) versions:
    • Jira 9.11.0 and any higher version (this Jira version ships with A4J 9.0.1)
    • OR Jira 8.20.0 and any higher version, in combination with A4J 9.0.1 

Solution

Rule configuration details

The rule will need to be configured as follows:

  • Add the Scheduled trigger with the settings below:
    • Frequency: Once per day
    • Select the option simply run the conditions and actions without providing issues
  • Add the Lookup issues action with the JQL below. (info) Feel free to adjust it to your liking, for example by filtering with a specific project.

    Sprint in opensprints() AND issuetype = Story AND Resolution is empty
  • Add the Create variable action with the parameters below:
    • Variable name: OpenedIssues
    • Smart Variable:

      {{#lookupIssues}}<tr><td><a href="{{url}}">{{key}}</a></td><td><a href="{{url}}">{{summary}}</a></td><td><em>{{assignee.displayName}}</em></td></tr>{{/}}
  • Add the Lookup issues action with the JQL below. (info) Feel free to adjust it to your liking, for example by filtering with a specific project.

    Sprint in opensprints() AND issuetype = Story AND Resolution is not empty
  • Add the Create variable action with the parameters below:
    • Variable name: ResolvedIssues
    • Smart Variable:

      {{#lookupIssues}}<tr><td><a href="{{url}}">{{key}}</a></td><td><a href="{{url}}">{{summary}}</a></td><td><em>{{assignee.displayName}}</em></td></tr>{{/}}
  • Add the Send email action with the settings below:
    • In More Options, untick the option Convert line breaks to HTML line breaks 

    • To: Choose the Jira group of your choice

    • Subject: You can use the suggestion below:

      List of on-going and resolved issues in current sprint
    • Content: You can use the suggestion below, which will list all the issues along with their URL, summary, and assignee:

      <h2>List of on-going and resolved issues in current sprint</h2>
      
      <h3>On-going Issues from Sprint</h3>
      <table border="0" cellspacing="0" cellpadding="2">
      <thead>
      <tr>
      <th align= "left">Key</th>
      <th align= "left">Summary</th>
      <th align= "left">Assignee</th>
      </tr>
      </thead>
      <tbody>
      {{OpenedIssues}}
      </tbody>
      </table>
      
      <h3>Resolved Issues from Sprint</h3>
      <table border="0" cellspacing="0" cellpadding="2">
      <thead>
      <tr>
      <th align= "left">Key</th>
      <th align= "left">Summary</th>
      <th align= "left">Assignee</th>
      </tr>
      </thead>
      <tbody>
      {{ResolvedIssues}}
      </tbody>
      </table>

Screenshot of the rule

The complete rule is illustrated in the screenshot below:

Example of email sent by this rule





Last modified on May 30, 2024

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.