-
Bug
-
Resolution: Obsolete
-
Medium (View bug fix roadmap)
-
None
-
6.2.4.3
-
None
-
6.02
-
In some instances, Epic-specific fields (Epic Status, Epic Name etc.) appear as assigned to other Issue Types, and so show up as Required in screens that are not relevant. This affects different Issue Types.
Example:
Workaround:
Restart Jira Instance (in most cases corrections scripts will run at the start and fix the problem)
If restart doesn't work try the workaround: Epic Name field is required on Create Issue Screen for other Issue Types
- is caused by
-
-
- Closed
-
-
JIM-1089 Failed to load
- is related to
-
JSWSERVER-9564 As a Support Engineer, I would like for 'Epic Name' field duplicated records to be automatically deleted.
- Closed
- mentioned in
-
Wiki Page
No Confluence page found with the given URL.
-
Page
Failed to load
-
Page Loading...
-
-
-
-
-
-
[JSWSERVER-9552] Incorrect contexts for Epic related fields
Hi jeff809062307,
As per my comment above we believe that the issue reported here has been obsolete since JIRA 6.1.6 and the upgrade tasks that were run for upgrades from JIRA Agile 6.2.2.
Consequently, could you please raise a support request with us at https://support.atlassian.com so that we can review what is happening to you instance and troubleshoot with you further?
Thanks in advance.
Regards,
Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].
Jeff Galbraith
added a comment - We are new users to Jira and installed v7.1.7#71011 and this is exactly happening to us as detailed above.
Jeff Galbraith
added a comment - We are new users to Jira and installed v7.1.7#71011 and this is exactly happening to us as detailed above. Hi all,
We believe that the issue originally reported here has been solved.
After investigating, there were 2 possible causes for the symptoms reported in this JIRA issue:
- Using a CSV import which did not properly validate the file. This was reported and fixed: https://jira.atlassian.com/browse/JRA-35644. Fixed in JIRA 6.1.6
- The other was upgrading the JIRA Agile plugin. Many cases were reported a little after 30 May matching the release of JIRA Agile 6.2.2 (https://confluence.atlassian.com/display/AGILE/GreenHopper+6.2.2+Release+Notes)
There were 2 upgrade tasks added before that release - UpgradeTask033 and 34, both operate on fields and screens of epics. We have not been able to reproduce the problem with a simple upgrade, but this might not be the case for some datasets.
In any case, this is a version (6.2.2) of JIRA Agile that Atlassian no longer supports, the oldest JIRA Agile issue currently supported is 6.4.5, so the issue would be Obsolete.
Hope the above information helps clarify the current status of this issue.
Regards,
Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].
Chris Charlton
added a comment - You may need to add the field to the "SCREEN". I found it when digging around the global Project settings. I think this happens when you start a project with one ticket template system and then migrate it to another later.
Chris Charlton
added a comment - You may need to add the field to the "SCREEN". I found it when digging around the global Project settings. I think this happens when you start a project with one ticket template system and then migrate it to another later. 
Eunice Mora
added a comment - Ref ticket GHS-12635 eunice.mora, could you please open a ticket at support.atlassian.com and provide us with the backup of your instance, so that we can take a look at the details of your configuration? Thanks in advance!
Eunice Mora
added a comment - Have the same bug. Running JIRA V6.1.5 + JIRA Agile V6.3.6.1 standalone .
What causes this problem?
Eunice Mora
added a comment - Have the same bug. Running JIRA V6.1.5 + JIRA Agile V6.3.6.1 standalone .
What causes this problem?
I had this issue and found that it was due to 'Epic Name' field not being on the screen for certain projects.
Admin menu->Issues->Screens. Make sure 'Epic Name' is on all the screens that you use.
Create Epic now works for me. Hope this helps.