We use the Github integration for a few of our projects. I have it configured to import Features to Issues and Requirements to Issues. It would be very helpful to exclude some records during the import process. For example, I recently sent a Featu...

Problem If a Version is exported from Aha to Jira using the integration, and a fix version with that same name already exists in Jira, Jira will response with HTTP status code 400, and a JSON payload: {"errorMessages":[],"errors":{"name":"A versio...

Linking BMC, Value Proposition Canvas and Personas with Strategyzer

Sometime companies use customized templates with custom work item types. Currently the ADO integration only supports integration with the standard types like "initiatives", "features", "Requirements". Our template supports a custom type called "PI...

Enable the parent - child hierarchy for Aha tool so that we can see the view for parent-child relationship. Same like Jira we have parent -child relationship concept of subtask we need in Aha same functionality.

Stories that are pushed to Rally from the Aha Parking Lot are creating a release in Rally titled Parking Lot. I would like to see these user stories not be assigned to a release in Rally, that way they will be be displayed on the backlog.

It looks like if you add a custom field in JIRA, Aha will not recognize it unless you delete the integration and add a new one, which means you need to relink everything. You should be able to go through the integration UI and add new field mappi...

We currently have no way for Rally to tell Aha that a feature is fully groomed. This would help considerably to give Product team visibility to the feature grooming status in AHA for PI Planning and priority alignment. Aha has a feature status of ...

It is common practice for teams to have multiple Trello Boards. For example, in our organization, we have our "current development" board with Next Up, In Progress, Awaiting Validation, Completed ... and but like any product organization, you do n...

Use case: Aha! releases are mapped to Jira sprints as a field mapping under features. Currently this mapping is only supported in one direction, Aha! to Jira. It would be helpful if this mapping supported the flow of data in both directions.