Allow TFS integration to populate 'Replication steps' for bugs created in Aha
To be able to easily create bugs from within Aha and use the TFS integration to pull across all relevant info from the description field into reproduction steps. After a long investigation by Aha they found that this link was not created as part o...
Integrations 2.0: Support JIRA Priority field mapping
In 1.0 I could map a custom field to the priority field in JIRA.
In 2.0 it appears as an option but the Aha! fields it can map to are only the name/description. It doesn't allow mapping my custom field to the JIRA field.
Danny Archer
over 6 years ago
in Integrations
0
Shipped
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 concern...
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...
Using Link to JIRA feature to 'import' Epics with Stories into Aha!
In our rollout we are looking at EPIC to Feature mapping from JIRA to Aha.
When we link a feature in Aha! to an EPIC in JIRA the stories do not come across as requirements - we would expect them to do this!
Improve warning for integrations "Update Records" action
For a development tool integration (i.e. Jira), there's an "Update Records" button. When clicked, you get this attached warning. This doesn't warn you that Aha! will send data for any one-way mapped fields (Aha! --> Jira) as well. It would be h...