Jira

What is the challenge? use the right API calls from Atlassian What is the impact? Integration does not work Describe your idea The Atlassian API for getting resolutions for a project does not exist: 404 is the right response from Atlassian May use...

What is the challenge? We use checkboxes for our Acceptance Criteria (AC). Sometimes, it makes sense to add additional detailed ACs under a bigger AC. We use an indent for this, however, after Jira sync, these indents are removed. What is the impa...

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

I have a JIRA 2.0 integration setup for one of my workspaces. When I push over an Epic containing Features and Requirements, the Features are linked to the Epic but the Requirements are not linked to the Feature. So in JIRA, you can easily see how...

I believe that the way integration is currently implemented is based on a faulty assumption, e.g. that customers want all user stories created in an integrated Jira project and board to be sync'd to Aha!. We'd much prefer that this not be the ca...

Today, sending a release converts all the feature types to the default Jira issue type specified in the Jira integration mappings. This makes the release level integration useless if you manage different feature types in Aha (e.g. bug, defect, fea...

When creating Epics in Jira, they don't integrate into Aha. They will only integrate if you create child records under them that integrate into Aha. Epics need to be able to be integrated into Aha on their own.

When using AHA to integrate with other platforms such as Jira, sometimes fields are not mapped correctly due to either changes in Jira or custom fields in AHA. When this mismatch happens, we are only presented with 'unhandled error exception. Plea...

Would like to track when a feature was sent to JIRA and by who? Can you please let me know how I can accomplish this? JIRA_KEY (I am able to pull) JIRA_KEY_CREATE_DATE (Not known) JIRA_KEY_CREATED_BY Thank you //Need this for SOC compliance//

We implemented the sprint field mapping and have found that the sync isn't quite automatic. When we rename a sprint in JIRA - that shows up as a new sprint value along with the old one. This happens a lot and currently we run into a lot of confus...