It would be helpful if Requirements were built out so that they can be imported from jira 2.0 AND moved from feature to feature as easily and features are moved betweeen master features.
Kaylee gervasi
over 7 years ago
in Jira
0
Already exists
In 1.0, when using a template, you could choose what fields/behaviors to inherit from the template, and which to customize for that particular integration. This was useful for custom fields (now using a constant in 2.0) which will change from prod...
Max Cascone
almost 8 years ago
in Jira
6
Already exists
Allow integration of Custom Fields to any Jira Field of a supported field type
We have a process where we track issues reported by Release. Our issues come via Cases in Salesforce, which are then pushed as an Feature in Aha which captures the Affected Version in a custom field.
We would like to push this custom field valu...
Need an option to sync Jira fixVersion "Name" instead of "ID"
Aha! Feature may contain Requirements from different Jira Projects. Right now, the fixVersion is synced with "fixVersion ID", which will not be synced successfully when the Feature (Epic in Jira) and Requirement (Story in Jira) belong to different...
What is the challenge?
When assigning features in Aha that are then sync'd to Jira - the assignee field cannot be set
What is the impact?
When development teams use Jira and Product teams use Aha, the feature becomes the common currency. T...
Manesh Patel
2 months ago
in Jira
0
Already exists
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...
Calculate Epic Completion Based on JIRA Epic Completion
The options to calculate the completion of an epic in Aha is only based on user stories, but there are other items in JIRA that determine how complete an epic is. It would be helpful to have the progress bar completion automatically reflect whatev...
Rachelle S
almost 3 years ago
in Jira
0
Already exists
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...
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...