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

Jira Automation, copy Component/s and Security level from epic

Fabian Schöllhammer

Hello everyone

I want to use Jira automation to edit values in the Task.

That is what i have configured.

My Epics do have both values and i dont get any error message in the Jira Automation Log, still my Tasks (which are linked to the Epic) do not have any value in COmponent or Security Level.

Any idears what im doing wrong ?

Thanks in advance!

Accepted answers

Albert Manuel

@Sara Watson did you solved this?

All comments

Petter Gonçalves

Hello Fabian,

These fields do not have a proper form control yet on Automation for JIRA plugin, so they can not be edited like you are trying to do, however, you can configure them using a valid JSON object in the advanced form under More Options, as described in the documentation below:

Advanced Fields

To achieve your need, you will need to use Smart values to add the proper security level and Component to your epic by using the following parameters:

<span>{{issue.parent.epic.security}}</span>

<span>{{issue.parent.epic.components}}</span>

Please, check both documentation sent and let me know if you were able to configure the Automation.

Kashif Ansari

I am trying to do a similar thing. Whenever an issue is updated, I want the automation to check the issue's epic component. If the epic's components field contains Technical then I would like to update the given issue's components field with that of the epic.

Here is what I am doing.

Screen Shot 2020-04-20 at 1.06.43 PM.png

Sara Watson

Hi @Petter Gonçalves can you help me with the Advanced Field Editing for the following:

When: Issue Created

Then: Edit Issue Fields (Copy customfield_10001 from epic}

The closest I have gotten (as in, not an error message that it's not a valid JSON) was

<span>{{issue.parent.epic.customfield_10001}}</span>

but even that returned an error of : No fields or field values to edit for issues (could be due to some field values not existing in a given project).

Petter Gonçalves

Hello @Sara Watson and @Kashif Ansari

Thank you for reaching out.

Some smart values changed since my last answer. Please. try the syntax below as mentioned in this documentation:

<span>customfield_10001</span>}}{{issue.epic.

<span>components</span>}} {{issue.epic.

If it does not work, please ensure the field you are trying to edit is properly added to the edit issue screen of both parent and child issues.

Let us know if you have any questions.

Sara Watson

@Petter Gonçalves This is still not working for me. Is there more that needs to be added to the JSON to tell it to copy the field from the epic to the child issue (using "fields" or "update" maybe)? The error message I received this time said "Error while parsing additional fields. Not valid JSON.". See screenshot below of the rule as it exists now.

The custom field I am using in this case is "Team", which was setup in the project plan. I used <https://projecturl/rest/api/2/issue/issuekey?expand=names> to verify the custom field ID.

The Team is set in the epic but not in the child issue. The goal is to automate that selection so that anytime we are creating an issue from the epic, the child issue takes on the Team as well.

Parisa Askarnejad

Hi All,

I have a similar problem as Sara, I need to update the child's component based on the parent component. I am looking for a smart way to do this. if someone knows how to do this please share.

Thanks,

Albert Manuel

@Sara Watson did you solved this?

Sara Watson

@Albert Manuel No, I did not. Would be really great if there was a way to do it though!

unknown

{
"update": {
"components": [
{{#issue.epic.components}}
{ "add": {"name":"{{name}}"} } {{^last}},{{/}}
{{/}}
]
}
}

Mark Hanson

That works; thanks.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-software

automation