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?
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
Hi @Jenny Alexandra Canastero Romero
For a question like this, context is important for the community to help. Please post the following:
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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 value
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.