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...
As an Aha Administrator, I have a large number of products that link to one JIRA project and having to setup the same integration over and over again for these products is time consuming and painful. Setting up a JIRA integration at a higher level...
Add ability to bulk send features to JIRA when there are multiple JIRA projects
We have 5 teams and in each release, there are dozens of features. We are going to use tags to categorize which JIRA team will work on which features. Example: "Find Team" features will be tagged with "Search", "Recommendation" or "Catalog Managem...
Engineering has made many attributes in JIRA mandatory, which means I need to create custom fields. They would be OK with a static value that would identify it as coming from Aha!, as they want to make sure they are filled correctly manually but t...
Daniel Hirschberg
almost 9 years ago
in Jira
3
Shipped
Track effort (estimates) to prepare features for JIRA separately
When Aha!-JIRA integration is enabled, updating the features estimates on one of the tools, will cause an update on the other.
We suggest to have the possibility to un-map the estimates fields between the 2 tools. So updating on one tool won't aff...
Support 'parent link' field in Integrations for other issue types.
Aha recently added support for the Jira 'Parent Link' field in Integrations, and this was delivered via this ticket. https://big.ideas.aha.io/ideas/APP-I-7115 Turns out that this integration will only support the Parent Link field for the Initiati...
Ability to customize the hyperlink in the 'Integration' field for Jira integration 2.0
Assume the following are our server urls. Jira server URL - https://stag.external.sample.com/external_path Jira internal server URL - https://jira.sample.com/jira Now, the hyper link on Aha! records should ideally show https://jira.sample.com/jira...
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 ...
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...