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

"Request Type" field questions


Hi all, a couple questions:

1) How can I set the default value for field "Request Type" when creating an issue of type Incident.

2) I have an Incident queue to show All Incidents but it doesn't show the Incidents created with "Request Type = No request type" although I can see them using the All issues filter. Why? See images below:Screenshot_1.jpgScreenshot_2.jpg

2 answers

1 accepted

0 votes
Answer accepted

Hi @Paul Heath 

Question 1

As far as I know, you can't set a default value for "Request Type" - which is a locked custom field.

The alternative is to use an Automation Rule to populate empty Request Types - for example...

  • Trigger: Issue Created
  • Condition: Issue Fields Condition
    • Field = Request Type
    • Condition = is empty
  • Action: Edit Request Type
    • Request Type = <Default option here>


Question 2

I assume you're viewing this Queue in the "Incidents" sub-category of Queues.

It seems like to be in this Queue the Issue must have a Request Type, and must be an Incident. I tried to create a new Queue and search based on Request Type being empty and it shows 0 results (even though I created test Issues for this).

They do show in general Queues though - eg. "All Open Tickets"

It looks like this is a Bug which has been raised before, and the behaviour confirmed to be based on Request Types - see JSDCLOUD-9732 

So ideally, you wouldn't have any ticket raised without a Request Type :)



Yes, I'm viewing this Queue in the "Incidents" sub-category of Queues.

So if Issues must have a Request Type why does JSM allow  "Request Type = No request type" and how can we prevent it?



Hi @Paul Heath 

You'll need to either...

  • Create the Issues via the Portal (where Request Type is required) or...
  • Use the Automation Rule I suggested in my original Answer to set a default Request Type when it is left empty

You cannot make the field required at this point, but there is a feature request you can view / vote for - see JSDCLOUD-8406 

I guess it's allowed to offer the flexibility of created these Issues either via the Portal or using the internal "Create" button. You're also looking at different functionality between ITSM JSM Projects and general JSM Projects - this is a specific issue within ITSM Projects because they have categorised Queues, rather than just a general list of them.


0 votes
Jack Brickey Community Leader Jan 11, 2023

Hi @Paul Heath ,

when you say “incidents” are you referring to the ITSM issue “category” that Atlassian has presented in their implementation or do you mean you have created an Issuetype called Incident? Regardless, could you please provide the underlying JQL for your queue? My suspicion is that the JQL needs to be updated to include issues that do not have a Request type. Having said that, I would suggest that you try to resolve why issues are getting created without a Request type as this can present any number of problems that I have seen over the years. 

Incident is the Issue type.

The underlying JQL for my queue is "issuetype = Incidente ORDER BY key DESC"

I am creating the Incidents without a Request type to test what the differences are between Incidents with and without Request type. I didn't know this could be a problem, how so?

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events