• Type: Suggestion
• Resolution: Unresolved
• Fix Version/s: N/A
• Component/s: None
• Labels:

  • branch-review
  • coverage
  • jac-cleanup-phase5
  • report
  • reporting
  • review

1. 

   image-2017-02-08-10-18-20-956.png

   6 kB

   08/Feb/2017 6:18 PM

[CRUC-7378] Review coverage report doesn't show all reviewed lines

Collapse comment: Marek Parfianowicz added a comment - 04/Feb/2019 6:21 PM

Marek Parfianowicz added a comment - 04/Feb/2019 6:21 PM

Atlassian Update – 4 February 2019

Hi everyone,

We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to close it.

Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye & Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details.

We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

Regards
Marek Parfianowicz
Fisheye/Crucible TL

Expand comment: Marek Parfianowicz added a comment - 04/Feb/2019 6:21 PM

Marek Parfianowicz added a comment - 04/Feb/2019 6:21 PM Atlassian Update – 4 February 2019 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to close it. Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye & Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Regards Marek Parfianowicz Fisheye/Crucible TL

Collapse comment: Jessica McMullan added a comment - 08/Feb/2017 6:21 PM

Jessica McMullan added a comment - 08/Feb/2017 6:21 PM

We are experiencing this issue which makes it look like our production code contains commits that have not been reviewed. We purchased and use this tool with the expectation that, in the event of an audit we would easily be able to show that all of our code has been reviewed by showing the review coverage report. This bug prevents us from using the tool as intended.

This image shows the commit graph of a portion of our production code with the red commits being incorrectly identified as not being reviewed.

Expand comment: Jessica McMullan added a comment - 08/Feb/2017 6:21 PM

Jessica McMullan added a comment - 08/Feb/2017 6:21 PM We are experiencing this issue which makes it look like our production code contains commits that have not been reviewed. We purchased and use this tool with the expectation that, in the event of an audit we would easily be able to show that all of our code has been reviewed by showing the review coverage report. This bug prevents us from using the tool as intended. This image shows the commit graph of a portion of our production code with the red commits being incorrectly identified as not being reviewed.