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

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

                Created:
                Updated: