You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
This is Jehan from Jira Service Management Cloud with a new Feature Labs release.
We are excited to "Default Request Types", a new feature that will ensure that issues no longer lose their Request Type when they are moved or the issue type is changed.
To access this feature, simply click on "Project Settings" > "Features" and scroll to the bottom.
If you turn on this feature, whenever an issue is moved (or any other action is taken that causes the request type to be lost), the request type field is updated so that it is not null.
By default, it will select the first request type alphabetically. But you can override the default by setting the request type yourself.
This feature has been fully developed and tested. That said, we do not yet have the optimal experience nor functionality built, so it is currently a beta feature from a user experience perspective.
So, what will change?
I'd love to know what you think about this new feature. We'd love to hear your thoughts, whether positive feedback or constructive criticism.
You can comment on this post or leave us feedback in product (see the "Give feedback" icon on the bottom left of the image above). We read every single piece of feedback you leave and do use it to inform out decision making, so please don't hold back.
Looking forward to hearing from you!
Product Manager, Jira Service Management Cloud
5 accepted answers