Jira Automation, increment value in the Title

Peter Fahlstrom

Hi, I am struggling to understand if the Automation would allow the title of the created issue to change for each occasion it has been triggered. Example. I want the title of the new issue change (increment) to reflect the current quarter it has been created?

Earl McCutcheon

Hello @Peter Fahlstrom ,

This can be accomplished using Smart values and a variable broken into the quarterly values with some if/then logic and JQL identifiers for the variable by Quarter.

As a reference point the documentation for these concepts can be found here:

• Smart values - general
• What are smart values?
• Create Variable
• What is advanced searching in Jira Cloud?

In the following example I set this up using a manual trigger to simplify it for testing, but depending on the Trigger you want to use you will also want to add in a re-fetch for other trigger use cases that alter the data, as an example if you wanted this to occur on an "issue created" trigger, you need to include a "Re-fetch" action between the Creation of the issue and the create variable action, as the variable cannot be created until after the issue fully exists, and the re-fetch will allow the variable to get data from the issue as it is being created to be used in the automation rule.

So an additional logical breakdown on re-fetching is that data is created in Jira as part of the rule, the re-fetch then caches that original data value in the rule, the variable can then store that cached data element, and reuse the original data to modify data in other portions of the rule.  And a good example of re-fetching the data can be seen in this thread:

• https://community.atlassian.com/t5/Jira-questions/How-to-update-the-Summary-field-by-appending-text-using/qaq-p/1407893

Additionally, In the following Example, There needs to be a way to identify the time by quarter variable, I used Q1 - Q4 as the identifier with a breakdown of on the timeframe the issue was created, modify accordingly if you wanted to base the timeframe on something else, such as the resolution date or on an issue updated event:

• Q1: January – March
  • created >= startOfYear() AND created <= startOfYear(3M)
• Q2: April – June
  • created >= startOfYear(4M) AND created <= startOfYear(6M)
• Q3: July – September
  • created >= startOfYear(7M) AND created <= startOfYear(9M)
• Q4: October – December
  • created >= startOfYear(10M) AND created <= endOfYear()

Sot, the Rule breakdown will be like this:

• When:
  • Manually triggered
• Then:
  • Create Variable
    • Variable name "oririonalSummary"
    • Smart Value "{{issue.summary}}"
• if
  • Matches:
    • JQL
      • created >= startOfYear() AND created <= startOfYear(3M)
  • THEN
    • Edit Issue fields
      • Summary
        • {{oririonalSummary}} : "Q1"
• Else-if
  • Matches:
    • JQL
      • created >= startOfYear(4M) AND created <= startOfYear(6M
  • THEN
    • Edit Issue fields
      • Summary
        • {{oririonalSummary}} : "Q2"
• Else-if
  • Matches:
    • JQL
      • created >= startOfYear(7M) AND created <= startOfYear(9M)
  • THEN
    • Edit Issue fields
      • Summary
        • {{oririonalSummary}} : "Q3"
• Else-if
  • Matches:
    • JQL
      • created >= startOfYear(10M) AND created <= endOfYear()
  • THEN
    • Edit Issue fields
      • Summary
        • {{oririonalSummary}} : "Q4"

If an issue has the summary "test", When the above rule is triggered during each of the quarters the summary will update to one of the following:

• "test:Q1"
• "test:Q2"
• "test:Q3"
• "test:Q4"

Regards,
Earl