The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
  • Community
  • Q&A
  • Jira
  • Questions
  • How to show the url and the summary of the parent issue(of a subtask) in the automation email body

How to show the url and the summary of the parent issue(of a subtask) in the automation email body

Sabri Alyakut
October 5, 2022

The bold part below doesn't work, any idea to show the url and the summary of the parent issue(of a subtask) in the automation email body?

 

Hi,

A new {{issue.issueType.name}} - {{issue.url}} was created by {{creator.displayName}}

The summary '{{issue.fields.summary}}' and description '{{issue.fields.description}}' with the priority {{issue.priority.name}}

Linked Issues are;
'{{issue.fields.issuelinks}}'

Parent Issue is
'{{issue.parent.key}}' and '{{url}}| {{issue.parent.key}}'
'{{#lookupIssues}}
• {{url}}| {{issue.parent.key}} {{url}}| {{issueType.name}}: {{summary}}>
{{/}}'

This issue is part of the following releases:
{{#issue.fixVersions}}
* Fix version: {{name}}, released/to be on {{releaseDate}}
{{/}}

For Bugs; Reproduction Environment(s) are;
{{issue.[BUG] Reproduction Environments}}

Regards

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

2 votes
Answer accepted
Mark Segall
Community Champion
October 5, 2022

Hi @Sabri Alyakut - A couple things:

It would help to see more context around this (screenshot of the entire rule).  However, a couple things:

  1. By simply using {{url}}, you're getting the url of the trigger issue.  You should use this instead if you want the parent URL:
    1. {{issue.parent.url}}
  2. Email formatting is html, so you can clean up the appearance by formatting your URL this way:
    1. <a href="{{issue.parent.url}}">{{issue.parent}}</a>

If that doesn't resolve your issues fully, please share a screen shot of the rule and/or a screenshot of a sample email with notes on what you expect for outcome.

Sabri Alyakut
October 5, 2022

It was not mentioned below but still works! Thanks

 

{{issue.parent}}
Accesses the details of a subtask's parent issue. Can only be used when the active issue is a subtask, and can't be used to access a standard issue's parent issue.

Available properties:
{{issue.parent.key}} - Returns the issue key of the subtask's parent issue.

{{issue.parent.priority.name}} - Returns the priority of the subtasks's parent issue.

{{issue.parent.Epic Link}} - Returns the issue key of the parent issue's epic.

{{issue.parent.epic.summary}} - Returns the summary of the parent issue's epic.

Like Mark Segall likes this
Marcel Rossouw
Contributor
April 24, 2024

For this to work now since parent/epic changes (team managed projects) - the following formats need to be used to return for #lookupIssues

{{parent}} - returns the Parent key

<{{parent.url}}|{{parent}}> - links the Parent Key

{{parent.summary}} - returns the name (summary) of the parent

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events