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

Automation set team on ticket creation stopped working

Marius Skoglund

Hi all, we have had an automation active for a while that fills the Team field on ticket creation. This was working up until recently, and as I was tasked with changing the Team value, I noticed that this was no longer working.

The automation is triggered on ticket creation, and it fills in custom field Team with the Team ID found within Plans > Manage Shared Teams. I had this working with a different Team ID, but this has all seemed to stop working now.

Can anyone shed some light on why this automation has stopped working? Schermafbeelding 2023-03-17 092504.png

Thanks, and kind regards

Marius

Accepted answers

Marius Skoglund

This was resolved. The workflow was changed and there was no Issue Created event firing on the create transition. Once added, automation is working again, and the team is set correctly.

All comments

Rilwan Ahmed

Hi @Marius Skoglund ,

In the Automation rule audit log, what is the error displayed ?

Marius Skoglund

Hi @Rilwan Ahmed ,

Unfortunately there are no errors in the log.

Schermafbeelding 2023-03-17 094054.png

Rilwan Ahmed

Hi @Marius Skoglund .

1. This could be because there is no team name found mapping to the value you entered.

2. Assuming Team is single select list, Try using the below lines.

"customfield_11449" : { "value": "option3" }

or

"customfield_11449" : { "id": 10112 }

Please refer this link for the syntax.

Fazila Ashraf

Hi @Marius Skoglund

Could you check on the rule details to see if the project scope of the automation is set correctly?

Marius Skoglund

The Team fields is the one corresponding with the Advanced Roadmaps plans and the teams, so this is a locked field, with values being pulled from the Manage Shared Teams page. As described here: Solved: Can someone tell me how to find the Team ID which ... (atlassian.com)

ID 191 is the only one I can find for this particular team.

Solved: Default value for Team field when creating new iss... (atlassian.com)

This is the original setup I used.

Marius Skoglund

Yes, this has been checked. The scope has not changed and the rule was working previously.

This is the setup used:

Solved: Default value for Team field when creating new iss... (atlassian.com)

Marius Skoglund

This was resolved. The workflow was changed and there was no Issue Created event firing on the create transition. Once added, automation is working again, and the team is set correctly.

Welcome!

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

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server

automation