Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Automated Transition Issue Type from SR to Incident

I want to use automation for Jira for doing automation on email send to SD.
By default I have that when email is send to SD then Service Request is created. But e.g. when the email subject has some word (WARNING) I want to change issue type to Incident, change Priority etc.
I have success with changing the issue type to Incident, but there is left status from Service Request (Waiting for support), SLA is not updated and I am not able to start working on ticket and resolve it (missing buttons). This is probably due to bad mappings, but I am not able to do it automatically.
I tried automation Transition the issue - Destination status - Open or specific transition but this doesn't work.
Is there any way how to do it?
I am Jira admin.

In Audit Log:
Transition issue
No transitions found for user. Ensure that the rule actor has permission (including issue security levels) to see issue and perform transitions.




1 answer

0 votes

Hey @Ladislav Esterka 

Did you solve this problem you had, or you need further assistance? If yes, we can see it together. Let me know!

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events