-
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...
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.