I understand that Features are not to be touched by Reviewers, but User Stories are items that typically get assigned to non-product managers. It would be extremely useful to allow Reviewers to log time on Requirements, so the Product Manager can ...
Max Cascone
almost 8 years ago
in Features
1
Unlikely to implement
Limit contributors or another role to edit selective fields
Contributors or another role should have the capability to edit selective fields (ie Internal Notes or Description) vs all fields like the product owner. By default, the field should be editable by the product owner, but there should be a setting ...
Christina Wongbuphanimitr
almost 8 years ago
in Features
1
Unlikely to implement
Allow sorting on feature board by goals and initiatives
You can sort features on the board by a variety of values, including the associated master feature. For teams looking to organize and prioritize based on strategic goals and initiatives, it would be helpful to also be able to sort records on the b...
Danny Archer
over 4 years ago
in Features
0
Future consideration
In the Features roadmap, the info of "Not shown in notebook" really clutters the view and doesn't add any relevant info.
I also am having a hard time understanding what it is that triggers a feature to not be shown in a notebook.
Regardless, I don...
Max Cascone
almost 8 years ago
in Features
1
Unlikely to implement
We design our workflow per "Workflow Approval Design.JPG" that require approval for each status transition. Take "Discovery" for example, 4 approvals would appears in To-Do tab. Approving one of them to trigger status change, and the rest of the 3...
Hank Liu
over 1 year ago
in Features
0
Future consideration
Make record ID's distinct for records shared with Develop team
When users are notified of Product features that are assigned to a Develop team, the notifications link the users to the Roadmaps board where it originated. On the reverse, Develop features that get assigned to a Roadmaps release, direct users to ...
Stephanie Lechner
over 1 year ago
in Features
0
Future consideration
Similarly to how custom fields can have optional descriptions. The same would be good for tags, so that additional information (essentially explaining the tag in more detail) can be conveyed to other users. This would reduce the need to either cre...
Sam Banks
over 4 years ago
in Features
1
Future consideration
Trigger Automation of requirement cards based on Feature status
As a developer, I need to ensure that I have a peer code review and test my code. I track that its complete and who did it by creating requirement card and assigning it to another developer. This allows the PMs to track that that was complete. I c...
Guest
over 4 years ago
in Features
1
Future consideration
Being able to copy an initiative with its underlying structure, such as subhills and epics. The team I work in has some recurring tasks for every quarter and adding the same subhills and epics to the new initiative takes a lot of time.
Aleksandra Marciniak
about 3 years ago
in Features
0
Future consideration