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

In Jira Automation, how do I add to a component, and not clear the existing value?

April_Delay

I am trying to make a rule where when an issue is assigned to a specific set of users, the component field is updated to include a specific component, let's call it "kitttens". I got this automation working, however, it's replacing the values in the component field with "kittens". I want it to say "kittens" and "puppies".

Accepted answers

April_Delay

Well this is embarrassing, I solved my own problem

In case anyone else needs it, the answer in the automation is edit issue-> components-> "kittens" and "copy from issue"

All comments

April_Delay

Well this is embarrassing, I solved my own problem

In case anyone else needs it, the answer in the automation is edit issue-> components-> "kittens" and "copy from issue"

John Funk

Glad you found it! Sorry we couldn't get to you before then. ;-)

Chad Vernon_k3p1tw

How do you enter a component in addition to Copy Components from Current Issue? My UI only allows me to select Copy Components from Current Issue and I can't enter anything else.

Screenshot 2023-01-22 231048.png

Karen Corbeill

I am also looking for the answer to this. I want to add to existing values in the Components field. Right now my options are only Set or Copy. I would love the options to be the same as it is with Labels where you can specify Set, Add/Remove, or Copy.

unknown

I had the same problem: "copy from issue" wasn't available.

Luckly the Jira knowledge base helped out: https://confluence.atlassian.com/automationkb/how-to-add-components-to-issues-with-automation-rules-in-jira-1021222395.html

append one component

{
    "update": {
        "components": [{
            "add": {"name": "Name of the Component"}
        }]
    }
}

append multiple components

{
    "update": {
        "components": [{
            "add": {"name": "Name of the Component"}
        }, 
        {
            "add": {"name": "Name of another Component and so on"}
        }]
    }
}

A_ Boehme _Communardo_

This solved it for me, thanks! I was trying to set one or more components according to one or more asset objects ("App") that were set on the request.

To make sure I'm not appending components to an incorrect initial set, I first clear the component field and then iterate over the asset objects.

JSON for the advanced edit issue fields action:

{
"update": {
   "components": [{
      "add": {"name": "{{ProductApp.Component}}"}
      }]
   }
}

Bill Sheboy

Hi @A_ Boehme _Communardo_

First thing: for the piece of the rule you show, there is an Edit on the Components field and then they are apparently updated again later, but without first using the Re-fetch Issue action. As a result, the later edits may not work as expected.

Next, using an advanced branch over the values may lead to errors and collisions in the edits. The reason is branches which could be on more than one thing are executed in parallel and asynchronously, with no guarantee of processing order or when the branch will complete...up until the last step of the rule. This means each attempted edit with the JSON could collide, and potentially fail.

This is why the other posts in this thread suggest using one single edit which iterates over the values, creating a single JSON expression.

Kind regards,
Bill

A_ Boehme _Communardo_

@Bill SheboyI'll have a look at it in case I run into issues, so far my tests were successful.

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

automation

component