Uploaded image for project: 'Jira Software Server and Data Center'
  1. Jira Software Server and Data Center
  2. JSWSERVER-9193

Custom Fields, Issue Types and Schemes appear incorrectly on a new install of Greenhopper

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: High
    • Resolution: Tracked Elsewhere
    • Affects Version/s: 6.2.2.2, 6.2.3, 6.2.4, 6.2.4.1, 6.2.5
    • Fix Version/s: None
    • Component/s: None

      Description

      Steps to reproduce

      • On a brand new JIRA instace (tested on 6.0.5); install Greenhopper (6.2.5)

      Expected Results

      • Better handling of sample data generated

      This is affecting the following names and descriptions

      • Custom Field names.
      • Issue Type names.
      • Issue Type Scheme.

      Workaround

      If this is a fresh installation and contain no valuable data, we encourage to re-do the whole installation process with an empty database, follow the steps below:

      1. Uninstalled JIRA and clear the data
      2. Install JIRA and create a backup directly
      3. Install GreenHopper and Reindex
      4. Noticed that the problem still persist
      5. Perform a system restore with the backup data created earlier
      6. Double check that the problem is resolved after the restore
        Thank you Matthew for pointing this out

      If the instance is being used for production:

      1. Unlock the GreenHopper Custom Fields as per our How to unlock a Locked field KB. This will enable them to be editable.
        Please lock them back after making the changes so as to prevent any accidental changes to the configuration, which can break GreenHopper.
      2. If there are duplicated Issue Type names (e.g.: "Story" and "gh.issue.story"):
        1. Bulk Edit the old Issue Types to the new ones as per our Modifying Multiple ('Bulk') Issues docs. For example, if there is a "Story" Issue Type, move those issues to "gh.issue.story".
        2. Rename "Story" to "Story (unused)" and remove it from all the Issue Type schemes.
        3. Repeat these steps for any other duplicated Issue Types.
      3. Rename the Issue Types, Issue Type Scheme, Workflow Name, Workflow Scheme and Custom Fields through the browser to human-readable names (e.g.: rename the Issue Type "gh.issue.story" to "Story").
      4. Reindex JIRA, so as to update the indexes with the new names.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              pkirkeby Pelle Kirkeby (Inactive)
              Votes:
              12 Vote for this issue
              Watchers:
              28 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: