@Kevin Bui Filter them away works in the Roadmap view but how do I get rid of the done Epics in the backlog view. I don't want to see all the already done Epics when trying to assign issues to Epics and it will only get worse when we have closed a few Epics? In the old version with the very nice drag and drop the epic didn't appear if it was done. How could that be done?
How do I go about setting the Epic when I create a new Story? I see it happens automatically when I do it on the board but from the Create dialog the field is not there. This means I need to create the Story and then press the ... in order to set the Epic.
Hello, is it possible to add new statuses to the epic in next-gen? Exploring whether it's possible to use epics as "shippable MVP/feature" but Todo/In Progress/Done isn't enough in terms of a workflow. Also - although epics can appear as timeline roadmap bars, is there anyway in Next Gen to have them appear on a board of their own?
The only other option would be to ignore the epic and create two next generation boards - a Scrum one for the team and a Kanban one for the shippable features... with issue links between the two.
Can we connect an Epic in a Next Gen Project to a Story in a Classic Project? Some of our teams are still on Classic Projects, and we'd like to link to them from Next Gen Epics.
This is great, and thanks for adding colours to Epics. However we still can't use this feature as its only for Next-gen projects which would be fine if you could link Classic issues to Next-gen Epics, but you can't..
@Bree Davies, this next-gen projects are just the right direction jira has to move in in my opinion. Biggest hassle for us has always been roadmapping and actual jira work taking place.
Few additional requests please.
1) Epic Progress indicators - on the roadmap according to points burned or number of stories completed (would like to pick this per epic, i.e. we don't way bugs logged) would be great for constant feedback to the stakeholders
2) Time logging - on certain projects, like overheads etc. which do not get weighed, but we track time against in the older projects, we just Add Work (2h or 1d etc.). This field would be nice on these new-gen projects.
3) Kanban Burnup chart - currently we export the backlogs of our projects into excel, where we automate a backlog burnup against your current velocity, giving a nice pessimistic and optimistic completion view down the backlog. A report for this would be great, using the best and worst velocities over the last X number sprints as your pessimistic and optimistic velocities (or manually entered for a team).
When I run a issue filter on a new gen project, and then drill into a story, I can _not_ see the epic the story is linked to. How do I view the epic from the story?
Hello, We have the following problem with a next-gen epic.
All of the projects we have in our JIRA are classic, while we have one next gen project DEVOPS.
We have several boards that are built on the following approach: - the board filter includes issues for a particular project, - and represents them in epic swimlanes (according to the rank of corresponding epics),
- epics themselves may belong to different projects.
To make this approach work, the board filter includes issues from particular project OR epics from any project.
This approach works perfectly fine with one small exception. An epic from the next project DEVOPS is included on all such boards as an actual issue in 'Issues without epics' swimlane. This epic doesn't have any issues that are relevant to this project or this board, so it is simply included in the filter because of that 'OR epic from any project' condition. Classic epics are not represented as swimlanes if they don't have any issues relevant to the board inside. What could be the reason for the classic board treating a next gen epic so different? Is there a way to exclude nextgen epics from the filter?
Love the look and feel of next gen projects, exploring moving our digital marketing team's board over in the next few months.
For the roadmap feature, would be great (mentioned by a few others in this thread) if you could visually see amount of stories completed displayed on the epic bar (i.e. 21 out of 40 stories done for specific Epic) as well as how many story points completed for the actual Epic (i.e. 65 out of 100 story points completed for this specific Epic).
Nice. But i would really love to have an EPIC BOARD in the Project, where i can move my EPICS in a special Workflow.
I tried to put a standard jira board and filter the epics from the new gen project. but then i cant style my own workflow because it uses the next gen story workflow...
Hi - Any update on when we will get the epics panel back in the sidebar and the ability to color code epics?? I would love to use this next gen project scheme with my technical team as they don't work in formal sprints, but am having difficulty setting up the project the way I like. Please bring this feature to the Next Gen Kanban project ASAP
I'm also with @Ian Sheffield , @Michael Pavey , and @Mahmoud Elmashad -- the list of epics on the left of the backlog provided several excellent UX and visibility benefits. It made organising issues into Epics easier. It provided a high-level visualisation on the tasks at hand when organising sprints, since all the Epics were visible at once in a list. And the progress tracking through each Epic also provided a good higher-level measure of progress when deciding how to schedule backlog tasks.
The new UI looks great, and the roadmap is a great feature, but I think we lose a lot without that Epic list in the backlog! Please consider bringing that back.
Sometimes I will export tasks into excel/csv for dashboards/presentations - however I notice that in the extract, I don't see what epic that task/line item is attached to, is that something we could see down the road?
153 comments