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

JIRA Automation

John Nyamiwa_3iz4pm

Hey guys. I have been trying to set up an automation rule on Jira where when an issue is raised on the service project and a component selected, the component lead is automatically assigned the issue.

Currently when I create the issue, I still have to go inside Jira to the assignee tab and select automatic for the issue to be assigned. Any one know how I could automate this?

Accepted answers

Vamsi Kandala

Hi @John Nyamiwa

Welcome to the community!

You can create the automation rule:

Select the trigger as 'Issue created'
Select 'Issue fields condition' and select the 'Component/s' field
Select the 'Condition' as 'contains any of'
Select the relevant value in the 'Value' field
Select the 'Edit issue' action
Select 'Assignee' and select 'Automatic' in the list of options

Enclosed the screenshot for your reference.

Hope this helps.

Thanks,
Vamsi

Component assignee.png

All comments

Vamsi Kandala

Hi @John Nyamiwa

Welcome to the community!

You can create the automation rule:

Select the trigger as 'Issue created'
Select 'Issue fields condition' and select the 'Component/s' field
Select the 'Condition' as 'contains any of'
Select the relevant value in the 'Value' field
Select the 'Edit issue' action
Select 'Assignee' and select 'Automatic' in the list of options

Enclosed the screenshot for your reference.

Hope this helps.

Thanks,
Vamsi

Component assignee.png

John Funk

Hi John - Welcome to the Atlassian Community!

Unless I am missing something, why don't you edit the Component to tell it to assign the issue to the Component lead?

Joseph Chung Yin

@John Nyamiwa -

Welcome to the community. I agreed with @John Funk suggested of using component lead (easiest) if you want the issue to be assigned to the lead automatically.

However, this will work if component is selected at at issue creation time + only one component is selected (NOTE - Component/s can be one or more for each issue).

Are you populating the component at issue creation time? If so, then no further automation is required by just using the component lead as the default assignee setup.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

John Nyamiwa_3iz4pm

Thanks @John Funk I already did that but for some reason the rule doesn't seem to work automatically Screenshot 2023-01-31 at 15.22.27.png

John Funk

Did you check the history of the issue? Is it maybe getting set and then overwritten by something else?

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management