The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Issue fields condition request type does not work

Gergely Márton
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 2, 2024

We have Jira service management, and we want to approve some of the requests automatically based on their requesttype, the issue type is not an option. The automation it is set like this: 

image.png 

The problem is: When we submit a request in this request type, the automation does not approve it. Instead it executes the last else block. I do not understand the problem here. I think the condition is set properly. 

Thank you for your help!

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Marc -Devoteam-
Community Champion
February 2, 2024

Hi @Gergely Márton 

Welcome to the community.

Please share you complete automation, as this will help community members to help you.

Also show the audit log details of the rule.

Gergely Márton
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 4, 2024

Thank you for your response!

 

We've resolved the issue, but for the benefit of others who might encounter something similar, I'd like to share the solution:

 

In Jira Service Management (Cloud), if an automation rule uses the request type of an issue, it cannot access the request type at the moment when the issue is created. Therefore, an automation rule with the 'when issue created' trigger cannot use the request type of the issue.

 

To work around this, I used a hidden field on the portal with a default value. The automation rule was able to interact with this field.

DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events