I migrated some issues with their epics from a one project to another and almost everythig was put where it should be, except for one epic that still shows in my current Kanban board.
This epic is done and released, but it still shows in the board, I don't know why.
Since this is something we are not currently working on, I find it a bit annoying to have it there. Is there a way to hide it or remove it from the board without deleting the epic?
I have tried every trick I found (editing, moving, etc.) with no success.
Any guidance will be appreciated.
I can see on your screeshoot that you're reffering to the Epic Panel no the board itself.
To remove the epic from this list you have to change the EpicStatus field to Done. You can do this from the Epic Panel->Select the issue->Click the small Square/triangle icon->"Mark as Done"
Or you can use our Plugin the Agile Board Filter which includes a Live search and next week we'll be releasing new filtering options:
I think we'll need more information to answer your question. First, what is the query (filter) powering your board? We need to figure out what in your filter is letting that issue hang around.
Go to the board and click the "Configure" (JIRA Server) or "..." (JIRA Cloud) button at the top right. (You'll need to be a board admin to see this button.) Click the "Edit Filter Query" link to go to the JIRA search results page which will display the filter.
Some screenshots might help us as well.
In the mean time, a poor man's fix would be to exclude the issue ID from the filter. You could add "and issue != key-1234" to the end of your filter.
No need to delete your Epic!
We're standing by for more information,
I don't see a "Configure" button; I click on the three dots in the top right and go to Board settings. I assume that is what you are referring to? There I see "Quick filters", which currently have to active filters:
assignee = currentUser()
updatedDate >= -1d
I think these filters come by default as I did not created them. Not sure exactly what they do.
I am attaching a screenshot. The epic I'm referring to is "Planning for release 1".
That's what I was asking. :-)
When you do a move, the Project it is associate with should change as well. The new ID would not be CCDB-220 but the new project code along with the next number for that project.
Have you actually tried to do a move? If so, what happened because it did not actually move.
If not, try that first.
By the way, in the RAC Dev project I had several completed epics. I moved them all at the same time to the CCDB project. All other epics, except for the Planning one, are in the right place. Since this was done in a bulk change, I don't understand why this single one ended up showing up in the CCDB Kanban backlog. Weird.
Oh, I think I understand now - it just has the wrong status. Can you not just change the status from from Backlog to Done (moving in interim statuses if necessary)?
I had the same issue where I created EPIC's to track parts of the project then tasks under the EPIC. I found that if you close the tasks and the EPIC task it breaks and still shows up on the Panel. As a work around I closed out all the Tasks under the EPIC, then used the option in the panel to mark the EPIC done which will remove it from the Dashboard. By marking the EPIC done directly other than the Panel it remains in there and you have to delete it since I can't figure out how to reopen it.
Actually I figured that if you Start progress again it reopens the task and you'll be able to close out the Epic on the panel, then you have to go the EPIC Task and mark it done. Make sure you close out the EPIC Panel first otherwise it wont remove it.
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events