Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira Cloud: Issues can't be used as swimlanes and (Sub-)Issues of an Epic don't show up on a Board

René Schubert
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 4, 2021

Hi,

I created a filter-based Scrum board to be able to see all the issues of multiple projects in Jira Cloud.

What I want is to

  • see only non-epic-issues/stories (including the ones that are assigned to an epic / have an epic as parent-issue) on that board.
  • see the epic that issues are assigned to as colored label on their cards.
  • use stories as swimlanes in the "Active sprints" view so that I can also see the states of the sub-tasks of my stories.

What I get:

  • Generally, epics are handled like stories in that board and not actually as epics.
    • Epics are visible in the backlog as part of the backlog (but not as "label" on the cards).
    • As soon as I assign an epic to whatever issue, the issue is handled as a sub-task and is no longer listed in the backlog.
    • When I configure "Stories" as swimlanes, epics are displayed as swimlanes, instead of stories.
    • Epics surround stories in the "Active sprints" view with a gray box just as I would expect stories to surround their sub-tasks.
  • Epics can't have a label or color and are displayed as "unlabelled-XYZ-123" without color in the "Epics panel".
  • If I try to drag/drop a story on one of the epics in the epics panel, I get the following error message:

    The request contains a next-gen issue. This operation cant add next-gen issues to epics. To add a next-gen issue to an epic, use the Edit issue operation and set the parent property (i.e., `"parent":{"key":"PROJ-123"}` where `PROJ-123` has an issue type at level one of the issue type hierarchy). See <a href="https://developer.atlassian.com/cloud/jira/platform/rest/v2/"> developer.atlassian.com </a> for more details.

I already tried to tweak the filter (exclude epics, include sub-tasks) to get what I want, but it didn't help. Is there anything I can do to fix that (e.g. define the issue type "Epic" differently)?

Thank you so much for your help!

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events