-
Bug
-
Resolution: Tracked Elsewhere
-
Low (View bug fix roadmap)
-
None
-
6.2.2.2
-
JIRA for Windows 64-bit
-
6.02
-
1. Upgraded JIRA 5.2.6 to 6.0.2
2. Then installed Greenhopper 6.2.3 via Plugin Manager.
Noticed that the Epic issue type had been created as follows:
Name: gh.issue.epic
Description: gh.issue.epicdesc
The other Greenhopper types: Story, Improvement, etc, were created correctly.
Workaround: Edit the issue type and correct the Name and Description. Problems will still exist with other strings such as gh.epic.label.name and gh.epic.label.desc, not sure yet how to work around these.
A previous installation of Greenhopper 6.2.2.2 on JIRA 5.2.6 (staging server) did not exhibit this problem.
- is caused by
-
JRASERVER-33966 Race condition occurs between JIRA and plugins with i18n translation
-
- Closed
-
-
JRADEV-23317 Failed to load
- is related to
-
JSWSERVER-9238 GreenHopper Issue Type does not render on fresh installation with JIRA 6.0.x
-
- Closed
-
-
JSWSERVER-9702 Please write an upgrade task to fix instances that have been affected by JRA-33966
-
- Closed
-
- relates to
-
JSWSERVER-9193 Custom Fields, Issue Types and Schemes appear incorrectly on a new install of Greenhopper
-
- Closed
-
-
JSWSERVER-13032 Description for Epic and Story are not showing on Issue Types or help page
-
- Closed
-
- mentioned in
-
Page Loading...
This is caused by a bug in JIRA as tracked under
JRA-33966.