• Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • User interface
    • None
    • 18
    • 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 haven't found ability to view a diff of a folder between several commits (not for a single commit, and not for single file)

      http://screencast.com/t/1SbqOxrj1PO

      Such feature exists in WebSVN:

      http://screencast.com/t/R0wsXNPcm
      http://screencast.com/t/5WkZIGbs9m

            [FE-239] Compare selected revisions of a folder

            Atlassian Update – 18 November 2022

            Hi everyone,

            We have recently reviewed this issue and the overall interest in the problem. As it does not fall into the scope of Fisheye's basic maintenance mode, we've decided to close 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.

            Regards

            Marek Parfianowicz
            Development Team Lead
            Fisheye/Crucible Team

            Marek Parfianowicz added a comment - Atlassian Update – 18 November 2022 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As it does not fall into the scope of Fisheye's basic maintenance mode , we've decided to close 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. Regards Marek Parfianowicz Development Team Lead Fisheye/Crucible Team

            Atlassian Update – 19 May 2020

            Hi everyone,

            thank you very much for reporting this suggestion and your involvement in the conversations around it. This suggestion is in the 'Reviewing' state which means it awaits assessment by our team.

            As Fisheye and Crucible have entered basic maintenance mode, our team currently focuses more on bug-fixes and platform updates rather than on feature development. We may still deliver some small improvements if they fit into the maintenance theme. However, suggestions which have been assessed already and are in the Under consideration state have higher priority.

            It means it may take time until we review this suggestion and decide whether to put it on the roadmap or reject it. You can expect an update from us in couple of months. 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
            Fisheye/Crucible Team

            Marek Parfianowicz added a comment - Atlassian Update – 19 May 2020 Hi everyone, thank you very much for reporting this suggestion and your involvement in the conversations around it. This suggestion is in the 'Reviewing' state which means it awaits assessment by our team. As Fisheye and Crucible have entered basic maintenance mode , our team currently focuses more on bug-fixes and platform updates rather than on feature development. We may still deliver some small improvements if they fit into the maintenance theme. However, suggestions which have been assessed already and are in the Under consideration state have higher priority. It means it may take time until we review this suggestion and decide whether to put it on the roadmap or reject it. You can expect an update from us in couple of months. 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 Fisheye/Crucible Team

            Classic Atlassian. Basic Features not implemented after 10 Years.

            Johannes Renoth added a comment - Classic Atlassian. Basic Features not implemented after 10 Years.

            Vinodh added a comment -

            Do we have this fixed? 

            we need your help to get this feature to compare two branches and put for a review rather individual files review.

            Vinodh added a comment - Do we have this fixed?  we need your help to get this feature to compare two branches and put for a review rather individual files review.

            We are currently trialing Crucible, and this may be one missing feature that would cause us to pass. I often make many commits to a personal branch where a good portion of those are merging from a trunk. In Crucible this provides a long list of commits to pick from, and ideally I would prefer to choose all of the valid commits and ignore the merges. This can sometimes involve a lot of clicking to include the right changes. Using a diff between trunk and branch/tag would be the best solution for this. We currently use Code Collaborator which has no issues doing this.

            Jerimiah P. Lee added a comment - We are currently trialing Crucible, and this may be one missing feature that would cause us to pass. I often make many commits to a personal branch where a good portion of those are merging from a trunk. In Crucible this provides a long list of commits to pick from, and ideally I would prefer to choose all of the valid commits and ignore the merges. This can sometimes involve a lot of clicking to include the right changes. Using a diff between trunk and branch/tag would be the best solution for this. We currently use Code Collaborator which has no issues doing this.

            +1 for this feature
            (even free tools, like Trac, support this...)

            Robert Wilterdink added a comment - +1 for this feature (even free tools, like Trac, support this...)

            Shn Ops added a comment -

            This was requested over 6 years ago, are there any plans to actually implement it?

            Shn Ops added a comment - This was requested over 6 years ago, are there any plans to actually implement it?

            Please increase the priority of this issue. We regard this feature as fundamental and can't believe it isn't there.

            Telstra Automation Engineering added a comment - Please increase the priority of this issue. We regard this feature as fundamental and can't believe it isn't there.

            My users are asking: any progress or ideas on when this will be fixed?

            Broadcom Support added a comment - My users are asking: any progress or ideas on when this will be fixed?

            +1 we just moved to crucible/fisheye from google-code-review/trac and have been very excited... until seeing this and CRUC-1542 - extremely disappointing!

            Aaron Daubman added a comment - +1 we just moved to crucible/fisheye from google-code-review/trac and have been very excited... until seeing this and CRUC-1542 - extremely disappointing!

              Unassigned Unassigned
              de21f8a6ae93 Stepan Koltsov
              Votes:
              137 Vote for this issue
              Watchers:
              85 Start watching this issue

                Created:
                Updated: