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

Difference in Automation Rule Options: Team-Managed vs Company-Managed Projects?

Lin Classon_8e7fqd

Hi everyone! I’ve noticed a difference between team-managed and company-managed projects when setting up automation rules in Jira. Specifically, in a team-managed project, I see options to both assign the newly created work item and to link it to a parent item at the time of creation. However, those same options don’t appear when I try to replicate the rule in a company-managed project (screenshots attached).

Is this expected behavior, or am I missing a configuration setting somewhere?

Appreciate any insights - just trying to confirm I haven’t lost my mind. Thanks in advance!

team managed.png Company managed.png

Accepted answers

John Funk

Hi Lin - Welcome to the Atlassian Community!

Yes, those are available for Company-managed, also. Click the Choose fields to set dropdown and you should find them.

BTW, the More options is for putting in JSON code.

Let me know if you have trouble finding them.

All comments

John Funk

Hi Lin - Welcome to the Atlassian Community!

Yes, those are available for Company-managed, also. Click the Choose fields to set dropdown and you should find them.

BTW, the More options is for putting in JSON code.

Let me know if you have trouble finding them.

Bill Sheboy

Hi @Lin Classon -- Welcome to the Atlassian Community!

Yes, and...to the suggestions from @John Funk ...

Both of the rules you show using the Work Item Created trigger. There is a known timing defect with that trigger where the rule can sometimes start before all the field data is ready. This can cause symptoms of unexpected behavior, including errors or conditions to fail, etc. This defect is regardless of the project type.

The mitigation for that is to always add the Re-fetch Work Item Data action immediately after the trigger, and before other steps. This will slow the rule slightly and reload the data before the steps proceed.

And because of that same defect, I recommend not using the new feature to add conditions directly to the trigger when using Work Item Created. Instead, use a separate condition step, as in your first rule shown.

The Atlassian team is aware of this defect and according to this recent post, they are actively working on changes to address this, although there is no resolution timeline communicated.

Kind regards,
Bill

Lin Classon_8e7fqd

@John Funk Thank you so much! And I am so embarrassed for having missed the big giant gear button.

@Bill Sheboy thank you for the heads-up and also the link to the article. Off to studying now. The new feature "Branch at the same time" worked! THANK YOU!

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

automation