Uploaded image for project: 'Crucible'
  1. Crucible
  2. CRUC-6918

Allow filters in the "Review Coverage" report, include/exclude users, branches

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Currently the "Review Coverage" report for a repository gives details of the amount of code that has been subject to a code review for all commits to a repository.

      However, this has two drawbacks:
      1. It's not possible to exclude certain committers from the report - we have build server user which creates new branches in the repository when we do an automated release. It would be good to be able to exclude this user from the report.
      2. It's not possible to focus just on one branch, so if we have different feature branches working concurrently, there's no way to see the % code review coverage for an individual branch.

      The filters should allow for excluding / including particular users, and excluding / including particular branches, and when set they should affect the whole view (eg. the % of code coverage, the graph, etc.)

            [CRUC-6918] Allow filters in the "Review Coverage" report, include/exclude users, branches

            Marek Parfianowicz added a comment -
            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

            Marek Parfianowicz added a comment - 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

              Unassigned Unassigned
              david.vivash David Vivash
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: