Jira

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.

When integrating AHA / Jira the field mapping only shows fields that can be editable. We are looking to bring in Created Date and Resolved Date on both the Jira epic and Jira story. These fields are dynamically created and populated based on the f...

In this scenario, there is one Program product workspace in Aha! and one Program project in JIRA which contains Master Features per Agile Release Train. All Stories (Aha Features) and sub-tasks (Aha Requirements) are with one or many Agile Teams (...

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...

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...

Today the Aha JIRA integration will leverage the user account setup in the integration settings as the actor for all integration sends between the systems. This creates a lot of confusion for who actually made changes in one system or the other. F...

What is the challenge? Could not use the new Jira object in the mappings What is the impact? Teams want to group similar Epics in capability. without this, we can group them for tracking Describe your idea We already have Aha Integration to Jira i...

We would like to specify a conversion factor or formula to map numeric fields between Jira and Aha! numeric fields, especially a Jira number field and Aha!'s Original Estimate field. This would allow us to enter hours into a Jira number field whic...

To help me quickly troubleshoot background job logs: Tag each Update all linked records job type with the integration name. You are already doing this with Integration Import job types. In the case where a background job has failed, you write in t...

What is the challenge? Authentication issues are not called out when they occur during the reload configuration process. What is the impact? The user thinks they have successfully reloaded the configuration from Jira but the authentication may fai...