Automatically update features end date by the end date of the release
If the feature will be moved from one release to another release, end date of the feature should be automatically updated by the end date of new release.
Kote Khutsishvili
over 4 years ago
in Features
1
Future consideration
When using a date range picker tab should advance from the start date to the end date
What is the challenge? Tab advances to next field, not end date What is the impact? I have to jump from keyboard entry to mouse. Other fields cycle on tab. Describe your idea when in first date, tab should jump to end date.
Guest
8 months ago
in Features
0
Future consideration
Customize navigation terminology separate from object terminology
We love the ability to customize object terminology in AHA. However, the navigation menu language follows this customization too closely, and we would love the ability to customize the navigation terminology separate and in parallel to the object ...
Bastian Schoell
over 3 years ago
in Account settings
1
Future consideration
We would like to create a custom role that controls who can create and edit the following: * custom fields for ideas * custom fields for workspaces * idea portals * ideas layouts * ideas forms layouts * ideas portal layouts * workspace layouts * i...
Guest
almost 4 years ago
in Ideas
0
Future consideration
Ability to apply a 'Release>Portfolio' filter and list of Releases to the 'Feature>Board' release views
Hi
Would be great if we had the option to take a saved filtered view from the 'Release>Portfolio' screen (therefore if you have created a view where only 3 of 7 active releases are visible) so that when you go to the 'Feature>Board' view onl...
Guest
almost 10 years ago
in Features
2
Unlikely to implement
We sometimes upload short videos to demonstrate errant behaviour in bug reports. It would be good if we could show these in a lightbox or similar (as images are handled now) within the feature, rather than having to download and then play them loc...
Andrew Weeks
over 9 years ago
in Features
1
Already exists
Allow "To-dos" to support both Aha users and non-Aha users
What is the challenge? Representing actions where the assignee may or may not be an Aha! user What is the impact? To-dos are not usable for us otherwise Describe your idea Allow the input of an assignee who may not have an Aha account and show it ...
Guest
8 months ago
in Notes
3
Future consideration
In addition to being able to edit the layout of the Overview tab, it would be helpful to be able to specify what information shows on the Related tab. As an example, it would be good to see the sprint or story points associated with each feature i...
Lexy K
almost 2 years ago
in Epic
0
Future consideration
Comment fields: Any one with contributor status should be able to update the comments field and should be ordered newest to oldest
The comments field is used by several people to comment on status, updates, questions etc. Contributors should be able to add update comments started by other people to keep the thought thread together. Also, they should have a sort order provided...