-
Bug
-
Resolution: Fixed
-
High
-
None
-
15
-
Severity 3 - Minor
-
1
-
Summary
When users attempt to link a Story of non next-Gen project with Epic of Next-Gen project, Jira still shows them in the list of possible Epics to be links. However, since Epic from next-Gen project has no Epic Name, it shows as unlabelled-issue key and has below error.
Issue 'issue key' must be of type 'Epic'.
From users' perspective, this is Epic issue type from next-gen project and they don't expect this to be much difference from other Epics. With the above error message returned, it is confusing users.
Steps to reproduce
- Have 2 projects (Next-gen and non next-gen)
- Create an Epic from Next-gen project
- Create a Story from non next-gen project
- Edit the Story and try to link it from Edit Issue screen
- Update
Expected Result
This seems not currently possible to do this crossed project linking between Next-gen and non next-gen project. Below are the proposed solution/expected behavior:
- Update our documentation about this limitation
- Epics from Next-gen projects should not be returned in the list of Epics, when users attempt to link it from non Next-gen project
- Provide clearer error message that users can't link with Epic from Next-gen project
Actual Result
Below error message is shown:
- is duplicated by
-
-
- Closed
-
- is related to
-
-
- Closed
-
-
ROAD-351 Failed to load
[JRACLOUD-91542] Provide clearer message when users link Story from non next-gen project with Epic of next-gen project
The change has been deployed in production. The next-gen epics should no longer show in the list of available epics in the epic link field in classic projects. Please let me know if you still see any next-gen epics (usually then are displayed as unlabelled-issue key). We will proceed with updating the docs!
We are currently working on the fix. Addressing all three points,
- We will update the documentation about the limitation of linking between next-gen epics to classic project issues.
- The next-gen epics will not be returned as options for classic project issues.
- Once 2. is done, I believe we are not going to see the message in UI very often. But we will think of the message as well.
Thanks for your patience, I will update this ticket once the changes are deployed!
jfemia does moving this to the Roadmap mean that it will be addressed imminently?
Good to see the priority of this issue increasing; its still an issue that affects us daily.
We're using a Next Gen project for its Roadmapping feature. All our Epics are contained there so we can plan and schedule them. All our other projects are Classics and we would like to link the issues within them to the Next Gen Epics. This bug prevents this from occurring, rendering our desired roadmapping unlinked.
I know this issue is marked as resolved but the 3 points raised above will not resolve the issue. Any time a classic board's filter includes a Next Gen project the Epic labels for all the Next Gen issues will display as "Unlabbeled- epic" regardless of which type of story was linked to that issue. The only way to completely resolve this is to fix the classic board's epic pane to also display Next Gen Epic names.