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.
Hi there everyone
Could anyone perhaps share cind of 'best practice' workflow for technical support Requests? And which requests types does he use?
Does someone familiar with the use case of creating a linked issue in software and has some good tips?
will be happy To become wiser from your experience and shares!
Hi Noa - To me, it really depends on your process. Your workflow should mirror your process. If you don't like you process, then change that, but model your process on the tool.
Use of Issue Types for me comes down to how you want to handle different types of work (or even how you want to report on the different work). Different issue types can have different workflows.
Finally, screens fields can be mapped to issue types. So you can narrow down the fields that are seen on the screen by issue type to make it less cluttered for the user.