-
Bug
-
Resolution: Fixed
-
Medium
-
56
-
Severity 3 - Minor
-
30
-
Problem
When adding a team-managed (formerly next-gen) Project via Filters to the company-managed (formerly classic) Board, the Epics of the team-managed (formerly next-gen) Project still shows as unlabelled issuekey on the Epic Pane of the company-managed (formerly classic) Board.
- Create a team-managed (formerly next-gen) Project
- Create some Issues using the Epic Issuetype
- Create a filter that comprises of issues from a team-managed (formerly next-gen) project and a company-managed (formerly classic) project.
- Navigate to Manage Boards and Create a new Scrum Board using the filters you just created.
- Go the newly created backlog and Click on the "Epic" pane and see the "unlabelled Issue-key of the team-managed (formerly next-gen) project.
Expected Results
The Epics of the team-managed (formerly next-gen) project should actually link to its child issues.
Actual Results
The Epics of the team-managed (formerly next-gen) project shows unlabelled issuekey on the Epic Pane on the company-managed (formerly classic) Backlog.
Notes
- Epic from team-managed (formerly next-gen)n will be shown in Backlog of Scrum board (company-managed (formerly classic)); as if it's "standard" issue type.
- Epic's children won't be shown in Backlog of Scrum board (company-managed (formerly classic)); as if it's "Subtask". They will be shown if it's added to Active Sprint and will be shown there (Active Sprint view).
- In the backlog, child issues show a label of sub-task from the Epic instead of child issue
Workaround
currently, there's none, as the team-managed (formerly next-gen) project is independent of other Projects.
- duplicates
-
-
- Closed
-
- is related to
-
JRACLOUD-91210 Add full support to issues from team-managed projects in company-managed boards
- Closed
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-