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

"Edit Issue" not working while configuring automation to copy fields from Epic, how can I fix it?

May Azulay

Hi community

I'm trying to create an automation to copy a field from child issue to epic, an automation I succeeded in performing before but now this specific field is not cooperating.

*The field is typed "Select List (cascading)"

I added the field to multiple screens in our project.

When I run it, I get the following errors:

Edit issue

Could not find your configured field, it may have been deleted?

Roadmap

No fields or field values to edit for issues (could be due to some field values not existing in a given project):

SA-50833

Am I missing something?

Thanks

May

Accepted answers

Bill Sheboy

Hi @May Azulay

There are several possible causes for this symptom. Four of them are:

For the issue type you are copying to, the field is not selected for that issue type. Solution: work with your admin to add the field.
For the issue type you are copying to, the field is not on the issue views. Solution: work with your admin to add the field.
By default, the actor for rules is Automation for Jira, and that user has permissions to perform many actions. Has the rule actor been changed to someone who does not have the needed permissions?
Are the epic and child issues in the same project? If not, are any of the projects involved team-managed projects? If so, the fields will have different id values and so an advanced edit with JSON must be used to set the field.

Kind regards,
Bill

All comments

May Azulay

Adding for reference the error and the automation structure

automation process.jpg automation error.jpg

Wasim_1etshw

Hi @May Azulay ,

Once check the field "Roadmap" is still present into the edit issue screen and field configuration scheme for the respective issue types.

May Azulay

Hi @Wasim

Thanks for the quick response.

I verified it's present in both. Still getting this error...

Screenshot 2023-11-08 102214.jpg

Wasim_1etshw

Hi @May Azulay ,

The error is related to the copying the value from child to the parent issue.

It all about the inheriting the value from one to another issue, there is something which will impact the process of the action being performed.

To understand the concept of it you can go through the below mentioned linked why we facing this error

Automation For Jira - a rule fails with the error "No fields or field values to edit for issues"

Hope that helps you get the resolution!!

May Azulay

Hi @Wasim

Just to make sure we are on the same page, I'm trying to copy a value from the epic issue to its child issue (not backward)

I tried the solution offered in the link and it didn't work.

I also tried to replace "Epic issue" to "Parent issue" and also "trigger issue" but nothing worked.

What can we do?

Bill Sheboy

Hi @May Azulay

There are several possible causes for this symptom. Four of them are:

For the issue type you are copying to, the field is not selected for that issue type. Solution: work with your admin to add the field.
For the issue type you are copying to, the field is not on the issue views. Solution: work with your admin to add the field.
By default, the actor for rules is Automation for Jira, and that user has permissions to perform many actions. Has the rule actor been changed to someone who does not have the needed permissions?
Are the epic and child issues in the same project? If not, are any of the projects involved team-managed projects? If so, the fields will have different id values and so an advanced edit with JSON must be used to set the field.

Kind regards,
Bill

May Azulay

Hi @Bill Sheboy

Reviewed all 4 (I'm the admin)

1. When you say the field is not selected for that issue type, are you referring to the field configuration for each issue type? if so, the field is there for all issuetypes I'm trying to copy to. If I'm missing something here, please let me know

2. Reg the issue views - if you are referring to screens, That's cover too. not the issue I guess

3. Jira for automation is still the main actor for performing automation in our project ( I see it on other automation that is active)

4. All issues & Epics are in the same project

Not sure what to do next, appreciate your help

Thanks

May

Bill Sheboy

I noticed your rule image, and my first suggestion should have been: try adding a Re-fetch Issue action immediately after the trigger.

The Issue Created trigger can fire so quickly that the issue data is not yet available to the remainder of the rule (i.e., a race-track error). This can cause unexpected behavior the remainder of the rule. Always adding the Re-fetch Issue action with slow the rule by about a second, reloading the data before the steps proceed.

May Azulay

Hi @Bill Sheboy

Tried that too, is it possible it's related to the field functionalities?

Maybe I'm still missing something.

Adding screenshot:

Screenshot 2023-11-14 144737.jpg

Thanks

May

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