Be able to send just the features and requirements over to Visual Studio TFS for a Release Phase.
Currently we can only send over the Features and requirements for the entire release, or feature by feature.
Having the ability to do it per phase...
Guest
about 9 years ago
in Releases
0
Unlikely to implement
Support shortcuts for keyboard layouts set to other languages
Right now, shortcuts like Ctrl+V, Ctrl+Z work only for English keyboard layouts (Windows). If I use another language for the keyboard layout (e.g. Russian), keyboard shortcuts don't work.
Chrissi McNamara
about 3 years ago
in Notes
0
Future consideration
When exporting a note to a PDF, the table of contents does not function in the PDF. In the same way that an export to PDF works in text editors like MS Word or Google docs, the ToC should function in the PDF.
Chrissi McNamara
about 3 years ago
in Notes
0
Future consideration
Ability to call attention to dates in notes/record descriptions
It is often necessary to call out important dates in a note or feature description. While it's possible to manually format the date, it would be nice if there was an automatic way to add a visual element to quickly call attention to these dates in...
Chrissi McNamara
about 3 years ago
in Features / Notes
0
Future consideration
Story map should have a setting allowing to block automatic adding of rows
Story map should have a setting allowing to block automatic adding of rows especially when features are moved vertically for reorder . Today for larger maps the map grows vertically in uncontrolled way making it difficult to manage
Guest
about 3 years ago
in User story map
0
Future consideration
Add related ideas based on the same category for existing ideas
It would improve our customers' understanding of what other ideas are category-related so they don't create additional ideas unnecessarily. It will also help us as administrators to view from the customer perspective and group ideas more efficiently
Guest
about 3 years ago
in Ideas portal
0
Future consideration
When creating a new Feature in Aha! and pushing the data to Jira: Aha! should have a way to handle sending data to Jira fields which are: a) required b) Autocomplete Renderer so the Epic can be created and not rejected by Jira
I created a new feature in Aha! When I attempted to send the changes from Aha! to Jira, expecting a new Epic to be created in Jira, I got the following error: The following required fields could not be set on the epic: Fix Version/s. Please check ...
Guest
about 6 years ago
in Features
8
Already exists