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 Rule on Issue Create limit by issue type

Ann Rumenapp

I wrote an automation rule triggered by issue creation to default the Team field value. I want this rule to run on issue types of story, task,& bug; however I do not want team field to default on issue types of risk, issue or decision. Is this possible?

Accepted answers

Mikael Sandberg

Yes, that is possible. All you need to do is add an condition that checks the issue type. If the issue type is not part of the list the automation will not proceed past that step.

All comments

Mikael Sandberg

Yes, that is possible. All you need to do is add an condition that checks the issue type. If the issue type is not part of the list the automation will not proceed past that step.

Ann Rumenapp

I tried to add a condition, but it doesn't work. Between the Issue Create and Setting the field. The condition I used was 'If issue matches JQL' wtih the JQL of issuetype in (Story, Bug, Task, Spike, Sub-task, "Dependency Task", "SecurityRisk", "Technical Debt", Improvement, "Production Support").

When I create a story the team field does not get set. Can you tell me what condition I should use?

Mikael Sandberg

That condition looks correct. If you look at the audit log, what does is say? Does it pass the condition?

Ann Rumenapp

Found it - That audit log is awesome,

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