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

Creating review from Jira Fisheye plugin's fisheye issue tab panel - need to be able to include all related changesets (beyond max changesets)

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

      Using Jira Fisheye plugin version 2.5 against Fisheye/Crucible 2.0.3. Currently, a link is displayed on the fisheye issue tab panel to "Create crucible review for all xxx changesets in yyyyy" (where yyyyy is the name of the repository).

      When the number of related commits exceeds the "max changesets per project" setting, links for the additional changesets will appear at the bottom of the tab, identified by "More related changesets:" In the link to create a crucible review, however, the number displayed in "xxx changesets" never exceeds the max changesets per project. As a result, it's impossible to create a code review that contains all of the related changesets. One can only create a code review containing the first xxx changesets (where xxx is the max).

      Attached screenshot shows a situation where max is set to 5 and there are actually 13 changesets related to the issue. Here, the user cannot create a code review with all 13 changesets.

            [CRUC-2306] Creating review from Jira Fisheye plugin's fisheye issue tab panel - need to be able to include all related changesets (beyond max changesets)

            Marek Parfianowicz made changes -
            Status Original: Gathering Interest [ 11772 ] New: Not Being Considered [ 11776 ]

            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
            Marek Parfianowicz made changes -
            Fix Version/s New: N/A [ 54415 ]
            Labels New: jac-cleanup-phase10
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3019740 ] New: JAC Suggestion Workflow 3 [ 3633339 ]
            Marek Parfianowicz made changes -
            Component/s New: Integrations [ 14490 ]
            Component/s Original: Plugins [ 12772 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2946722 ] New: JAC Suggestion Workflow [ 3019740 ]
            Owen made changes -
            Workflow Original: FECRU Development Workflow - Triage [ 939681 ] New: Confluence Workflow - Public Facing v4 [ 2946722 ]
            Status Original: Open [ 1 ] New: Gathering Interest [ 11772 ]
            Owen made changes -
            Backlog Order (Obsolete) Original: 2520000000
            Issue Type Original: Improvement [ 4 ] New: Suggestion [ 10000 ]
            Piotr Swiecicki made changes -
            Workflow Original: FECRU Development Workflow (Triage) [ 309705 ] New: FECRU Development Workflow - Triage [ 939681 ]

            Another great option would be to create review for my changesets. Useful if more than 1 person is commiting changesets to the same issue end need separate reviews.

            Draupnir Gudmundsson added a comment - Another great option would be to create review for my changesets. Useful if more than 1 person is commiting changesets to the same issue end need separate reviews.

              Unassigned Unassigned
              81035e918722 DaveT
              Votes:
              6 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: