I'm currently using the Capacity bar on the features screen based on points for my releases. Right now the bar shows 'Work done' (green), 'Work remaining' (blue) and then white space for points left. When I scroll over the green & blue section...
Joseph Abromaitis
about 7 years ago
in Features
0
Already exists
When copying a feature, pop up a link so that I can get to it quickly
As a Product Manager, I would like to be able to quickly open a new feature that was just created by copying another feature so that I don't have to search for it before I can use it. Stretch goal: Do this for master features, ideas, initiatives -...
Tom Beck
about 7 years ago
in Features
1
Already exists
Feature and Master Feature Views of Kanban should by sync'd, in line with logic used for the Board views.
When I’m in a Kanban, I can switch easily between Master Feature and Feature (which we call Value Proposition), but I can’t figure out how to sync the name in each side.
If I applied a product name to the saved view (e.g., SCHEDULES – Value Prop...
Guest
about 7 years ago
in Features
0
Already exists
Filter initiatives/releases available for linking to only Active items
When I am linking a release or story to an initiative, and over time my initiatives have grown to a list of over 40 initiatives, the list of available initiatives to link to doesn't fit on the screen and contains old initiatives that are no longer...
Guest
over 7 years ago
in Features
0
Already exists
BUG: master feature name doesn't display on the feature card unless a master feature exists for that product
In designing the feature cards for new products, the "Master feature name" doesn't display on the feature card unless a master feature already exists for that product, even though master features are turned on.
Guest
over 7 years ago
in Features
0
Already exists
If some one enters the wrong amount of time in the Work done input, it seems impossible to undo that.
Users should be able to correct mistakes, without having to delete and re-create the feature again
Guest
over 7 years ago
in Features
1
Already exists
Instead of using a seat (email / password), we would like to have an API key mechanism for authentication. This can be shared with the integration engineers and is not tied to an individual user.
Guest
over 7 years ago
in Features
2
Already exists
Every feature within the release can have its own milestones which cannot accurately be represented through requirements. Basically think of requirements stemming from the milestones for a particular feature. Would love to have that functionality ...
Guest
almost 8 years ago
in Features
0
Already exists