Features

Who would benefit? All users What impact would it make? Long descriptions and acceptance criteria can easily be read. Especially if charts are involved. How should it work? When in a Parent Feature and the user selects the export icon in the upper...

When mapping statuses between a Team and a Workspace, I need to map each team one at a time. When teams are sharing the same workflow, I'd like to map each shared workflow to the current workspace statuses; rather than one at a time. This will all...

Who would benefit? Every person editing a feature or epic What impact would it make? As i write more on more document in the notebook, it shall be logical to be able to add these documents to my features How should it work? i shall be able to sele...

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...

Who would benefit? my whole org What impact would it make? would allow for us to standardize on feature/requirement description based on the feature type selected when creating a new feature How should it work? When adding a new type, in descripti...

I use nested folders to organize the images that I am uploading to be included in feature and item descriptions. Sometimes these folders can be very deep, six or more levels. Every time I place an image in the feature/requirement I am click the im...

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...

Who would benefit? Product Managers using Prioritization functionality as well as the feature board What impact would it make? It would reduce the time and administrative burden with feature prioritization while improving consistency across the pl...

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...

We use ideas to capture pieces of customer feedback. As such, it would be really useful to have a calculated field that counts the number of ideas linked to a feature. This would help us capture prevalence in prioritizing features. It would be rea...