Currently, when a feature or epic is created in Jira and pulled over to Aha! via the integration webhook, the created by user defaults to the Aha! user who is the webhook "run as" user. Even if there is mapping setup to map the Jira "Reporter" to ...
Allow the JIRA integration to support mapping to more than one JIRA issue type and in Aha provide the ability to select the JIRA issue type to sync with
We use Aha for both Feature Requests and Defects and need to be able to designate if the JIRA issue type is an Epic, Story or Bug when linking to JIRA.
Kevin Konishi
over 8 years ago
in Jira
11
Already exists
Who would benefit? aha admins What impact would it make? keeping Aha in sync with JIRA on the release. This would also help other internal stakeholders informed. How should it work? The integrations import desperately needs additional filtering cr...
Shri Iyer
about 1 year ago
in Jira
0
Already exists
Expose "Estimate" at story creation in AHA! and push to JIRA "story points" field
Expose "Estimate" at story creation in AHA! and push to JIRA "story points" field - prevents having to go to JIRA and add points individual after time spent planning in AHA! - efficiency for PMs and Engineering
When sending a Feature to JIRA, automatically move the new JIRA epic/story into the JIRA project's Backlog
When we sync Aha! Features into JIRA, we're ready to begin planning sprints that will include the resulting JIRA epics/stories. Extend the JIRA integration so when new epics/stories are created from Aha!, automatically move them into the JIRA proj...
Allow the mapping of Products in Aha! to Component/s in Jira.
In order to automatically assign Aha! items pushed over to Jira to the right component, I've had to create a custom field in aha! with a pick-list of the component names from Jira. I c...
Max Cascone
about 7 years ago
in Jira
3
Already exists
Allow users to refresh all Aha! features from a linked JIRA integration.
Currently, only the changes made to a JIRA issue are sent over to Aha! through the webhooks. We should have a way to force Aha! to synchronize all descriptions and fields from JIRA for an entire release.
Alex Bartlow
about 9 years ago
in Jira
0
Already exists
Ability to use "belongs to" relationship in Aha to map to "is contained by" link type in Jira
I don't see a way to connect Aha's "native" record hierarchy to a similar hierarchy in Jira. Using epic --> feature as an example, if I select the parent epic while editing a feature, that creates a "Belongs to epic" relationship under that fea...
Gene Lewin
over 2 years ago
in Jira
1
Already exists