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

Crucible report to show review status for every file in branch/directory

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

      It would be nice to have a report on files in a given branch or directory to display:

      • the current version of the file
      • the last reviewed version and
      • the status of the last review
      • possibly more relevant data

            [CRUC-6649] Crucible report to show review status for every file in branch/directory

            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

            As a development team, we need Crucible or Fisheye to report the report status for each file in the implementation directory before we want to deliver to the customer.

            In order to fulfil this task, we would need to be able to select the branch and directory including the sources which are the basis for the delivery. Other branches and folders are not relevant, they may e.g. contain technical developer documentation.

            With either a report (preferred) or a web interface (search / filter - which we could print), we want to ensure, that:

            • All relevant files have been reviewed and what is the status of the review comments (resolved in discussion or issue raised), who was participating in the review, ...
            • How many files are currently under review
            • How many files have to be added in a future review (never reviewed or reviewed in a previous version)

            Thanks.

            Hans-Jürgen Tappe added a comment - As a development team, we need Crucible or Fisheye to report the report status for each file in the implementation directory before we want to deliver to the customer. In order to fulfil this task, we would need to be able to select the branch and directory including the sources which are the basis for the delivery. Other branches and folders are not relevant, they may e.g. contain technical developer documentation. With either a report (preferred) or a web interface (search / filter - which we could print), we want to ensure, that: All relevant files have been reviewed and what is the status of the review comments (resolved in discussion or issue raised), who was participating in the review, ... How many files are currently under review How many files have to be added in a future review (never reviewed or reviewed in a previous version) Thanks.

              Unassigned Unassigned
              pkoczan Peter Koczan (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: