Redirect users to accessible version of link if they do not have access to internal link
Users submit requests via an externally facing portal. Once that request is received, the team handling the request have one view of the request, while those who do not have that internal access can only see the publicly visible version of the req...
Guest
about 3 years ago
in Features
0
Future consideration
Create ability for a feature to support multiple epics across workspaces. This will allow a single team that's working on a single feature that supports multiple epics across multiple teams. Currently we have multiple teams enabling a feature and ...
Steven Schafer
over 1 year ago
in Features
5
Unlikely to implement
Add "current user" as a selectable option in all user filters
As an Aha! user, when I filter based on User ("assigned to", "created by", etc.), I should be able to choose "Current User" as an option. This way, when I save and share a View, the results are dynamic and update based on the signed in User.
For e...
Matthew Monahan
over 5 years ago
in Features
1
Future consideration
In general our portfolio workflow involves us managing our backlog in Aha, but then creating a physical board that has all the current and upcoming features on a standup board where all of our team members can gather and discuss. Working only onli...
Guest
over 8 years ago
in Features
5
Unlikely to implement
Allow Reviewers to Change Status and View History on Features and Master Features
Our workflow starts with product management creating a roadmap of features and master features in Aha. Engineering responds by changing the status to "understood", "committed", "will not fit", etc. Seeing the history on that provides a record of w...
Julia Doyle
about 6 years ago
in Features
0
Unlikely to implement
Sometimes I use Features Board to discuss with internal stakeholders, and I don't feel comfortable showing internal release date there. External normally has some buffer and more generic (like a quarter of the year, when I am planning to release)....
Pablo Perez
over 8 years ago
in Features
6
Unlikely to implement
Who would benefit? users in need of detail What impact would it make? provide additional method of validation or review How should it work? When adding columns to a List, whether features, epics, requirements, etc. it would be nice to have "Last m...
Guest
about 1 year ago
in Features
0
Future consideration
Add a tooltip to explain that shipped releases can't be chosen to be linked to a feature
I think the issue is that this is not communicated in product on that field.. Some help text there describing how the drop down list is derived would clear up any confusion.
Simon Ravenscroft
6 months ago
in Features
0
Future consideration
Allow a feature to transition to different release phase when feature status changes
In order to make best use of multiple release phases I would like to be able to automate the moving of a feature from one phase to another when I update its status. For example a feature will be In design as a feature status and part of the Design...
Laura Phillips
over 3 years ago
in Features
0
Future consideration
Who would benefit? PMs, Product Ops, docs team, What impact would it make? Easier to use and navigate to-do lists within discrete phases How should it work? I'd like to be able to nest or group to-do checklist items under a higher-level checklist ...
M K
about 1 year ago
in Features
0
Future consideration