Advise needed on Project Setup and Usage

Hi, I'm currently reviewing Jira to replace our in-house issue and project task tracking system. With our current system we break down 'general' issues into 15 areas, usually business area, and have a unique code for each. For example 001 - General Support, 002 - Business Area 1, 003 - Business Area 2 etc. Moving onto Jira I was wondering if anyone would recommend having 1 project per business area or having 1 project with a component/category for each business area? I like the idea of the latter as it just seems simpler, but I didn't know if this would cause any performance problems as most of the issues/requests etc (~ 2k/year) would be under 1 project. Actual projects, i.e. none support related work, will have their own project and set of tasks etc. Thanks in advance, Mj

1 answer

1 accepted

0 vote

I would lean towards the second for your case here, but I'd look at the human side and think about reporting as well.

First, components are editable by the project admins, so, if you make use of versions or delegate the user maintenance to project admins, you might find they go adding/editing/deleting components

Second, components are multi-select. You can therefore say "issue belings to General, Business area 4 and business area 7". That might not be valid for you

Both of those are simple to fix - use a custom field instead. You can have a single-select, or multi-select, as appropriate, and only Jira system admins can maintain the list of options.

For the human and reporting side, think about how you'd like your people to work. If each business area has a team of people who rarely work in other areas, then I'd be strongly tempted to have a project per business area. But if it's more about tracking "who wants it" or "where it came from", and your workers are all working together and don't really care that much about business area, then you'll find a single project far more easy to handle. The business area field remains useful for reporting, but the workers might not be bothered about it.

For what it's worth, there's a project here with over 90,000 issues, generated over 5 years. The only problem we've got with volume is slightly slow searches sometimes, and the "closed" statistics makes everything else look silly because it's always 99.99%...

Thanks Nic. It does just seem to make more sense to have a general catch all as it'll make life easier. Also having the custom field sounds like the correct way to go as well. I just needed that extra push. Thanks.

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,183 views 13 19
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