youngmon/atlassian-qna huggingface dataset:
Why is there a limit of 5 repository links per component?
Asked by Tony Urso:

I imagine there's a reason behind the limit that I'm missing, but looking at the component types I have to imagine there's an application or monolith out there that's made up of more than 5 repos.

This limits the flexibility of Compass and is requiring our team to look into workarounds. Less we may end up needing a 3rd party tool for service/repo management instead.

Would love to know what others have done to work with/around this or if there's something I'm missing.

Thank you!


Answers:
author: Andrew Freedman
body: Hi Tony, we recently increased the limit for each link type from 5 to 10; let me know if that change hasn't worked for you though.

Can you tell me a bit more about the application/monolith model spread out over multiple repos that you're describing? My initial reaction was that those would be best modelled as seperate components in Compass, which would allow you to track ownership/events/metrics/etc discretely --- and that starts to feel a lot like a decomposed piece of software rather than a monolith. We're always really keen to hear about different ways of organising code \& projects. :)

Also, +1 to [@Alfred](/t5/user/viewprofilepage/user-id/5004810)'s suggestion --- that's my recommendation for link types like documentation. If you have dozens of docs, maybe put them into a Confluence page and link to that single page instead of trying to reference them all in Compass discretely. Repos are a little different however, as linking them in Compass allows us to ingest events and metrics generated by the SCM.


author: Alfred
body: Try creating a link to a file which lists out every repository link.

comments: author: Tony Urso
body: Hi Alfred,

