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

AUTOMATION_EPIC (PARENT LINK) for INITAITIVE_dont exists in Action "EDIT"

Mateusz Janus_emo9ao

Brothers, Sisters

how to update parent .jpg

I have a simple automation.

1. Initiative is created

2. Automatically it is LINKED (flat) with EPIC

3. I want to now update EPIC - Parent Link with Initiative issue.key

I am creating variable and want to put it into EPIC Parent Link but this field is not available in Action "EDIT".

How else i can update this field. I dont believe its not possible.

Accepted answers

Christos Markoulatos -Relational-

Hi @Mateusz Janus

Instead of picking a field from the dropdown, scroll down in the Edit Issue action and look for "Advanced field editing" or use the raw JSON edit mode. You can set the parent link using:

{
"fields": {
"parent": {
"key": "{{initiativeKey}}"
}
}
}

Where {{initiativeKey}} is your smart value variable storing the Initiative issue key ({{INITID}} in your case).

Hope this helps!

Marc -Devoteam-

HI @Mateusz Janus

Is the parent issue (work item), you want to "link" in the same project?

Is the hierarchy in Jira adjusted so Initiative is on a level above Epic?

If this is not the case, the rule has to span multiple spaces, you will need to be a Jira admin at least to create a rule via "Global automation" and set the scope of the rule to multiple spaces or global (all spaces)

@Christos Markoulatos -Relational- Parent can be chosen and used from the dropdown, if field is on the screen.

So most likely this is based on the scope of the issue or permission related.

All comments

Christos Markoulatos -Relational-

Hi @Mateusz Janus

Instead of picking a field from the dropdown, scroll down in the Edit Issue action and look for "Advanced field editing" or use the raw JSON edit mode. You can set the parent link using:

{
"fields": {
"parent": {
"key": "{{initiativeKey}}"
}
}
}

Where {{initiativeKey}} is your smart value variable storing the Initiative issue key ({{INITID}} in your case).

Hope this helps!

Marc -Devoteam-

HI @Mateusz Janus

Is the parent issue (work item), you want to "link" in the same project?

Is the hierarchy in Jira adjusted so Initiative is on a level above Epic?

@Christos Markoulatos -Relational- Parent can be chosen and used from the dropdown, if field is on the screen.

So most likely this is based on the scope of the issue or permission related.

Mateusz Janus_emo9ao

hi @Marc -Devoteam-

1. yes same project. I have an Initaitive and EPIC, both are Linked Issued (flat)

2. Yes hierarchy is correct, Initiative is above EPIC

also this is my ParentLink id FieldId=10101 cause i found it i custom filed section.

I dont need to make it global rule if its not required. All happens under one project but i can try make it as Global if it helps. Question is should i use same JSON method like proposed? Instead of "parent" maybe better use "customfield_10101" ??

What else i can do then? any other JSON method?
CC: @Christos Markoulatos -Relational-

Marc -Devoteam-

Hi @Mateusz Janus

Ah you are on DC, yes, you should use the JSON method, as automation on DC can't use the parent field (like in Cloud)

Mateusz Janus_emo9ao

yeeeep... lovely DC but want to ensure about JSON cause i am just copy paste this

{
"fields": {
"parent": {
"key": "{{INITID}}"
}
}
}

Can I use this instead?

I am not so solid with JSONs...

{
"fields": {
"customfield_10101": {
"key": "{{INITID}}"
}
}
}

@Marc -Devoteam- @Christos Markoulatos -Relational-

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-data-center

automation

data-center

initiative

parent-link

automationconcepts