Skip to Main Content
ADD A NEW IDEA

Jira

Showing 252

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 about 2 years ago in Jira 0 Future consideration

The Aha <->Jira Integration Mappings should be Transparent to User

Presently, the record level mappings between Aha and Jira are opaque to the user. This makes it quite difficult for the user to debug the syncing.Without this info, it is quite challenging to get the Integration working. If the integration does no...
Guest over 2 years ago in Jira 1 Already exists

Resolve links - Aha-JIRA integration

Wish links are resolved to the respective JIRA Tickets. Not everyone (non-Product Team) has access to Aha :(
Guest almost 3 years ago in Jira 0 Future consideration

Ability to map Jira Web Links with Aha! URL at Integration

Why is it useful? Web links at Jira are used to show all the links associated to an issue/record. Who would benefits from it? Its easy for all users to view Aha! link at Jira epic or story rather than having it at a custom field. How should it wor...
Tej Namala almost 3 years ago in Jira 0 Future consideration

Synchornize workflow approvals from Aha! to Jira

Allow for mapping Aha! approvals to Jira via the integration. When a team member moves an item in Jira to a status that requires an approval in Aha!, pass the approval status back to Jira once it is updated in Aha!
Guest almost 3 years ago in Jira 2 Future consideration

Many to one mapping for field integrations

The use case for this is we have 7 different fields for grouping development teams containing over 50 total teams in Jira. We would like to be able to combine these into a single field in Aha for the purpose of running reports to show which of the...
Jerimiah Rudden almost 3 years ago in Jira 0 Future consideration

Integration last used field

To enforce usage of Aha when communicating priorities and reporting progress against developing those priorities, want to see the last time updates were sent to/from Jira so we can track against that date.
Danielle A almost 3 years ago in Jira 0 Future consideration

Trigger status change based on record % complete

E.g. if engineering has reported that 100% of work on a release is complete via the Jira integration, update the status to 'ready to ship'
Danielle A about 3 years ago in Jira 0 Future consideration

One epic in Jira

When creating integrations to Jira (master features and features to Epics and stories, within in several Jira board in the same instance) the first created epic in Jira should be the only epic created. Not one per integration/Board. At it is set u...
Guest about 3 years ago in Jira 0 Already exists

Align release with Jira sprints

Have the option in the integration settings to sync release with sprints in Jira There is no current way to represent a sprint in Aha yet that is how most people develop these days Currently whenever I move features between releases I have to manu...
Guest about 3 years ago in Jira 0 Unlikely to implement