The Feature History has changed to also show Story/requirement History. This makes it hard to find the history of the feature or single level you are looking at. History needs a filter to filter to only 1 level and not the children levels.

Please consider remove that section if no similar ideas were found.

Please could you give us a description field on the time logging form? At this moment we cannot describe what kind of work the amount of time was for. We can only enter the amount of time. We need more insight in the kind of work that has been don...

When editing or viewing a feature for example then selecting the release "tab" a completely different release appears. Meaning you have to find and select the correct one each time. Selections should maintain the context across tabs as you usually...

This will allow a customer support or sales rep to see all ideas that have been submitted by a customer to provide the comprehensive view of their activity. This data will allow us to see problem areas and trends for what's important to this custo...

Currently only a user story can accept custom "types". But this is available to configure when you are setting up the workflow and status for either a Master Feature or a Feature. Master Feature cards should also be able to include a custom type s...

This is how things works in reality for complex applications. We have a very modular architecture for a product. ( micro services ). One product can have up 10 repositories. Even the simplest application would have frontend and backend repositorie...

It would be great to allow for cards (epics, features, requirements) to move in any "card" based view. A great example is Google Keep (Web version on Desktop). Google Keep allows for easy moving of cards and pinning of favorites to the top. Add in...

the toolips on estimates fields need consistent messaging in all field contexts, with proper messaging/tip content based on the units of the configuration. this needs to be the UX when creating (actual configured units not a hard-coded either/or t...

apply rank opens a picker to let user decide which custom field to apply the rank value to , and that custom field needs to be the field in the mappings that provide update into target tooling (my case, its ADO, stack rank). I see multiple custom ...