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,557,331
Community Members
 
Community Events
184
Community Groups

Best practice for issue types and workflow

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!

 

 

2 comments

Pramodh M
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 14, 2021

Hi @noa harel 

There's content from Atlassian to start with

https://www.atlassian.com/software/jira/guides/getting-started/best-practices#best-practices-for-epics-and-stories-in-jira

Let me know the requirements from your end!

Thanks,
Pramodh

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 14, 2021

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. 

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events