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; } } }

JIRA Best practices for projects managed by different teams

lshaigorodsky

Hi,

Working on different projects by different teams we starting to see too many projects in work by different teams

Can you please recomend approach that would allow us to identify and filter projects only relevant to specific team. We intially were thinking to include it in project name but this idea was not working very well

We want to basically use the same JIRA instance, while more or less segregate projects, rapid boards, issues, etc between team (if these projects are not really relevant for these teams)

Thank you!

Accepted answers

Amy Biasella

I agree with Harry in that your instance might be getting too cumbersome.

That said, customizing dashboards through gadgets can go a long way. You can put multiple rapidboards on one dashboard, muliple activity streams showing you updates from only the projects you're interested in etc.

All comments

Vishwajeet Singh

Defining project category might be a way to categorise the projects.

Harry Chan5

Project categories might help, but won't help with searching, boards etc. You might have gotten to a point where your instance is so big that you rather have separate instances - potentially 1 for each team or branch/section of the organization.

Amy Biasella

I agree with Harry in that your instance might be getting too cumbersome.

lshaigorodsky

Thank you, it is very helpful!

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-cloud