Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

The value of an inherited field is not visible

Jenny Alexandra Canastero Romero
December 15, 2025

I created an automation so that children inherit the value of a specific field. The log shows that it runs successfully and that the children are updated, but that value is not visible in the issues. Why?

3 answers

2 accepted

1 vote
Answer accepted
Florian Bonniec
Community Champion
December 15, 2025

Hi @Jenny Alexandra Canastero Romero 

Do you have configured a context for the child type ? If so does the value from the parent valid for the child ?

You may also have a field configuration that hide that field for this type.

From the work item you can try ... (top right) > Find your field. It will help understand why it's not displayed.

https://support.atlassian.com/jira-software-cloud/docs/find-a-field-on-the-issue-view/

Regards

0 votes
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
December 15, 2025

Hi @Jenny Alexandra Canastero Romero 

For a question like this, context is important for the community to help.  Please post the following:

  • what type of project is this: company-managed, team-managed, JPD, etc.
  • an image of your complete automation rule in a single image for continuity
  • images of any relevant actions / conditions / branches
  • an image of the audit log details showing the rule execution
  • explain what is not working as expected and why you believe that to be the case

Until we see those...

Are the parent and child work items all in the same project?  If not, the rule scope may need to change.

What are the types of the fields involved?

 

Kind regards,
Bill

Jenny Alexandra Canastero Romero
December 15, 2025

Hi, thanks for your answer. This is automation and processing with unexpected results:
Project type: company-managed

This is the automation and process with unexpected results:
Project type: company-managed

What I expect is that when changing a custom header (Work Category) in the main issue, that value will be inherited by the children.
In the images, I show the automation and the log.

The log shows that the process runs successfully and shows that the children were updated, but when I look at one of the children, it does not have the updated valueDiapositiva1.JPGDiapositiva2.JPGDiapositiva3.JPGDiapositiva4.JPGDiapositiva5.JPGDiapositiva6.JPG

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
December 15, 2025

Thanks for the images, @Jenny Alexandra Canastero Romero 

Rather than setting the field with a smart value, please try changing the Edit Work Item action using the ... option at the right of the field, and selecting Copy from the Parent.

0 votes
Jenny Alexandra Canastero Romero
December 15, 2025

This is the automation and process with unexpected results:
Project type: company-managed

What I expect is that when changing a custom header (Work Category) in the main issue, that value will be inherited by the children.
In the images, I show the automation and the log.

The log shows that the process runs successfully and shows that the children were updated, but when I look at one of the children, it does not have the updated value.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events