Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


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!


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
Community Members
Community Events
Community Groups

Grouping per project

We have multiple project consisting of dozens of micro-applications in total and many more services.

How can we group them, ideally by project, or even by label or component?

Right now it looks like the list of services and applications can easily grow out of hand and become cluttered. 

2 answers

Hi Andrew

The situation is as follows. 
We have multiple projects, hundreds of repositories, multiple teams (some working on the same project),
Imagine you're working on project A, and you get the compass link. You'll see dozens of applications and only some of them will be from project A, while the others will be of no relevance to the user (they will be junk in this context).

This would be even worse in the case of the service where there could be hundreds of services, while only some of those will be related to project A. 

Option 3 doesn't work for us since multiple team can work on the same project. 

Regarding option 1: labels are cute but I have no idea how to use them (I can set them but I can't click them afterwards to filter by label)

Option 2 feels like a bit of a hack but it looks like a good enough workaround for now.

How do you you guys use it on your side? You said you have 1500 micro-services.

Let's say a developer on your team wants to look into the Atlassian status page. If over 90% of the micro-services and micro-applications in there are for Jira, Confluence and some of the bigger projects, how will that developer not drown in a sea of irrelevant items? 

1 vote
Andrew Freedman
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 17, 2022

Hi Mircea,

Compass has a few options which might be suitable here.

  1. Labels — you could set a label with the name of your project on each of the components related to it. You're then able to assign Scorecards to labels, which would let you define policy at the project level.
  2. The "Other" component (or maybe "Application" if that's more intuitive for your situation) — you could create an "Other" for each project and have it depend on all of the components related to it. This would allow you to examine the Activity Feed for the project and see all of the upstream dependency events in one place.
  3. Teams — you could assign a project team to each of the related components. This would allow you to view the aggregation of Scorecards for all of the project's components on the Team view.
  4. Some combination of the above, depending on which features you're looking for.

Could you share a little more about your situation? Do you need the ability to use Compass features across arbitrary sets of components? Is "findability" a concern without those extra waypoints from projects? Something else entirely? :)

— Andrew

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events