I have a software type board, minimal customizations to status, but left standard ticket types.
For some reason some epics appear on my board as epics, and some appear as 'issues without an epic'. I am not sure why, it isn't after ticket 100 then all epics are now not recognized as epics, it it random.
All the epics have level-0 ticket under the level-1 epic.
I just want to have epics without an epic to behave like normal epics in the same project
Hi @philipf
For the epics shown on the board in the "Issues without Epic" area, do any of them have child issues, or child issues which match the board filter?
If not, that may be why they display there.
Kind regards,
Bill
They all have child issues, if they don't then they weren't appearing on the board. So I always put in a placeholder ticket so I can find it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Comparing your board's filter and the placeholder issues, added as children to the epics, would they display with that filter?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is weird, I created a new epic in the board and it acts normal. But older ones don't. I then updated a ticket by cleaning up sub-tasks and it is now not counting as an epic.
There are no filters applied, all the epics have sub-tickets within the same project (i thought maybe since refencing other project tickets may be causing the issue).
I am stumped,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I wonder if this is related to the changes with the epic fields, which continue to roll out this week, and how boards show swim lanes by Epics. One of the field changes sunsets "Epic Link", replacing it with "parent" for company-managed projects.
At this point, I recommend creating an Atlassian Support ticket here: https://support.atlassian.com/contact/#/ As you are a site admin for a paying Jira license you can do that. I did a quick check and did not see this symptom in the public backlog as a defect.
When you hear back from them, please post what you learn to benefit the community. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.