When editing Tags list on "Config Tags" page, having the ability to bulk edit Tags (Delete specifically) would be very handy as the tags list could become very lengthy and removing multiple tags (with a criteria e.g. Tag starting with RFP#) takes ...
Work requests: option to promote to an existing record, instead of creating a new record
Work requests are helpful for establishing and managing work records that are dependent on each other. Sometimes, the work records both exist when the dependency is identified. Instead of creating a new record through the work request, we rather w...
Add Competitors, Business Model, Personas and Vision to be terms which can be renamed under 'Terminology'.
Competitors is not hugely relevant for the large areas of the product organisation currently working with. However, being able to re-use competitors and it's charting capability to represent some strategically important to them is. For example, it...
Project Parker
almost 8 years ago
in Strategy
12
Shipped
We would like the ability to have new records created in JIRA/Rally automatically import into Aha!
Currently, they have to be accepted in Aha! prior to import. This causes an extra step in our workflow we do not wish to have to go through each time.
Danny Archer
almost 8 years ago
in Integrations
7
Shipped
Add 2-way integration mapping for release start and end dates
Release start date can currently only be mapped 1-way from Aha! to Jira (or any development system.) This is because that date used to be calculated based on features and phases in the release. Now that this date is set manually, it should be poss...
Link existing GitHub issues with a new Aha! Feature
The current Aha! - GitHub integration lets you sync features to GitHub issues. This won't work in the opposite way. However, It'd be nice to have an editable field to reflect that the Aha! feature is linked to a GitHub issue.
After provisioning a new user via SSO, go to their pasted URL instead of the homepage
What is the challenge? An Aha! user shares an internal link to an Aha! report. Someone in the company without an Aha! account clicks on that link. They are automatically provisioned an account via SSO and has view access to all workspaces. Instead...