When assigning To-Dos to someone, it'd be useful to know how much time they're spending on it, rather than just Done/Not Done. That could be rolled into the feature/requirement/etc's time estimates, too.
This would need to be enterable by Reviewers.
Max Cascone
over 7 years ago
in To-dos
0
Unlikely to implement
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
over 7 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
over 7 years ago
in Features
1
Unlikely to implement
Customize slack commands terminology to align with company's Aha! terminology
Slack uses the default Aha terminology and it is unable to customize to suit user's preference. Not having this customization is very confusing to the users when updating Aha via slack. An improvement on this feature to allow customization will en...
Guest
about 6 years ago
in Slack
1
Unlikely to implement
The new Roadmap "Starter" report is very cool way to visually build roadmaps against multiple products. However I would not call this a report, this is a missing functionality to the releases section.
This feature needs the ability to visually dr...
Display month abbreviation on pivot reporting instead of in numerical date format
Please display the month abbreviation on Pivot reports (Jul, Aug, Sept) instead of numerical dates (2021-07, 2021-08, 2021-09). It already appears like this on roadmap reporting, and it's much easier to read at the month level.
Kalyndra Craven
about 3 years ago
in Reports
0
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
Remove image files if they are removed from the description
User flow: When writing up the description for Release or Epic or Feature I have ability to paste in the image. In the release description I would usually paste in mockups for each step of the journey (can be up to 100 images). Each pasted image t...
Guest
about 3 years ago
in Releases
1
Future consideration
Change cardinality between feature and release to 1:N
It just so happens that features are not finished within a single release and then there is problem with what to do. Create a custom status "unfinished" or make a cut at the finished work and clone the feature to next release to capture leftover w...
Daniel Pokrývka
over 4 years ago
in Releases
3
Future consideration