A way to retrieve all the fields, including custom fields, and metadata for an item type (eg. Feature) using REST.
Field information would ideally include the type of the field (string, number, drop down, etc.), and properties such as if it is a required field or read only field. This would allow the integration to know what fields are available when creating,...
Guest
over 6 years ago
in Integrations
1
Unlikely to implement
Some teams use Whimsical as a document repository, similar to how Confluence is utilized in many organizations. We would like an integration with Whimiscal to share Aha information with our engineering teams.
Veronica Melin
over 3 years ago
in Integrations
0
Unlikely to implement
To help with creating integrations between systems.
The specific case would be an automated system that keeps aha synchronized with an external system. The system needs to log in as an user to make updates, but the system does not need to see webh...
Tim McCaskill
over 6 years ago
in Integrations
0
Future consideration
enhanced Kanban workflow - Similar to leankit or swiftkanban
we are in the process of switching over to Swiftkanban as the kanban board is great to use and allows us to create end to end workflow.
We will more than likely continue to use AHA for strategy but ideally we are looking for a single solution that...
Guest
almost 10 years ago
in Wanted
2
Already exists
Displaying information which is relevant to the user
The count in Settings->Integration updates is for all workspaces, including those to which I have no privileges to action.This can be confusing as when user selects the option, there are no updates to process.
Guest
over 3 years ago
in Integrations
0
Future consideration
Add Ability to not send a specific release to Rally on Master Feature or Feature
Rally has a concept of Backlog where the Release is set as 'Unscheduled'. But there is no way in Aha! to assign a Master Feature or Feature to something like 'Unscheduled' so that the Release information does not get populated in Rally. We want to...
Amy Lackas
over 6 years ago
in Rally
0
Future consideration
Currently, enhancements are all listed together. Hidden in the text, you can usually find an "Availble with Enterprise+" or similar. But it's time consuming, and annoying to read about an enhancement, and then find out it's not relevant to your pa...
Julie Edwards
over 3 years ago
in Wanted
0
Future consideration
When sending an Epic to Jira, allow sending of all /updates to Features
Currently, when you send an Epic to Jira, all of its features are sent, but they are sent as the default Feature type instead of the types that they were actually categorized. Often the product person is working in Aha! and doesn't want to yet sen...
Karie Kelly
over 3 years ago
in Jira
0
Future consideration
Add Product Prefix field as a choice in the JIRA integration
We integrate Aha! with multiple JIRA projects and often use the product prefix as the Component to identify the source of the ticket. Today we use a constant and add that manually. Adding it from the prefix would save us a lot of time!
Gordon Kent
over 6 years ago
in Jira
0
Future consideration