Jira
Sort by:
Trending
Status:
Shipped
Showing 104
2
VOTE
Aha Needs to Utilize JIRA API Token Based Authentication, Not Basic HTTP, for the JIRA Integration
There are security vulnerabilities associated with Basic HTTP.
JIRA offers a Token based authentication with their API. This needs to be utilized for a more secure integration.
Setting this idea as "need it yesterday" because of security concerns ...
2
Shipped
2
VOTE
Release Roadmap Start On & Due On not working well with JIRA
We're using custom fields "Start Date" and "Planned Done Date" on our JIRA epics extensively, and we sync JIRA epics with Aha features. And we've added "Start Date" and "Planned Done Date" as custom fields in Aha features.
When we use the Releases...
1
Shipped
1
VOTE
Force Status field to be in sync with Jira
The recommendation of keeping Status as a one way sync from Jira makes Aha! reports silently unreliable, as Aha! and Jira status will diverge if somebody touches a record "by mistake".
If I set it to two-way sync, transitions not allowed by Jira m...
1
Shipped
1
VOTE
Support certificate-based authentication
My company, as well as many others, does not want to open ports in the firewall to connect to Jira. We use EAA as our protection in front of our on-prem Jira. Aha! supports OAuth to Jira, which is ok but we still need cert-auth in front of that to...
0
Shipped
1
VOTE
Auto-field mapping for Jira Integration
I have created a custom field in Aha which maps directly a field in Jira. I have created a pre-defined choice list in Aha! which contains all possible values in Aha!. When creating the integration between Jira and Aha! I have to manually match eac...
0
Shipped
1
VOTE
Webhook error handling with Jira integrations
I spend countless hours trying to debug webhook issues only to find the error should have been easily caught and reported back correctly. It seems the only issue that comes back is "Processing webhook: unhandled error. Please contact support@aha.i...
0
Shipped
1
VOTE
Create AHA reference automatically after import rather than having to 'resend' all data fields back to the place I have imported from.
After I have imported a record from Jira I then have to ‘resend all the fields’ from AHA in order for the AHA reference to be populated. Is there anyway that on import an AHA reference is created at that point?
0
Shipped
1
VOTE
When syncing Epics to Jira- please add the ability to Sync the tags
Syncing Aha! with Jira using the following mapping:
Initiatives> Epics
Features>Story
Requirements>Sub-task
There is no way right now to sync the tags associated with the Initiative to Jira as Initiatives do not allow custom field mapping...
0
Shipped
1
VOTE
Allow me to not sync requirements when syncing features with Jira.
We use Jira sync to keep bugs (jira bugs) and dev work (aha features) in sync and up to date. However, when the dev work gets defined (aha requirements), these requirements show up in jira (sub-tasks). I would rather not have them push into and cl...
0
Shipped
1
VOTE
© 2024 Aha! Labs Inc.•All rights reserved