I do not have a solution for this, but am replying because I’m experiencing the same issue. Before I mention the details of my circumstances in which I’m seeing this bug, I wanted to link this older closed topic about what appears to be the same issue: No issue details, but the summary view says I have 13 bugs - #18 by Silviu_Asandei
According to that thread this was a bug that was since fixed. While I saw this bug go away for one of my projects it persists for another.
For the purposes of this topic I’ll simply refer to my projects as project A and B. I will also be referring to days in the timeline based around one particular day: that being the day that @Silviu_Asandei’s last post was made on the earlier linked topic, saying that it had been fixed and that a full root cause analysis would be conducted. I will refer to this as the “original fix day”.
Project A:
- ALM used - JIRA
- CI system used - Azure DevOps
- Source Control repos hosted at - GitHub
- Languages of the repository - Typescript
Project A was experiencing this issue approximately 6 days after the “original fix day”. This means the issue was still occurring even after it was supposed to have been fixed. The next day (so approximately 7 days after the “original fix day”) it suddenly started working and showing details for the issues in the summary. It’s as if the fix was delayed in terms of when it applied to Project A.
Project B:
- ALM used - JIRA
- CI system used - Azure DevOps
- Source Control repos hosted at - GitHub
- Languages of the repository - .NET C#
I noticed this issue with Project B approximately 8 days after the “original fix day”. This was after Project A started working correctly again. At time of writing Project B is still experiencing this issue.
@Silviu_Asandei, do you know what was the full root cause analysis of this bug? Are we sure it has been fixed completely and that the fix has been applied to all users? It seems that @samarpan-b and I are still experiencing this issue.