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

if a request type has a specific value it must prevent an issue to be closed

Hi all,


We have JSM running in the cloud and all is working fine. We have one challenge that we need a bit of help. There are 2 ways to create tickets:

1. using the portal

2. by E-mail.

Our challenge is that if an issue is created using an E-mail we have to change the request type to get the proper classification of the issue (including the correct SLA for that request type). What good to know is that we have multiple JSM projects.

My goal: To prevent issues that have the request type "Emailed request" to be closed. 

I already tried to add a condition in the workflow:

The field Request Type will have to be not equal to value 'Emailed request'. Compared as String.

But this condition is not working sadly. 

Is there any smart thing that we can do?

1 answer

1 accepted

1 vote
Answer accepted
Patrik Korovsky
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Nov 25, 2022

Hi @Reinier

I see many solutions depending on how the email requests are closed.

The easiest one I can think of is to copy the workflow of another request and apply it specifically to the "Email Request" issue type, then set the "Always False Condition" (Always fails) for the close transitions.

If you share more details, I will be happy to work out the best solution for you.



let me try to explain a bit more:

If an Emailed request comes in we change the request type form Emailed request to something else. 


Screenshot 2022-11-28 at 08.40.37.png

And all other request types have an SLA (Emailed request is the only exception). I am afraid that if we create a second workflow that we can only adjust this if we "move" the issue. And moving is something that I would like to avoid because it introduces more risks (like moving the issue from customer a to customer b).

So I hope that there is an option to prevent the issue (Emailed request) to proceed.

Looking forward to your suggestions and options.


With kind regards,



Patrik Korovsky
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Nov 28, 2022

Hi @Reinier

I propose to set up a condition, that blocks (status transition will not be visible) transitioning  the issue from the "create" status if the Customer Request Type = "Emailed request".

We will need to get the ID (key) of the request type

This can be done by first acquiring the ID of a ticket and then passing this onto an endpoint.

  1. Open the issue, that has the "Emailed request" Request Type active
  2. Clicking the "move" option in additional options under the ticket
  3. You will see the issue ID of the at the end of the URL
  4. Go to "" in your browser
  5. In the returned JSON, under "validRequestTypes" search for the "Emailed Request" type and find it's "key"
    • For this step I recommend to use a formatter, such as
    • Also note the portalKey, that you will need in the set up

Workflow set up:

For each transition from the "Create" state we will need add a condition, that it cannot transition. This applies to all transition you do not want to be visible in the example below I would set it up for "To Analysis" and all "to All" transition such as the All -> Discarded.

  1. Add a new "Value Field" condition with the following set up
    1. Field: "Customer request type"
    2. Condition: "!=" (Not equal to)
    3. Value: "portalKey/key"
    4. Comparison Type: "Option ID"

Let me know if you have any questions or this solution does not suit you.


Hi Patrik,


Good suggestion. I hope we can add multiple portalkey/key (for each different support project we have that shares the same workflow).

I will test and report back here.




Hi Patrik,


This works really nice thanks a lot. :)

It took some time to figure out the json formatting stuff but we got it.

Again thanks.





Like Patrik Korovsky likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events