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 - Copy from Epic Issue - Can't find issue to copy from

Gábor Hajdu_1k8lvq

Hi All!

I'm facing a problem that i can't figure out - details:

I use an automation rule to copy a few custom field data from Epic fields to its Isseu fields. It is seems working, but in case of a few issues i have got the following error in the audit log, and also found that Jira did't make the necessary copies:

"Can't find issue to copy from

customfield_10034, customfield_10036, ..."

I used the following rule:

1. When scheduled - every 90 minutes

2. Branch Rule - For: Current Issue

3. Issue fields condition: Issue Type is not one of Epic

4. Then Edit Issue fields:

- Copy customefield1 from Epic Issue

- Copy customefield2 from Epic Issue

...

- Copy customefieldN from Epic Issue

All the affected Epics are exists and filled with all the necessary data. Also the issues are existed and linked with their Epics well. (And they are normal issues, not sub-tasks.)

I'd tried more times to run manually the rule, and got the always the same results - 95% of the issues updated well, and the remaining has the "some errors" resulted with the "can't find issue to copy from" log.

I have no clue, i appreciate any comments, suggestions, thanks!

Accepted answers

Fernando Eugênio da Silva_2ddgg8

@Gábor Hajdu

Is there any chance that the issues that are having problems are Sub-tasks?

From the description, your logic seems fine, but if Jira for some reason was unable to make the copy looking at a Copy from Epic reference, it means that perhaps the issue is not associated with an Epic or it is a Sub-task.

Can you check this and if it is not the case, can you put here the example of the JQL you are using in Scheduled?

Bill Sheboy

Hi @Gábor Hajdu

For a question like this, please post images of your complete rule, showing the details of the trigger and actions, and of the audit log details showing the rule execution. Those will provide context for the community to offer ideas. Thanks!

Until we see those...that symptom could happen when:

the JQL for your trigger is returning issues which do not have epics
while the rule is running, an issue is removed from an epic
while the rule is running, an issue selected by the trigger JQL is moved or deleted
one or more of the custom fields selected are not present in one of the issue types: epic parent or children

After we see your rule information, we can narrow down the cause of this symptom.

Kind regards,
Bill

All comments

Fernando Eugênio da Silva_2ddgg8

@Gábor Hajdu

Is there any chance that the issues that are having problems are Sub-tasks?

Can you check this and if it is not the case, can you put here the example of the JQL you are using in Scheduled?

Bill Sheboy

Hi @Gábor Hajdu

Until we see those...that symptom could happen when:

the JQL for your trigger is returning issues which do not have epics
while the rule is running, an issue is removed from an epic
while the rule is running, an issue selected by the trigger JQL is moved or deleted
one or more of the custom fields selected are not present in one of the issue types: epic parent or children

After we see your rule information, we can narrow down the cause of this symptom.

Kind regards,
Bill

Gábor Hajdu_1k8lvq

Hi @Bill Sheboy , thank you for your kindly answer.

My rule is the following:

And the result:

Both the issue and its epic are exists and in active state - that is why i can't understand the error result. For example:

Epic: BPSZH-861 > Issue(Task): BPSZH-862

Gábor Hajdu_1k8lvq

Thanks @Fernando Eugênio da Silva for your answer!

I've double checked, and all of my errors got on normal tasks, not sub-tasks.

Both the Task and its Epic are exists and in active state.

I have attached images in my previous answer to Bill Sheboy. May you can take a look at them, if i am missed something necessary.

Thanks!

Bill Sheboy

Thanks for that information.

The audit log also shows BPSZH-860 was picked up by the scheduled trigger: what type of issue is that?

I suspect is it not an epic and it does not have a parent epic, as that would cause the errors in the Edit Issue action.

If your intention is the second part of the rule only runs for issues which have an epic parent, you can enforce that by adding another condition test after the test "Issue Type is not one of: Epic".

Gábor Hajdu_1k8lvq

Thanks for your suggestions.

BPSZH-860 is another active issue (task) that has an active parent epic BPSZH-854. There is no different with BPSZH-861/BPSZH-862.

Again, i've double checked:

- Only Issue/Tasks are used (sub-tasks doesn't)

- All the issues are active issues, and has an active parent epic.

- Only a few of them ends up with error described earlier.

- Using the issue editor, i can click to the linked epics and open them with no problem.

- Only the rule automation seems like can't find the right epic. (but only 5% of the issues)

Scott Jackson_nk939s

I'm finding that "copy from Epic issue" doesn't work reliably anymore — probably a symptom of Atlassian's retiring of Epic Link in favor of Parent Link.

Instead, you'll have to do something along the lines of these smart values, especially necessary for Sub-tasks trying to pull from Epics grandparents:

Tasks: {{issue.parent.key}}

Sub-tasks: {{issue.parent.epic.key}}

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