best practice for specific case?

I should have a little hint, we are a company with a couple of software products (3, maybe 4 in some time). Each of these products having a bunch of modules/components and services. How should this be structured in Jira?

3 answers

And where should we add customer reported bugs?

I would set each product up as its own project. Then create issues with a type of bug for each project.

Best practise is to have separate projects for each product. This way, management and searching for issues is manageable.

For every project, assign the users accordingly so that a user (A) could not see another user's (B)'s issue. At the very least, it provides some sort of security (unless you are making a public tracker where anyone can see all issues).

Further enhancements would be to not allow users to perform certain transitions such as Resolve Issues and Close Issues. It would be best to allow your employees to track this and provide resolutions themselves.

Hope the above tips help in your quest!

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,264 views 14 20
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot