nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Best practice for issue types and workflow

noa harel

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!

Comments

Pramodh M

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

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

new-to-jsm