Automation to put description footer note

[Aaron Geister _Trundl_]

Is there away to get the creation date of a linked issue ticket put into the description footer of the linked issue from the parent issue?

Been using Automation for Jira and not sure its possible. I know the linked issue is on the issue ticket. I got requested to add a creation date of the linked issue some where on the ticket so they have the information available. 
I know some integration tools are able to put data in the description footer and wondering if we are able to do the same?

[Bill Sheboy · Accepted solution]

Hi @Aaron Geister _Trundl_ -- Welcome to the Atlassian Community!

You could add the key and creation date of any linked issues to the end of the description field with automation.  However, what problem are you trying to solve by doing this?

Some notes before trying this rule:

• This could get "noisy" when there are several linked issues...especially as the links are also shown below the description field
• Please think of a way to partition the description for updates to this data, such as a prefix like "Linked Issues Created...", for any updates.  Otherwise when linked issues change the list could start messing up your description field with noise.

Kind regards,
Bill

[Aaron Geister _Trundl_]

Bill,

Sorry for not giving enough information. I am looking to put the creation date of the linked issue (parent issue) into the description footer so that the person reading the ticket can see when the originally issue was created. 

This is for a RMA type issue that is being created by automation to fullfil a part order. I would give IF statements so it only created this for specific issues or within the current automation if I am able to do so. 
I wasn't sure how to add description  footers like some add-ons or integration sync tools do. 

[Bill Sheboy]

Thanks for the additional information, Aaron.

I am a bit unclear on what you mean by "description footer".  To add the information you note as text to the description, a simple example rule is below, assuming the parent is an Epic and this is a company-managed project:

• trigger: unclear what you want here, but it needs an issue, such as issue updated
• related issues condition: parent epic exists
• action: lookup issues with JQL of key = {{triggerIssue.epic link}}
• action: edit issue to update the description; you may select the format you wish for the created date

{{issue.description}}

Parent {{lookupIssues.key}} created: {{lookupIssues.created.fullDateTime}}

If you are instead doing this for a team-managed project, please change the condition to check "parent" and the lookup issues JQL to key = {{triggerIssue.parent}}

[Aaron Geister _Trundl_]

Bill, 

What I mean by the Description footer is at the end of the description field is adding notes there. See bottom of this reply!

So I can use a smart value to look up issue and put the information into the description field & or maybe another field like environment?








This would be the description footer! 

[Bill Sheboy]

Yes, you may add the parent info to the description as I did in my example.  To add that same info in another field, just edit it as well.

[Aaron Geister _Trundl_]

Bill, 

Thanks so much for the assistance. 

[Bill Sheboy]

Glad to try to help!