In Jira there are multiple types of issues in an EPIC with Story points: User Stories for development and will be released into Production Tasks for all items that is not released in Production (documentation, support, investigations, etc.) Bugs e...
Would be great to have the progress bar not just calculate on some field completed, but also show as a sort of segmented progress bar, where you can see the percentage of items in another status category. This would allow to have in one view a cle...
Kristof Dewulf
over 3 years ago
in Epic
0
Future consideration
Please add the concept of "Sprints" separate from "Releases"
Please indulge me be allowing me to start off with some definitions.
Sprints are generally 1-3 weeks long, happen at a regular cadence and don't have anything to do with ongoing projects/releases other than the fact that Stories related to a proje...
Apply filters to the Milestone Chart View and keep milestones off the chart until explicitly charted
We have a long list of master features for our product line that need to be prioritized at that level. It would be helpful to do it iteratively, and one way to do that is with filters that allow us to focus just on the master features associated w...
Guest
about 5 years ago
in Epic
0
Future consideration
When scorecards are applied to a product line, updates to the scorecard should not be applied to released epics. Since notifications for scorecard changes cannot be suppressed, changes to the scorecard result in a massive flood of email notificati...
Rachel Hiatt
over 3 years ago
in Epic
0
Future consideration
Despite your careful research, consideration, and planning - that epic you fought for inclusion into a release just isn't going to get started any time soon. Sprints later you realize that it's probably not going to happen ever. Holding on to hope...
Erik Didriksen
over 5 years ago
in Epic
0
Already exists
The Prefix for all Master Features is 'E', this is a suggestion to change this globally to M to align with the default terminology.
EG PRODUCT-E-123 should be PRODUCT-M-123 instead.
Guest
over 5 years ago
in Epic
1
Unlikely to implement
We have sophisticated intake requests for portfolio work for which we use at the Epic level. To streamline this for our team we would like to have one form where a user is guided through conditionally displayed questions based on previous question...
Guest
almost 4 years ago
in Epic
1
Future consideration
In complex software development we often have features that require the coordination of changes across multiple software products. In these cases we create an Epic to represent the overall capability we wish to deliver, and place related features ...
Andrew Foster
almost 2 years ago
in Epic
2
Future consideration