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

How to add in automation to copy the Team field from the triggered issue?

Sari Kachorovsky

I would like to create an automation that once specific field is changed to Yes a new Story is created and the mandatory fields which are Epic Link and Team are copied from the triggered issue. I've succeeded with the Epic link but Team field is not found and I need to add a Json, I've tried few options but nothing works. Can someone please advise how the Json should look like? The example below is not working I'm getting the following: Error while parsing additional fields. Not valid JSON.

I've also tried and it failed:

"fields": {
"customfield_12300" : issue.customfield_12300
}

But when I gave a specific team number it worked :

{
"fields": {
"customfield_12300": "39"
}
}

Accepted answers

Marc -Devoteam-

Hi @Sari Kachorovsky

You found the resolution yourself.

This needs to happen via JSON and you need to specify the ID of the Team

All comments

Marc -Devoteam-

Hi @Sari Kachorovsky

You found the resolution yourself.

This needs to happen via JSON and you need to specify the ID of the Team

Sari Kachorovsky

@Marc -Devoteam- MY solution is not good, I don't know what will be the team, I need it to copy it from the triggered issue (The RFE). The teams can be different.

Marc -Devoteam-

Hi @Sari Kachorovsky

This will do the trick I think.

Before creating an issue add the action: Re-fetch issue data
Then add the action: Create Variable
Then create the issue and use the json

Collista Lewingdon

Maybe the solution might be as simple as making sure that the custom field is available in your project type and is associated with your project? Once you do that you should be able to see it in your drop down menu in automations.

This article regarding editing a custom field context might help you edit it so that is shows and is a selectable field within your automation.

Marc -Devoteam-

Hi @Collista Lewingdon

The Team field is not available in the field dropdown in automations even if available in your project.

This is a know topic, the same applies to Epic Status.

These fields can only be addressed via a JSON statement in using more options in an automation.

Sari Kachorovsky

@Marc -Devoteam- Thank Marc for your help, I've implemented your fix (beside that I've choose Story and not same issue type cuse they are different issue types) and I'm getting the attached error. Any idea why?

Collista Lewingdon

@Marc -Devoteam- Well that is odd because I am able to access it in automation. And...even better....custom fields that I have created can be selected in Automation.

Marc -Devoteam-

Hi @Collista Lewingdon

The default advanced roadmap team field is a fiedl created by Atlassian.

This field is visible within the custom fields (all system created or app created fields and self created).

The Team Field is a locked field and of the Type Team, this type of custom field can't be created.

See:

Screenshot 2023-08-31 at 08.44.24.png

The screen you show looks like a self created custom field, named Team. Am I correct on this assumption?

The above shown field is only usable within a JSON clause in an automation

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