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

Automations - How to parent a story to an epic in the same automation

Eric Browning

Hello,

I am trying to automate the creation of "release" work items. At a high lvl, I would like to do the following(see Image 1).

Create a release (Release XX)
Create a epic that has "Release XX" as a "fix Version"
Create a story that is a child work item of the epic above

I am running into issue with referencing work items that are created in the same automation. For example, on the story I only see "current work item" and "trigger work item"(see image below). Some things Ive tried are below:

using multiple automations but is getting difficult bc im passing multiple user inputs (due dates, assignee, ect) so id like to have it in all 1 automation
Setting up the additional fields of the story and referencing by the name of the epic

Is this possible to achieve?

Accepted answers

Bill Sheboy

Hi @Eric Browning -- Welcome to the Atlassian Community!

Rather than using JSON, you may enter the key for the most recently created work item (i.e., the Epic) when creating the Story in its parent field from the dropdown list:

{{createdIssue.key}}

Or, after the Epic is created, you may branch to most recently created work item, and then create the child Story in the branch...selecting Current Work Item as the parent.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Eric Browning -- Welcome to the Atlassian Community!

Rather than using JSON, you may enter the key for the most recently created work item (i.e., the Epic) when creating the Story in its parent field from the dropdown list:

{{createdIssue.key}}

Or, after the Epic is created, you may branch to most recently created work item, and then create the child Story in the branch...selecting Current Work Item as the parent.

Kind regards,
Bill

Eric Browning

great thanks Bill!

I am using the branching method mentioned. It looks like you cant have nested branches. Any idea on how i could relate the epic to the fix version with this limitation?

Right now i have:

- create 1 release

- create multiple epics all with the release fix version

- create multiple stories/task under the epics above

Bill Sheboy

First, your branching is incorrect to use the Epic as the parent of the new Task. Please try this:

trigger: manual
action: create version
action: create work item (for the Epic)
branch: to most recently created work item
- action: create work item (for the Task), setting the parent to Current Work Item as that will refer to the Epic you are branching-to
- ...repeat for additional Tasks

Next, to relate the Epic to the new Version, you may use advanced edit with JSON in the work item creation. For example:

{ 
  "fields" : {
    "fixVersions" : [ { "name": "the name you used for the new version" } ]
  }
}

One more important thing I noticed: you are creating work items in multiple projects.

Versions are associated to a specific Jira project. When the rule runs and creates that version, you may optionally select the project, but when you do not, the version is created in the project for the rule scope (in the details at the top).

A work item cannot be associated to a version in a different project with Fix Versions.

Please carefully check that your version is in the same project as the Epic to associate it that way.

Eric Browning

@Bill Sheboy great yeah that worked! and yeah the screen shot was just a POC where i was trailing and erroring.

Thanks again for the help!

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud