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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,556,701
Community Members
 
Community Events
184
Community Groups

How do I remove 'no request type' from Request type?

Dorien Reynders
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!
Mar 20, 2023

I defined several issue types (incidents, changes, ..)  and request types (report security incident, report incident) .  

However, the option to pick 'no request type' (see print screen) should not be an option to an agent creating a issue.  

I defined default request types for every issue type, but still this option remains. 

Is there a way to remove/hide/delete the type? Or at least put it at the bottom in the request type list, as a 'last' option?

Kind regard,

Dory

Screenshot 2023-03-20 161825.png

 

1 answer

1 accepted

2 votes
Answer accepted
Dave Mathijs
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 20, 2023

Hi @Dorien Reynders welcome to the Atlassian Community!

In the back end, check if this is a request type with the name 'No request type' defined and visible in the request types. If yes, you can hide it from the portal.

Secondly, avoid that agents create Jira Service Management issues directly via the Create button. They too need to go via the portal to create an issue for themselves (as a customer) or for someone else (who calls the service desk for example).

If you don't assign a request type to an issue, then the issue won't be visible in the portal (as mentioned in the description of that Request type).

Dorien Reynders
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!
Mar 20, 2023

Thanks for your quick response! So basically: it is impossible. :) 

It is not visible in the Portal. It only applies if you push the 'create' button in your top-menu. Since 'no request type' is the first suggestion in the dropdown and not linked with any request flow, it is prone to mistakes. 🤷‍♀️

A customer cannot ask for a change request within our company. Changes of applications are managed and handled internally (Product Owner). Therefore, not everything can be added to the portal view. 

Kind regard,

Dory

In your screenshot it defaults to the first available option "Request Change for Existing Application" of your Issue Type - [System] Change.  This behaviour is the same in our project. 

I think the "No request type" is there because when the Issue Type is changed (i.e. [System] Change -> [System] Incident), this "No request type" is being defaulted, until user manually select the proper Request Type after changing the Issue Type.  

I do agree that if this can be at the bottom of the list, it might provide better user experience, or if there is an option to hide it, or even hide other request type we think might not be required.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events