Uploaded image for project: 'FishEye'
  1. FishEye
  2. FE-4415

Create a Report - Identify JIRA Issues That Aren't Associated with a Review

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.

      Our setup has multiple Jira projects (one for each development "pod" on our team) that work against a single code repository. We manually match versions across these projects for most of our reporting within Jira (ie, FixVersions of "5.22 September Release" exists across all our projects"). I have been asked to see if I can generate a report/dashboard to show the review coverage for a single release (ie, across this defined list of Jira projects against the single repository). We are wanting to see what percentage of our code that goes for a single release (ie, version) has been reviewed.

      The Release Report gives us more or less the "negative view" of what we want - ie, it tells us which jira cards have a code review, but it doesn't give us all the cards that are in the release that do not have a code review (which is ultimately what we are driving towards).

            [FE-4415] Create a Report - Identify JIRA Issues That Aren't Associated with a Review

            Marek Parfianowicz added a comment -
            Atlassian Update – 5 October 2018

            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 resolve it as Timed Out.

            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 – 5 October 2018 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 resolve it as Timed Out . 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
              drohan Daniel R
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: