Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-9238

GreenHopper Issue Type does not render on fresh installation with JIRA 6.0.x

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Tracked Elsewhere
    • Icon: Medium Medium (View bug fix roadmap)
    • None
    • 6.2.3, 6.2.4, 6.2.4.1
    • None

      After a fresh installation of JIRA 6.0.x with GreenHopper 6.2.x and , the GreenHopper Issue Type are not rendered properly:

      • Issue Type
      • Create Issue
      • Create Issue Epic

      Reindexing is done already right after the installation of plugin and after the issue occurs.

        1. Capture.PNG
          Capture.PNG
          77 kB
        2. create_issue.jpg
          create_issue.jpg
          176 kB
        3. epic_issue_type.JPG
          epic_issue_type.JPG
          88 kB
        4. issue_type.JPG
          issue_type.JPG
          202 kB

          Form Name

            [JSWSERVER-9238] GreenHopper Issue Type does not render on fresh installation with JIRA 6.0.x

            Dave C added a comment -

            This is caused by a bug in JIRA as tracked under JRA-33966.

            Dave C added a comment - This is caused by a bug in JIRA as tracked under JRA-33966 .

            Rick Schultz added a comment -

            Tried Igor's approach and it did not resolve the issue. The fields are still showing up fully qualified. Were there other steps? We restored from a vanilla backup taken right after we installed everything.

            Rick Schultz added a comment - Tried Igor's approach and it did not resolve the issue. The fields are still showing up fully qualified. Were there other steps? We restored from a vanilla backup taken right after we installed everything.

            Igor Dronov added a comment -

            After a few days of experimenting, just found a workaround solution, provided that it's a fresh JIRA install and you do not worry about losing data: do a complete restore from vanilla installation backup through JIRA administration panel and all GreenHopper property fields now show up just fine.

            Igor Dronov added a comment - After a few days of experimenting, just found a workaround solution, provided that it's a fresh JIRA install and you do not worry about losing data: do a complete restore from vanilla installation backup through JIRA administration panel and all GreenHopper property fields now show up just fine.

            My Kro added a comment -

            If this will not be fixed soon, can we please have a workaround to apply the fix in-place on our existing installation?

            I guess that it is just a few strings stored somewhere. But I am only able to find and fix two of the strings in the Administrator area: Name and Description. There are several labels in my system still showing the wrong text such as:

            • gh.epic.label.name
            • gh.epic.label.desc
            • gh.epic.color.name
            • gh.epic.color.desc
            • gh.epic.link.name
            • gh.epic.status.name
            • gh.epic.status.desc
            • gh.rank.global.name
            • gh.rank.global.desc
            • gh.sprint.customfield.default.name

            The users see these in the UI and in their email notifications and it makes the system look very unprofessional

            My Kro added a comment - If this will not be fixed soon, can we please have a workaround to apply the fix in-place on our existing installation? I guess that it is just a few strings stored somewhere. But I am only able to find and fix two of the strings in the Administrator area: Name and Description. There are several labels in my system still showing the wrong text such as: gh.epic.label.name gh.epic.label.desc gh.epic.color.name gh.epic.color.desc gh.epic.link.name gh.epic.status.name gh.epic.status.desc gh.rank.global.name gh.rank.global.desc gh.sprint.customfield.default.name The users see these in the UI and in their email notifications and it makes the system look very unprofessional

            Blargo added a comment -

            Same problem with new install here also. Did not happen with 6.0.1 fresh install.

            Blargo added a comment - Same problem with new install here also. Did not happen with 6.0.1 fresh install.

            Steve Conard added a comment -

            I'm have the same problem. See ticket: GHS-8696

            Steve Conard added a comment - I'm have the same problem. See ticket: GHS-8696

            Mischa Brammer added a comment - - edited

            I have the same problem with the rendering (https://support.atlassian.com/browse/GHS-8695).

            Mischa Brammer added a comment - - edited I have the same problem with the rendering ( https://support.atlassian.com/browse/GHS-8695 ).

            My Kro added a comment -

            For me (as reported in GHS-9231) Task and Story were fine, Epic was the only issue type that didn't render correctly.

            My Kro added a comment - For me (as reported in GHS-9231 ) Task and Story were fine, Epic was the only issue type that didn't render correctly.

            Stefan Nuxoll added a comment -

            Additionally, I just reverted and performed a fresh install of JIRA 6.0.1 and was not able to reproduce this issue. This bug appears to be a regression in JIRA 6.0.2.

            Stefan Nuxoll added a comment - Additionally, I just reverted and performed a fresh install of JIRA 6.0.1 and was not able to reproduce this issue. This bug appears to be a regression in JIRA 6.0.2.

            Stefan Nuxoll added a comment -

            Custom field translations do not render

            Stefan Nuxoll added a comment - Custom field translations do not render

              Unassigned Unassigned
              adanial Ahmad Danial (Inactive)
              Affected customers:
              21 This affects my team
              Watchers:
              27 Start watching this issue

                Created:
                Updated:
                Resolved: