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

Allow multiple reviewers when filtering reviews on the review dashboard

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.

      I would like it if crucible would allow me to filter by multiple reviewers (creator, moderators, authors). The organization I am with has multiple large teams that use the same crucible instance, and my team is divided into three smaller project teams. During our scrum I like to filter down the code reviews that are overdue for my group. This wasn't a problem until I allowed others to lead projects within my group and since they are the leads I am no longer on those code reviews (previously I was on every code review). My old query just found code reviewers where I was a reviewer. Now that I am not on all the code reviews I have to have a query per project lead. I would like to have just one query that will show me all overdue code reviews.

      Example of what I have (3 queries)
      http://xyz.com/viewer/cru/?filter=custom&project=MyOrg&reviewer=Josh&author=Josh&orRoles=true&state=Review
      http://xyz.com/viewer/cru/?filter=custom&project=MyOrg&reviewer=Nick&author=Nick&orRoles=true&state=Review
      http://xyz.com/viewer/cru/?filter=custom&project=MyOrg&reviewer=Mike&author=Mike&orRoles=true&state=Review

      What I would like to do
      http://xyz.com/viewer/cru/?filter=custom&project=MyOrg&reviewer=Josh,Nick,Michael&author=Josh,Nick,Michael&orRoles=true&state=Review

      I don't believe the crucible rest APIs allow this.
      What I have done:

      • Read the API documentation online
      • Searched the JIRA crucible queue
      • Tried my new modified query
      • Asked within my organization

            [CRUC-7437] Allow multiple reviewers when filtering reviews on the review dashboard

            Marek Parfianowicz added a comment -
            Atlassian Update – 10 January 2022

            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 Not Being Considered.

            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.

            Kind regards
            Marek Parfianowicz
            Development Team Lead

            Marek Parfianowicz added a comment - Atlassian Update – 10 January 2022 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 Not Being Considered . 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. Kind regards Marek Parfianowicz Development Team Lead

              Unassigned Unassigned
              c23bec577ffc Joshua Davis
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: