-
Bug
-
Resolution: Fixed
-
Low (View bug fix roadmap)
-
2015-12-14 Cloud, 2016-02-29 Cloud, 7.1.1, 7.2.0, 7.1.2, 7.3.1
-
None
-
7.01
-
17
-
Severity 3 - Minor
-
70
-
NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.
Summary
The Epic and Story description are wrong on the help page.
- <instance-url>/secure/ShowConstantsHelp.jspa?decorator=popup#IssueTypes
Steps to Reproduce
- In the instance click to create an issue;
- On the right side of Issue Type click on the help button.
Expected Results
Shows the right description.
Actual Results
| Issue Type | Description Shown |
|---|---|
| Epic | gh.issue.epic.desc |
| Story | gh.issue.story.desc |
| Bug | jira.translation.issuetype.bug.name.desc |
It also shows these incorrect strings on the Issue Types page in administration.
Workaround
Always generate backup of your database before making any changes to it via SQL. Any workaround requiring SQL changes carries inherent risk so a backup of your DB is essential to restore working conditions if there is a critical problem.
1. Execute the following queries in your database:
If you are using languages other than English, please replace the description string in queries with respective translation
UPDATE issuetype SET description='A problem which impairs or prevents the functions of the product.' WHERE description='jira.translation.issuetype.bug.name.desc'
UPDATE issuetype SET description='Created by JIRA Software - do not edit or delete. Issue type for a big user story that needs to be broken down.' WHERE description='gh.issue.epic.desc'
UPDATE issuetype SET description='Created by JIRA Software - do not edit or delete. Issue type for a user story.' WHERE description='gh.issue.story.desc'
2. Restart the JIRA instance
- duplicates
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
SW-3038 Failed to load
- is duplicated by
-
-
- Closed
-
- is related to
-
-
- Closed
-
-
SW-3146 Loading...
- relates to
-
-
- Closed
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-13032] Description for Epic and Story are not showing on Issue Types or help page
Here is the reason: code is looking for translation keys gh.issue.epic.desc and gh.issue.story.desc at each server startup.
These translation entries are expected to be in resource com/pyxis/greenhopper/jira/actions/BoardAction.properties stored in jira-greenhopper-plugin-*.jar available in installation location atlassian-jira/WEB-INF/application-installation/jira-software-application/ (mine is named jira-greenhopper-plugin-7.3.0-DAILY20170320173936.jar
There is a mismatch with keys in properties files:
gh.issue.epicdesc=Created by JIRA Software - do not edit or delete. Issue type for a big user story that needs to be broken down. gh.issue.storydesc=Created by JIRA Software - do not edit or delete. Issue type for a user story.
Here are possible quick fixes:
- correct keys in resource file in plugin and in corresponding jira-software-language-pack-* jar files
- provide keys in your own translation plugin, produced by InProduct Translation plugin or built manually
Then expected descriptions are applied to these two issue types at each server restart.
Daniel Koshel
added a comment - But who cares? 
When I just filled (from there) that descriptions manually, my plugins stopped working with these issue types.
Daniel Koshel
added a comment - But who cares?
When I just filled ( from there ) that descriptions manually, my plugins stopped working with these issue types. We upgraded our test system to version 7.3.3 two days ago, and the problem is still there (obviously, I suppose, as it hasn't been marked as fixed).
We could easily see the data we entered in the issuetype database table (we have 20 rows in this table), then it would get overwritten a few minutes later when we restarted JIRA.
I see this problem was reported more than a year ago now. It would seem like a small fix, so would be nice to have this done soon...
Reboot of server will WIPE out your custom text and replace it with - gh.issue.epic.desc
Why can't I enter my customized text? Why does the system wipe it out?
It happens also in upgraded installations, now only in fresh or new ones...
Installed JIRA yesterday (1/1/2017) and I am seeing this issue as well. Epic/Story descriptions revert to the wrong values (gh.issue.epic.desc and gh.issue.story.desc) after every JIRA restart.
HAUET Antxon
added a comment - Same issue here, would be nice to have it fixed. 
Well at least Atlassian has the same issue
No seriously this should be fixed by now for server 
Same as @Samuel Leslie and @Jessica Bartsch. We have a brand new installation, and all of the sudden Epic & Story descriptions revert back to these technical property names. It's hard to believe that this 1) slipped through testing, 2) slipped through testing for multiple versions, and 3) has taken over 8 months just to get to "verified" stage and still not assigned to anybody. I realize that his is a "minor" issue, but come on guys...if you can't get the labels of the basic issues types to show up right, it's hard to believe that I'm not going to run into more serious bugs that also don't get fixed. I assume your engineers are working on more serious bugs that have been around even longer, which is also worrisome.
Jessica Bartsch
added a comment - As @Samuel Leslie stated this bug is extremely annoying, the descriptions for the Epic and Story issue types will revert to those noted above upon restart of your JIRA instance. I assume its when the Agile plugin loads something in that code is overriding the database values for those issue types Epic and Story. Note that I don't see the problem for the Bug issue type it retains the assigned Description I provided after a restart.
Jessica Bartsch
added a comment - As @Samuel Leslie stated this bug is extremely annoying, the descriptions for the Epic and Story issue types will revert to those noted above upon restart of your JIRA instance. I assume its when the Agile plugin loads something in that code is overriding the database values for those issue types Epic and Story. Note that I don't see the problem for the Bug issue type it retains the assigned Description I provided after a restart. Is there any update on when this may be resolved or even a temporary workaround might be offered?
Thanks and regards,
Mitch
This bug is actually more annoying than I originally realised as it turns out the descriptions for the Epic and Story issue types will revert to those noted above even after updating their descriptions to something more useful. I'm not sure what triggers the reversion at this point. Note that I don't see this behaviour for the Bug issue type.
Confirming this affects a fresh installation of JIRA Software v7.1.6 using a PostgreSQL v9.3 database.
David Gray
added a comment - This appears to affect all new/fresh installs.
Is there a known workaround? Some suggestions I've seen involve a re-install of Jira, which needless to say is not an ideal solution. Is the issue a data issue that can be fixed with some SQL? or is it a something more complex that needs a patch?
We're currently evaluating the software and this has made me hesitant to continue with that process as I fear I will need to wipe the install and start again to resolve this issue.
David Gray
added a comment - This appears to affect all new/fresh installs.
Is there a known workaround? Some suggestions I've seen involve a re-install of Jira, which needless to say is not an ideal solution. Is the issue a data issue that can be fixed with some SQL? or is it a something more complex that needs a patch?
We're currently evaluating the software and this has made me hesitant to continue with that process as I fear I will need to wipe the install and start again to resolve this issue.
Found the issue appearing in a fresh 8.2.3 installation. After upgrading to 8.3.0 i have now 2 story fields and one epic.