Are you referring to [configuration as code](https://developer.atlassian.com/cloud/compass/config-as-code/what-is-config-as-code/) or some other kind of file?


Tags: component

limit

link

repository
Has anyone worked with the change compass?
Asked by Tushita Sarkar Biswas:

Has anyone worked with the change compass?


Answers:
author: Dave Liao
body: [@Tushita Sarkar Biswas](/t5/user/viewprofilepage/user-id/5111533) - hi Tushita!

Can you elaborate? What's "the change compass"?

comments: author: Tushita Sarkar Biswas
body: that's too a product of atlassian aiming at distributed architecture...


author: Dave Liao
body: [@Tushita Sarkar Biswas](/t5/user/viewprofilepage/user-id/5111533) - if you're looking for people who have used Compass, I would check I the Compass group! <https://community.atlassian.com/t5/Compass/gh-p/compass-alpha>


author: Tushita Sarkar Biswas
body: yes...very helpful..thanks a lot [@Dave Liao](/t5/user/viewprofilepage/user-id/523242)


Tags: off-topic
How to get start and end deployment times visualisation?
Asked by Pete Capra:

Hi there,   

We've started pushing deployment information for a component into Compass and was hoping to get a visualisation in a component's activity timeline that looks like the one bloew from on the Compass site, where the start and end of a deployment is marked by the green line.

I've tried to do this two ways, both unsuccessfully - using the startedAt and completedAt time-date in the deployment event in the json payload where the state was 'SUCCESSFUL' and then also by sending two separate events, one for the state 'IN PROGRESS' with the lastUpdated time being the start time and then other event with the state 'SUCCESSFUL' with the lastUpdated time being the completed time. It seems though that it only records the end time with a single green solid tick, not with a line drawn between the two like the visualisation below.   

Am I missing something?  

Cheers,   

Pete

![Activity feed screenshot](https://wac-cdn.atlassian.com/dam/jcr:514b5ddf-cde3-4296-85dc-9f8e2283812f/Record%20Change.png?cdnVersion=620)


Answers:
author: Dave Parrish _Atlassian_
body: Hey [@Pete Capra](/t5/user/viewprofilepage/user-id/4999715) ? It's Dave with the Compass product team. You're doing everything right! It's just that you've encountered a case where our marketing images are slightly outpacing what we've implemented in the product.

Currently, events such as deployments are represented as a single point on the activity timeline. In the future we intend to add duration lines to events, with both a start and endpoint. Apologies for the confusion here!

Out of curiosity, what tool are you sending deployment events from? Any other issues you encountered setting up the events pipeline?

comments: author: Pete Capra
body: Thanks [@Dave Parrish _Atlassian_](/t5/user/viewprofilepage/user-id/853503) - I thought that may be the case. That's all good. I'm working on a little Docker image that I hope to open-source which we'll use initially with helm + k8s as a post-deploy hook to notify Compass of the deploy. The same image will also slot into our deploy processes where we don't use helm as well.   

While you're here, it would be really nice to get some more detailed doco on json payload for sending events, especially deployment events. It's not super obvious what the different updateSequence numbers are for as well as the pipeline url vs deployment url. The doco says they are required, but I reckon the less required here the better.   

No real issues other than the one I shared. Compass looks really promising and if we can get it integrated well I can see it becoming very sticky :)
Why are scorecards restricted to component types?
Asked by Jan-Hendrik Spieth:

So far, we have the option of creating scorecards *per component type*. We can then limit the scorecard down further to certain components, e.g. by label. But the basic restriction is by type.

![Screenshot 2022-11-01 100625.png](https://community.atlassian.com/t5/image/serverpage/image-id/223512i0D49634BE4D57ADD/image-size/large?v=v2&px=999 "Screenshot 2022-11-01 100625.png")

After the first few experiments with scorecards (basic health metadata), we find ourselves copying scorecards just to have them available for several component types.

What's the logic behind this?

**Why should scorecards by specific to component types? Why now allow us to define basic scorecards that are applicable to all component types?**

To give you an example, we were thinking about checking component ownership like so:

* field - has owner
* metric - sth that rings an alarm when a component is "orphaned" due to staff leaving the company (last Jira login date, or user active/deactivated status - we're not sure yet this can be done, but that's our idea right now).

This "ownership" scorecard is applicable to all component types.


Answers:
author: Patrick Hill
body: Hi [@Jan-Hendrik Spieth](/t5/user/viewprofilepage/user-id/386132)

Thanks for reaching out! I'm the Product Manager for Scorecards and would love to chat more about this - mind finding some time using [https://calendly.com/patrick-atlassian/let-s-talk-about-compass?](https://calendly.com/patrick-atlassian/let-s-talk-about-compass)

When we started out to build Compass, we found that specific types of Components had certain fields that only applied to that particular domain - an example here is on-call for Services.

As we've expanded our thinking over time and made component types more flexible with Metrics and Custom Fields, we realise that you may want to have a Scorecard across multiple Component types. I'm super curious about how else you'd want to use Scorecards - targeting on different properties or fields, or new types of criteria so if you or others have ideas please let me know!

Thanks,

Patrick

comments: author: Jan-Hendrik Spieth
body: Hi [@Patrick Hill](/t5/user/viewprofilepage/user-id/502126) thanks for your reply.

We've just started with Compass! And quite some of our experimental components are external. That's a bit special and not what Compass has been built for it seems.

But, let us do a bit more experimenting with metrics and scorecards. I'll then get back to you!
Is there a way to get a graph of a Compass Metric over time?
Asked by James Wilson:

My use case is that I've created metrics for things like: unit test coverage, adoption of typescript, use of inline CSS styles - all things I'd like to increase or phase out of the codebase.  

I've set up Compass API calls in a pipeline to update these when PRs are merged, which is working fine. I'd love to be able to see how they change over time though - for example how the migration of a project to typescript is going?  

I guess my questions are 1. Is this currently possible? and 2. If not, how can I request it as a feature?

Thanks!


Answers:
author: Patrick Hill
body: Hi James,

I'm the Product Manager for Scorecards and Metrics and we're exploring this area currently. Can we find some time to chat about some ideas we have for this?

Here's my calendly: [https://calendly.com/patrick-atlassian/let-s-talk-about-compass?month=2022-11\&date=2022-11-14](https://calendly.com/patrick-atlassian/let-s-talk-about-compass?month=2022-11&date=2022-11-14)

Thanks,

Patrick

comments: author: James Wilson
body: Thank you Patrick :) Have added something!


author: Piotr Gajowniczek
body: Hi, I was wondering the same regarding charts for tracking history of metric values.

What was the outcome of your discussion? Is there any way to see such chart or are there plans to add such feature in the future?


author: Patrick Hill
body: Hey [@Piotr Gajowniczek](/t5/user/viewprofilepage/user-id/5188595)

We'll be adding this feature this quarter into the product, so stay tuned!


author: Daniel Konold
body: any news on that? I am also wondering if there are options, like for the "derived" metrics, to get averages displayed, smth like the average hours/week to deploy into production


Tags: graph

metric
Have the Github integrations been updated?
Asked by John Medina:

I noticed when I added Github repository addresses to some of my components that new metric fields (i.e. Build Success Rates) are now being displayed.

Are these new features? If so, is there any documentation surrounding them and how they are populated? Currently, the numbers being returned are unusual (i.e. the build success rates are always 100%, which contrasts with my own results on my Github Workflows).

These features are exactly what I've been looking for and would love to integrate them properly into my work.


Answers:
author: Dave Parrish _Atlassian_
body: Hey [@John Medina](/t5/user/viewprofilepage/user-id/4996391) ? You've spotted some changes with the GitHub integration that are so fresh we haven't even documented them yet! In recent days we've added some additional metrics that get automatically calculated for components that have a GitHub repository linked. The full list of metrics we calculate for GitHub are:

|----------------------|-----------------------------------------|-------------------------------------------------------------------|
| **Metric**           | **How it's calculated**                 | **When it's calculated**                                          |
| Open pull requests   | Current value                           | Each time a PR is merged to the default branch                    |
| PR cycle time        | Averaged over the last 10 pull requests | Each time a PR is merged to the default branch                    |
| Build success rate   | Averaged over the last 25 builds        | Each time a build is completed on the default branch              |
| Build time           | Averaged over the last 10 builds        | Each time a build is completed on the default branch              |
| Deployment frequency | Weekly average for the last 4 weeks     | Each time a deployment is completed to the production environment |

We'd like to help you diagnose what's going on with your build success rate. Just click the "Give feedback" button in the top right navigation of Compass, and we can follow up to help you figure it out.

Glad you are finding these metrics useful!

comments: author: John Medina
body: Hi [@Dave Parrish _Atlassian_](/t5/user/viewprofilepage/user-id/853503), I think I figured it out. The failing builds in our workflow all exist in the feature branches, as opposed to our default \`master\` branch.  

I do have a question as to what classifies as a \`build\` being completed though. Is this tied to the workflow actions being run on the repository's default branch?


author: Dave Parrish _Atlassian_
body: Hi [@John Medina](/t5/user/viewprofilepage/user-id/4996391) - Regarding your question about what classifies as a "build" - Yes, you've got it right. Specifically, we're listening for GitHub's [workflow_run](https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#workflow_run) event, which occurs when a workflow finishes. We only listen to this event on the default branch of the repository. When that happens, we register a build event in Compass.

Hope this helps!


Tags: github

integration
Not able to add more than 10 metrics on a service and application in compass.
Asked by Anupama .:

Currently I am try to add metrics card on service.

But when its exceeding more that 10 its starts giving below error says Error creating metric source. Please refer the attached screenshot.

![Compass_metric_error.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/216648i83AE8F870BBB1F70/image-size/large?v=v2&px=999 "Compass_metric_error.PNG")


Answers:
author: Taylor
body: Hey [@Anupama .](/t5/user/viewprofilepage/user-id/5022017) , thanks for raising this!

So we do have an internal limit at the moment of 10 metrics on a given software component. Apologies the error message does not make this clear.

This was simply part of being an Alpha product and setting some constraints to start with, both from a performance POV and a user experience POV via the design.

We are happy to raise this to a higher upper limit, but would love to learn a bit more about your use case. How many metrics are you expecting to add to a component? What would be an upper limit you are happy with?

If you have 30 minutes, grab some time to talk with me about Compass and your use cases. This helps directly inform our roadmap and what we decide to build for you!

<https://calendly.com/tpechacek/compass>

Cheers
Activity Monitoring for Components
Asked by Isaac Petersen:

We are trying to integrate Compass as a dashboard to observe different environments for our builds. I had added the deployment and name tags to the bitbucket-pipeline.yml file under the branches in the repository for one of our applications![A16CE28E-72BC-48A0-8AEE-BD980AE047CB_4_5005_c.jpeg](https://community.atlassian.com/t5/image/serverpage/image-id/213079i0C5C9F4E98345937/image-size/large?v=v2&px=999 "A16CE28E-72BC-48A0-8AEE-BD980AE047CB_4_5005_c.jpeg") and once the build had succeed, nothing populated in the activity tab.

![9C5EB9DC-852A-4B40-B06F-07776866BEE5_4_5005_c.jpeg](https://community.atlassian.com/t5/image/serverpage/image-id/213080i8746D66455DA600A/image-size/large?v=v2&px=999 "9C5EB9DC-852A-4B40-B06F-07776866BEE5_4_5005_c.jpeg")

Was wondering if I could get some help with the environment integration.

Thanks


Answers:
author: Dave Parrish _Atlassian_
body: Hey [@Isaac Petersen](/t5/user/viewprofilepage/user-id/5017302) ? It's Dave with the Compass product team. Currently, Compass filters out deployments that aren't targeting the \`production\` environment.

So just update the \`deployment\` line in your script to read:

```
deployment: production
```

And you should be all set!

comments: author: Sarah Bland
body: Hi [@Isaac Petersen](/t5/user/viewprofilepage/user-id/5017302) ! Sarah here from the Compass engineering team. A quick tweak to what Dave mentioned above - in order for deployments events to be picked up, the **name** of the environment does not need to be "production", but the environment needs to be of **type** production. More information about environment types in Bitbucket pipelines can be found here: <https://support.atlassian.com/bitbucket-cloud/docs/set-up-and-monitor-deployments/> under "**Step 1: Define your environments**".
REST API to create / update / delete projects and goals
Asked by Florian Royer:

Hi,

Is there any plan for having a REST API or JIRA automations to be able to create an Atlas Project automatically and post updates on it based on some Confluence or JIRA objects?

We'd like to create automatically an Atlas project when a JIRA issue representing a project is created. So, we plan to do it through REST API or Automations, whatever seems easier.

It's a bit frustrating to see the potential of Atlas, but seeing that it isn't opened...

Regards


Answers:
author: Mark
body: Hi Florian,

Great question! The team is currently working on our APIs though I can't yet provide a date when they'll be widely available. We totally understand how important this feature is for many users.

As you note, another way of achieving this would be for us to integrate more deeply with Automation in Jira and Confluence, which is also on our longer term roadmap.

Thanks,

Mark

comments: author: Victor Babenko
body: Any way to get into a beta for the API if you are planning to do one?


author: rorteg
body: I would also like to sign up for the beta


author: Anthony Navarre
body: Also interested in APIs \& integrations (like jira automations) with Jira.


author: Fitzgerald_ Jeffrey
body: Count me in for a Beta Trial as well - we have been using Atlas in tracking all our Projects and would love a way to integrate with an API to display the data.


author: Kshama Joglekar
body: Please count me in for beta trials!


author: Eleanor Mallory
body: Very interested in APIs and automations for goals!


author: Orlando Kelly
body: Any updates on the atlas api, we really need this or have this in automation to create projects automagically ,
Ability to hide empty / missed Atlas updates
Asked by Mark Chaimungkalanont:

Some projects don't need a weekly update or there's no progress each week, so you end up full screens of noise e.g.

![Screenshot 2024-01-10 at 1.21.41?pm.png](/t5/image/serverpage/image-id/299784iF044E202F1B9A1AB/image-size/large?v=v2&px=999 "Screenshot 2024-01-10 at 1.21.41?pm.png")

I can see a case for having one call to action for "Last Week"'s lack of updates but the "Previous updates" shouldn't just replicate the text and should have the no update sections hidden or collapsed


Answers:
author: Mark
body: Hi Mark,

Great feedback! We totally agree and have been exploring ways to collapse multiple weeks / months of no updates on a project or goal. We're also looking at collapsing multiple projects with no updates on the feeds views. I'll work with the team to prioritise these improvements from our backlog.

Thanks,

Mark

comments: author: nicolevonvon
body: It would also be great to be able to set the update time - we update our ongoing projects every 2 weeks aligning with our sprints. Updating weekly would be noise for the stakeholders. This we only do if a specific decision was made.


author: Tyron Jardine
body: Hi Mark, any update on the ETA of this feature? We also have multiple projects have have these "No update was posted" posts, which clutter the project page.
Link Advanced Roadmap plan to Atlas work tracking (or initiative)
Asked by Chris Barlow:

In many cases, we structure a project to be made up of several Epics. The Epics roll up into a plan.

Currently, I can only see functionality to link and sync a Atlas project 1 to 1 with a Jira Epic.

I would love the ability to link a Jira Advanced Roadmap plan to syncronise the dates into the project.

Or to simplify, if I have a hierarchy in Advanced Roadmaps of Initiative -\> Epic -\> Story -\> Sub-Task, then I would like the dates of the initiative which have been rolled up from the plan to be the dates synced.


Answers:
author: Mark
body: Hi Chris,

Thanks for the feedback. To check my understanding, is your requirement to sync an initiative with a the work tracking link in Atlas? If so, we actually support that today. We actually support syncing epics and all hierarchy levels above epics to Atlas projects.

Or, is your need to sync the start and end dates from an Advanced Roadmaps plan as a whole? We don't support that today but are continually working to improve our integrations, so I can share that need with the team.

Thanks,

Mark


Tags: advanced-roadmaps

jira-software

roadmap
How to remove Atlas?
Asked by Michail Bashlykov:

We tried a new product (Atlas), but we were not interested in it. How can we refuse a product?


Answers:
author: Robert Wen_ReleaseTEAM_
body: If you have access to the billing details of your organization, you can cancel the subscription. Documentation is here

<https://support.atlassian.com/subscriptions-and-billing/docs/cancel-a-subscription/#>


author: Mark
body: Hi Robert,

Apologies for the late reply - we're still catching up on community posts after the holidays. We're sorry that you haven't found Atlas meets your needs. If you do wish to remove it, you need a user with access to Cloud Administration to go to Billing and then select "Manage" for Atlas. There will then be an option to cancel the subscription and remove Atlas from the site.

Thanks,

Mark


author: Carlos Garcia Navarro
body: Hi [@Michail Bashlykov](/t5/user/viewprofilepage/user-id/4309887) ,

I'm just curious, why didn't you like Atlas? Atlas has a free plan that allows to do a lot of project tracking, goal tracking, communication and reporting. And since it's free, it doesn't incur extra cost. I'm just pointing it out in case the cost is the issue. I started evaluating Atlas a few months ago and it's becoming my favorite Atlassian product!

comments: author: Dave B
body: It hijacks the main search, and for some teams, is pointless. Probably using it wrong, but it just appears to get in the way and adds zero value for us.


author: Carlos Garcia Navarro
body: Of course it's up to you, but I'd recommend to check with the Atlassian team, maybe you could get a demo or at least discuss your use case. It's such a nice tool (my personal opinion), that I'd advocate for second chances :-).