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

      What I want from the review coverage report is:

      • Show me a graph of how our review coverage is changing over time.
      • Let me dig into the detail for a particular period to investigate any unexplained changes.
      • Let me forward it to others so they can take a look.

      At present it falls down in the following areas:

      • It takes a long time for the graph to appear, which is annoying for me.
      • It's hard to forward it to others. If I send them a link to the report they have to sit there for several minutes waiting for it to appear. I can take a screenshot and email it but then it's harder to dig into the detail.
        Alternatively you maybe could have an "email me the report" button which would email it in html format when it's finished? That would allow me to forward it more easily.
      • The detail report has a rather clunky interface. It only allows me to select a day or a week ("week" appearing to mean seven days rather than any concept of working week) and it automatically refreshes every time I change anything rather than waiting until I've finished selecting what I want. It would be much more useable if I could just put in a start and end date and click a "go" button.

            [CRUC-7145] Review Coverage Plugin improvements

            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
              rverschoor Rene Verschoor (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: