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

Importing review history after SVN merge

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • N/A
    • None

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

      Hi tehre.

      We have been using Crucible for sometime now and we are starting to face some issue i'd like to see addressed. The issue is that when different teams are coding in different SVN branches they do all of their code reviews on those branches so we get good management reporting about the code review coverage of those branches. But when the teams merge their code to Trunk, the code review history is lost, and if you look at the code review coverage for trunk it does not depict the true picture. This is becoming critical for our setup, without the reporting on trunk management gets little value out of this setup.

      Steps to Reproduce:

      1. Configure the Repo in Fisheye.
      2. Commit a file into a Branch.
      3. Create a review with the file included.
      4. Review it and close it.
      5. Check the Review Coverage Report of the Branch
      6. Merge the file into Trunk.
      7. Check the Review Coverage Report of the Trunk.

      The Reviewed status of the file on Branch is not imported to the Trunk.

      Thank you in advance.

      Cheers,
      Douglas Fabretti
      Atlassian Support

        1. Branches.jpg
          Branches.jpg
          49 kB
        2. trunk.jpg
          trunk.jpg
          49 kB

            [CRUC-6113] Importing review history after SVN merge

            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

            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

            Sten Pittet (Inactive) added a comment -

            Hi,

            This is an interesting feature for SVN but it will be hard to implement.

            A SVN merge creates a new commit in the targeted branch with little information about the past commits. Attaching all the review data linked to the changesets that have been merged is difficult to do in this situation.

            Sten

            Sten Pittet (Inactive) added a comment - Hi, This is an interesting feature for SVN but it will be hard to implement. A SVN merge creates a new commit in the targeted branch with little information about the past commits. Attaching all the review data linked to the changesets that have been merged is difficult to do in this situation. Sten

              Unassigned Unassigned
              dfabretti Douglas Fabretti [Atlassian]
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: