Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Request Type not showing on screen called during transition

I'm able to create a new screen, populate it with several fields (including Request Type), and then set it as the screen for a particular transition, however when the screen shows, all fields are there with the exception of the Request Type. Did I miss a step? Or is this tied to the Request Type field itself somehow? 

2 answers

1 accepted

0 votes
Answer accepted

Yes, there's a slight oddity here in that Request type is implemented so that it looks like a field and so you can put it on screens.

It isn't a field you can change, it's a structural attribute and it determines other things, so you can't just change it as though it were a field.

Hi, I'm trying to do the same. I have a business role that acts as Triage for all incoming cases. If Request Type doesn't show in a transition, do you have any other options where I can remind them so that cases get routed to the proper issue category?

Like akhalifah likes this

I'm stuck now with same situation as Jason. Any Ideas ? don't want end up with creating a new list field for this purpose unless its the last option. any ideas please ? 

Hi, I had to pivot my approach. Maybe for the better. This work around removes the need for request types in transition screens. 

Inspired by this article: Automatically set Customer Request Type When Issue is Created via Jira | Jira | Atlassian Documentation

...I was able to come up with some legacy automation rules that will automatically assign request types. From there, I create a 'triage' queue in each issue category where have automation dumping requests. 

This removes the need for agents to select a request type during transition and also saves the agents from clicking back and forth between Top level navigation of Queues and (Incidents or Service) requests. 

To still catch cases that were created improperly, I've created a "Lost and Found" queue in the Queues category. 

This probably won't work for everyone's scenario and request types will have to be carefully crafted, but it works for me. So thought I would share. 

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Jira Service Management

JSM Jira Automation: How to Send SLA Breached Notifications

Hi Everyone, In   this tutorial,  we will show you how you can monitor an SLA, and send notifications before or after the SLA has been breached.   SLA Threshold Trigger The SLA t...

762 views 5 13
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you