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

Jira automation to Copy All release notes from all linked tickets in the parent ticket

Dirk De Mal_3mqsr2

Hi there,

I'm looking for a Jira automation where the release note fields from all linked tickets are all added to the release note field of the parent tick. To get some kind of automated overview in the parent ticket.

Tried it using branching in the automation but have not been succesfull.

Many thanks for all the help.

Kind regards,

Dirk

Accepted answers

Mark Segall

Hi @Dirk De Mal - How are you determining "parent ticket"? Is this a situation where all of the issues roll up to an epic or are you using a custom link type to establish a logical hierarchy?

This will help in determining the best path for consolidating the release notes into one issue.

All comments

Mark Segall

Hi @Dirk De Mal - How are you determining "parent ticket"? Is this a situation where all of the issues roll up to an epic or are you using a custom link type to establish a logical hierarchy?

This will help in determining the best path for consolidating the release notes into one issue.

Dirk De Mal_3mqsr2

Hi @Mark Segall ,

Thx for the help. The parent ticket is an Epic ticket where all of the issues reside under. We just link the tickets under an epic ticket.

Many thx for your help on this.

Kind regards,

Dirk

Dirk Ronsmans

Hey @Mark Segall ,

The parent issue here is the "trigger issue". So for example let's say the moment that issue is transitioned to a specific state.

There will be several linked issues on this trigger issue (no matter the link type). The goal is to capture a custom field from the linked issues, concatenate the values and edit the trigger issue with this value.

So it'll be a custom link type (not the epic link).

The main issue seems to be that in an Automation, the second you branch the data from within the brand itself it not accessible outside of the branch/root automation rule.

(Seems to be this: https://jira.atlassian.com/browse/JSWCLOUD-22527)

Mark Segall

This should be able to work...

TRIGGER: Field Value Changed (Release Notes)
CONDITION: Issue Type not equal Epic
BRANCH: (Parent)
- ACTION: Lookup Issues
  - "Epic Link" = {{issue}}
- ACTION: Edit Issue (Release Notes)
  - {{lookupIssues.Release Notes}}

Dirk De Mal_3mqsr2

Hi Mark,

Big thx for your feedback.

The parent ticket is not an epic ticket but a created issuetype (Release). My mistake.

So this is the automation we are working on...Everything works as expected until the last action...

TRIGGER: Manually triggered (for now)
CONDITION: Issue type equals Release
CONDITION: Linked issues present (All link types)
BRANCH: For linked issues (all link types)
- ACTION: Create variable (Getreleasenotes)
  - Smart Value : {{issue.fields.ReleaseNote}}
- ACTION: Add value to audit log
  - {{getreleasenotes}} (to check if the value is correct and it is)

So the next action is where I am stuck...Would it be possible to write the {{getreleasenotes}} value to the triggerissue value using the additional field configuration?

Many thx again for the help.

Kind regards,

Dirk

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud