• Icon: Bug Bug
    • Resolution: Invalid
    • Icon: Medium Medium (View bug fix roadmap)
    • None
    • None
    • None
    • Linux standalone server using mysql backend and oracle JDK.

      As a adminstrator of JIRA,
      When doing a single project import,
      JIRA needs to import all extra greenhopper version data
      so that my report data and graphs are not unuseable.

      Performing a single project import does not import green hopper aditional attributes on versions. Specically it does not respect the heirachy and the start/end/release dates on versions.

      This is very furstrating when importing a single project, as manually entering this data after the import is slow and painful (as you have to do it on the agile screen, as not all details are setable on the versions screen). Any extra custom data attributes used by plugins should be imported as some of this data is critical to the usefulness of JIRA.

      The lack of this data ruins reports and graphs that can be obtained on the interface.

          Form Name

            [JSWSERVER-4448] Import GreenHopper data as part of single project import

            I was able to merge two GH instances by writing a script that merges the GH data after you do the project import. Still, in order to be able to do this you need two databases.

            Sorin Sbarnea added a comment - I was able to merge two GH instances by writing a script that merges the GH data after you do the project import. Still, in order to be able to do this you need two databases.

            Michael Andreacchio added a comment - - edited

            Note, is it not possible to get GreenHopper data out of a project import. The Following issue exists for this problem:
            https://jira.atlassian.com/browse/JRA-28748

            Michael Andreacchio added a comment - - edited Note, is it not possible to get GreenHopper data out of a project import. The Following issue exists for this problem: https://jira.atlassian.com/browse/JRA-28748

            Hi Paul,

            Thanks for contacting Atlassian.

            This seems to be a support related issue and I'd like to help you in our support system http://support.atlassian.com please log the issue there and we will get onto your case ASAP.

            In future can you please raise support requests such as this by creating an issue in our support system, https://support.atlassian.com, not in http://jira.atlassian.com. As our support engineers respond to cases in https://support.atlassian.com, it will ensure that your problem gets addressed as quickly as possible. Also, https://support.atlassian.com is configured so that only Atlassian and you have access to the case, therefore it is a more appropriate location for us to gather any required system data and configuration from

            Cheers,

            Michael
            Atlassian Support

            Michael Andreacchio added a comment - Hi Paul, Thanks for contacting Atlassian. This seems to be a support related issue and I'd like to help you in our support system http://support.atlassian.com please log the issue there and we will get onto your case ASAP. In future can you please raise support requests such as this by creating an issue in our support system, https://support.atlassian.com , not in http://jira.atlassian.com . As our support engineers respond to cases in https://support.atlassian.com , it will ensure that your problem gets addressed as quickly as possible. Also, https://support.atlassian.com is configured so that only Atlassian and you have access to the case, therefore it is a more appropriate location for us to gather any required system data and configuration from Cheers, Michael Atlassian Support

              mandreacchio Michael Andreacchio
              ef921def4413 Brian Mills
              Affected customers:
              8 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: