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

Add cloned issue as Epic Link on transition

Ovidiu Vasilescu

Heya,

I'm trying to do a nifty Epic Workflow which creates some tasks / stories on certain transitions. I want these Tasks to have Epic link the original issue they were cloned from. Note that they are cloned from the Epic itself, so they can't inherit the Epic Link of the issue they were cloned from since Epics don't have Epic Link.

I've tried a few things so far and this one I was expecting to work, any ideas why it isn't?

def cf = customFieldManager.getCustomFieldObjects(issue).find {it.name == 'Epic Link'}
issue.setCustomFieldValue(cf, sourceIssue.key)

Cheers,

Ovidiu.

Accepted answers

Ovidiu Vasilescu

I tried a very dirty & basic workaround which solved a problem for me in the past:

Create "Dummy" field
On Epic creation, copy field Key to field "Dummy"
On Epic transition, clone issue as Task
On Task creation (inside the Task workflow), copy field "Dummy" to field "Epic Link"

I'm getting this error when looking at the Epic after I do this, so setting the field Epic Link requires something specific which I don't know about. The issue Key is not good enough.

EDIT: This actually works, just be careful to set the Copy Field to Field post-function AFTER the issue is created.

All comments

Tarun Sapra

Please see here - https://answers.atlassian.com/questions/211505

issue.setCustomField might not be right

Tarun Sapra

the same thing here - https://answers.atlassian.com/questions/13418341 (answer by user Dima Pasko )

Also, make sure that you have "Epic Link" issue added on the "Screens" of the issueTypes which are being cloned.

Ovidiu Vasilescu

Epic Link is added on the Screen, that's not the problem.

Even though the first ticket wasn't about a post-function, it had a snippet of code that might be what I was looking for. I tried it and it didn't work:

import com.atlassian.jira.issue.ModifiedValue
import com.atlassian.jira.issue.util.DefaultIssueChangeHolder
def tgtField = customFieldManager.getCustomFieldObjects(issue).find {it.name == "Epic Link"}
def changeHolder = new DefaultIssueChangeHolder();
tgtField.updateValue(null, issue, new ModifiedValue(issue.getCustomFieldValue(tgtField), sourceIssue.key),changeHolder);

My coding skills are really not that strong and I'm really out of my league right now. I really don't understand why issue.setcustomfield = sourceissue.key doesn't work.

Epic Link is a custom field and it's expecting an issue key, so it should work, no?

Any help is appreciated.

Ovidiu Vasilescu

I tried a very dirty & basic workaround which solved a problem for me in the past:

Create "Dummy" field
On Epic creation, copy field Key to field "Dummy"
On Epic transition, clone issue as Task
On Task creation (inside the Task workflow), copy field "Dummy" to field "Epic Link"

I'm getting this error when looking at the Epic after I do this, so setting the field Epic Link requires something specific which I don't know about. The issue Key is not good enough.

EDIT: This actually works, just be careful to set the Copy Field to Field post-function AFTER the issue is created.

Tarun Sapra

"I'm getting this error when looking at the Epic after I do this" - Do you mean Task or Epic?

Tarun Sapra

please see here - https://confluence.atlassian.com/jirakb/issue-screen-displays-error-rendering-greenhopper-epics-issue-web-panel-779158857.html

Tarun Sapra

"This will exit the Creation process and leave an inconsistency on issues. Make sure the "Creates the issue originally." Post Function is first in the Create transition."

Welcome!

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

Quick Links

Find more posts tagged with

scriptrunner

jira

jira-administration

jira-core