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 search for words who are part of separated list
Searching for the word "error" will not find features with a name "Indicate if terrain is processing/done/error in designs". This is due to the fact that AHA considers "processing/done/error" a single word. I suggest to treat the chars /,-,\ as wo...
Qua3926
over 1 year ago
in Features
0
Future consideration
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
Improve sorting option - Color by Flagged Records at Features level and Flagged record view to include only flagged features in Gantt chart
Sort color by option would be more relevant to bifurcate between Records with risk and no risk rather assigned/ release. May be worth to include color by " Flagged Records" which should cover both Epics and features in Gantt chart view. Filters in...
Guest
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
almost 5 years ago
in Features
1
Future consideration
Features List - Views need an option to be NOT EDITABLE
I have created and shared views for the team to use, but then someone edits the view which is NOT desirable. If they want to change it, they should first copy the view and then save it to a new name.
Please add the ability to set a view to NOT E...
Guest
over 9 years ago
in Features
2
Already exists
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