Jira
Sort by:
Popular
Status:
Future consideration
Showing 165
13
VOTE
Auto Resend all Fields per release
Right now, even after we manually click "Send to JIRA" for the first time for a release, subsequent changes to that release ( for eg. Addition of a feature under that release) do not automatically go through to JIRA. We'd want to have all changes ...
2
Future consideration
13
VOTE
Map one Aha release to several Jira projects
We have several Jira projects aiming towards the same release. When importing fixVersions from several Jira project to one product in Aha we get one release for each project/integration in Aha. This means that if we have 10 projects aiming for the...
0
Future consideration
11
VOTE
Provide alternative way to match users when email address is not exposed in Jira
Some time ago, Atlassian made changes that requires users to share their email addresses on an individual user profile setting. When that option is not checked, Aha! is not able to view their email address and if assigned user is mapped, is not ab...
1
Future consideration
11
VOTE
Show custom field names on integration errors
When there's an integration sync error with Jira on a custom field, Aha shows something like this: 'customfield_19011': Please fill out required fields The identifier 19011 has no meaning to us, as Aha doesn't expose a mapping of our custom field ...
1
Future consideration
11
VOTE
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
1
Future consideration
11
VOTE
Set feature initial status on "Send to jira"
It would be nice to have a status set on the first send to jira.
I have for example configured in jira integration page:
Status "New" in Jira -> Status "In design" in Aha.
So when I click the "Send to jira" button in the feature is should...
4
Future consideration
11
VOTE
Sync story points to Jira without Capacity Planning
My teams doesn't use capacity planning, as we have the same team members each week, but we'd like to be able to automatically link story points to Jira.
Currently this is only accomplishable when you have enabled capacity planning, which causes m...
1
Future consideration
9
VOTE
Support updating JIRA Integration Links by csv upload
While I recognise that moving JIRA issues between projects breaks the AHA integration links, the workarounds proposed here are not helpful. Option 1 ("Relink each record manually") is the only viable workaround, with options 2 and 3 being too haza...
0
Future consideration
9
VOTE
Allow requirements to be associated with the release record
The Problem: Jira requires each User Story type to have a Fix Version associated with it, similar to the Epic. The Epic will have Stories with various Fix Version ( the User Stories don’t inherit the Epic Fix Version as story releases are weekly o...
0
Future consideration
9
VOTE
The Jira integration should allow the sending of a release to Jira and properly map the feature types to Jira issue types.
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...
1
Future consideration