I've tried to find anyone else experiencing this elsewhere, and I've seen people who had similar issues (at least with the use of the word 'unlabelled') when using the Scrum board, but I don't have issues there.
On the 'Edit Issue' screen of any normal issue, when clicking in to the Epic Link field to assign the issue to an Epic, the Suggestions list that pops up shows, presently, two Epics:
"unlabelled-TEST-10 - (TEST-10)"
"Test Epic - (TEST-12)"
Except that TEST-10, not 12, has the Epic Name of "Test Epic" and TEST-12 has the Epic Name "Epic 2"
Since changing TEST-10 to have an Epic Name of 'Another Epic Name', the list is now:
"unlabelled-TEST-12 - (TEST-12)"
"Epic 2 - (TEST-10)"
Any help would be much appreciated as I'd love for our team to go back to using Epics.
JIRA 5.2.11 & GreenHopper 6.2.5
Yep, sorry, although I'm re-indexing it again now for other recent changes.
I've had this for a while, although I only recently upgraded from JIRA 5.1 to 5.2 and the issue persists, so I felt like this was a more appropriate time to report it.
The examples above are from a test project, but the same issue manifests if I create epics in the main project.
I'm not aware of an 'Epic Label', separately, but, yep, I am trying to assign them directly in JIRA after creating them, as this is a much more natural workflow for us.
I was hoping someone else had seen it and fixed it, although I know Atlassian only recently added support for the above in GreenHopper 6.2.2.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs