Better requirements link handling in Jira integration
From the Jira "READ SECOND" blog post: "If a new issue is created in JIRA that belongs to a record that is already link to Aha!, then the issue will be automatically imported to Aha! This applies to issues created under a version, stories created ...
Aaron Bawcom
over 9 years ago
in Features / Jira
1
Shipped
Currently, we need two Jira integrations - one for Bugs, and one for everything else. But when importing/linking Bugs, they get linked to a regular ol' Feature of "New" type.
As someone in this situation, i want imported/linked Jira Bugs to set t...
Two Way Jira Sync for Initiative/ Epic custom fields
As far as I am aware you can only map feature custom fields, and I'd like to be able to maintain due dates, team and other custom fields at the Initiative level.
allow clicking on JIRA ticket-id in feature_grids view
right now if i add the column "jira key" (or even jira-link), and i want to see the ticket in jira, i have to copy it from the UI, and go to JIRA to paste it (or my browser's URL) to see the ticket in JIRA.this can be solved by making the col to b...
Ability to sync more than one Issue Type to a Record
It's critical for us to track bugs/defects in Aha! related to a specific release but these bugs/defects belong to Features that have other WIP Stories. We need to be able to sync different Issue Types from JIRA to the Requirement record in Aha! Th...
Add integration support for the new "Users field" custom field type with JIRA custom field type "user picker"
We just launched the new custom field type "Users field". It would be powerful to be able to integrate this with JIRA and specifically, integrate it with the JIRA custom field type "User Picker".
Improve warning for integrations "Update Records" action
For a development tool integration (i.e. Jira), there's an "Update Records" button. When clicked, you get this attached warning. This doesn't warn you that Aha! will send data for any one-way mapped fields (Aha! --> Jira) as well. It would be h...
When a feature is linked to an existing epic in Jira, sync the child stories to Aha! as requirements
We map Aha! features to epics in Jira, with Aha! requirements as stories. When an epic already exist in Jira with child stories, I want to link that epic to a feature in Aha! and have the child stories immediately sync over as requirements.
One of the fields we have in JIRA has over 100 values. Mapping each value to Aha is a no go. The interface to manually drag and drop each value to the correctly mapped value is slow, cumbersome and took over 60 seconds to just do 1.
It will be pr...
Features created due to integration to appear on Releases - Overview, Details view
This would be very helpful since without it Product Manager doesn't get to know if Dev team has added any new stories during grooming. Currently such stories although result in creating features, they are only visible on Feature Board view under r...