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

Pipeline report annotations hiding behind similarly named annotations



I've build a custom pipe to parse the code coverage for our project, but I'm having some issues with the pipeline report annotations.

For this project we have +150 annotations, which does match with the amount under the report, but for some reason it has put in duplicated annotations of certain classes which share a similar names to each other, instead of the actual classes with lower severity level.

Example: lib/ was "HIGH", but instead there is 2x  lib/ which is "CRITICAL".

The annotation externalids all have the report name as the prefix with the later half being SHA1 generated string that comes from the filepath + name so for they should all have unique suffix.

I'm certain that they are being POSTed correctly, as I can see them in the pipeline debug messages AND the correct annotation for the classes is highlighted with the correct severity level in the pull requests view, even tho you can't find that class in the report's  annotations.

Any insight into how to fix this issue?

2 answers

1 accepted

0 votes
Answer accepted

Was found to be a bug, where the Pipeline report annotations aren't being fetch correctly when over 100 due to pagination error

0 votes
Patrik S Atlassian Team Feb 16, 2022

Hello @Petrus Hakakoski 

Welcome to Atlassian Community!

Reading through the details you have provided, we'll likely need to access your build logs and pull request to understand the behavior you reported.

Checking our internal tools I've noticed you have access to a workspace in the Standard plan, so in order to further investigate this case, I have created an internal ticket for you using the email of your community account, so you don't have to share this information here.
You should have received an email with a link to the support ticket. Just in case you haven't received it, please feel free to let me know and I can post the ticket URL here. The ticket will be visible only to you and Atlassian staff, no one else can view its contents even if they have the URL.
Kind regards,
Patrik S

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events