• 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.

      Would be nice to have better reports for reviews, for example:
      1. A CSV or Excel file dump of all comments in a review showing all details associated with the comments. The current CSV file has the history but not all fields (like defects and associated data).
      2. A report with defect rate for a review. Lists all the defects, can be categorized by type. Also would be nice if you could do this by project and across projects
      3. Time report to show the amount of time by person and total of a review. This should also be capable of doing it by project (for all reviews) and by all reviews.
      4. Review Summary report that shows items 2 and 3 in a summary format and can be done for project and all reviews.

            [CRUC-6570] Review Data Reporting

            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

            Regarding (1) I don't think that we will ever provide this in an excel export due to edge cases in fields handling by Excel. Customers should be able to build their own export through the REST API though so we already have a workaround in place.

            The rest of the suggestions are good. We intend to provide better reporting capabilities for Crucible in the future and we will keep this in mind. Please note that due to current priorities we are not going to work on this before the beginning of next year.

            Regards,

            Sten Pittet
            FishEye / Crucible Product Manager

            Sten Pittet (Inactive) added a comment - Regarding (1) I don't think that we will ever provide this in an excel export due to edge cases in fields handling by Excel. Customers should be able to build their own export through the REST API though so we already have a workaround in place. The rest of the suggestions are good. We intend to provide better reporting capabilities for Crucible in the future and we will keep this in mind. Please note that due to current priorities we are not going to work on this before the beginning of next year. Regards, Sten Pittet FishEye / Crucible Product Manager

              Unassigned Unassigned
              cyoshioka CelsoA
              Votes:
              3 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: