Features

In the knowledge base for scorecards, you say "if you want multiple people to weigh in, it's best to have a live collaborative session or request they provide comments for each feature." For features that are past the idea phase (eg: imports from ...

Story As a PM, some uncompleted Feature cards become outdated and would be best revised back down to Ideas. Case A bulk manage tool that downgrades Feature cards to Ideas would be very useful. Potential field mapping could be presented to the user...

Who would benefit? All Product & Project managers who need an additional level of organization to do "feature" level releases. This is especially useful since we train & speak to feature level releases in Agile framework & have no actu...

Easily create relationships for traceability on dependent or related features. Manual editing via a dialog box is old-school and very time consuming when working on large products.

When I am doing a bulk update on one feature and have accidentally selected many more than one it would be helpful to have an alert or warning for which a threshold could be set. For example, if I am about to bulk update over 100 features the syst...

Who would benefit? Product Managers and Product Owners What impact would it make? Reduce clutter in goal selection lists by filtering out historical and deprecated goals when relating to records. How should it work? Goals have time frames. Annuall...

It would save a lot of time if the release list within my feature and master feature would open defaulted to my application or at least the application I am currently attached to in the release already applied. With the current setup I have to wai...

We are experimenting with using release phases for contain our sprints (1 to 2 weeks) while the release itself represents several sprints + some extra testing/beta phases. It would be great to be able to filter in the Feature Board, Kaban Board, F...

At the moment when you moved a feature to shipped then the time recording changes to be the same as the estimate. So for example if I estimated 3 days, actually only took and recorded 2 days when I ship the feature the time taken changes to 3 days...

I have many feature requirements that are different than those that are listed for the feature. Allowing tags against the requirement itself would allow for further categorization of the requirements