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

Identify which request was created and then assign assignee based on that info

Muhammad Waleed_loxyqd

I have three different types of request.

- Content update

- Bug

- Change Request

I want to know which type of incident was created and then assign an assignee depending on that

Also, I want to change the assignee depending on the time of any action performed on the ticket.

Accepted answers

Kai Becker

Hi @Muhammad Waleed

welcome to the community and thank you for your question.

This can be done via Automation rule. I would recommend having a look at the following example: https://www.atlassian.com/de/software/jira/automation-template-library/rules#/rule/140670

The rule has several parts to match against issue data. You should be able to build you own rule using this example and checking for issue type instead of country.

Hope this helps to get started.

All comments

Kai Becker

Hi @Muhammad Waleed

welcome to the community and thank you for your question.

This can be done via Automation rule. I would recommend having a look at the following example: https://www.atlassian.com/de/software/jira/automation-template-library/rules#/rule/140670

The rule has several parts to match against issue data. You should be able to build you own rule using this example and checking for issue type instead of country.

Hope this helps to get started.

Muhammad Waleed_loxyqd

Hi @Kai Becker

Thanks for the info i already did try this but the issue the rule is not picking up the issue type by name. Let me know if i am doing something wrong because i checked the audit log as well and it said nothing to be changed here.

Screenshot 2024-02-15 at 12.56.46 PM.png

Kai Becker

Hi @Muhammad Waleed

is "Report a Bug" the issue type or is it the Request type?

Request types are based on issue types, but add a separate layer of configuration on top in JSM projects.

Also be sure to use Issue fields condition instead of JQL or smart value, as it will be faster and is a lot easier to use, because of the auto complete:

Screenshot 2024-02-15 at 09.17.50.png

Muhammad Waleed_loxyqd

Hi @Kai Becker Apologies to ping again i did as you told me but the transition rule is not adding any approver.

It shows me this error.

P.S I have added the rule details as well. Screenshot 2024-02-20 at 3.43.22 PM.png

Welcome!

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

Quick Links

Find more posts tagged with

cloud

automation

jira-service-management-cloud

jira-service-management