My ideas: Jira
Sort by:
Recent
Status:
Shipped
Showing 79
1
VOTE
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...
0
Shipped
9
VOTE
Warn when settings changes impact integration
When adjusting settings that are referenced in an integration, there is no warning that integrations will be impacted and users are not guided to update their integration settings. There are two main settings that result in notable issues in the i...
0
Shipped
17
VOTE
Add a "Do I need a webhook" test on Jira integration screen
When a user creates a Jira integration, the final screen automatically provides a webhook URL. There is an instruction in the help text above that indicates that you may not need to create the webhook, but many users are not aware as to whether a ...
0
Shipped
21
VOTE
Guide users to reload configuration when missing field in mappings
When new fields are added in the development system, they are not automatically shown in the Aha! integration mappings screen. Users do not intuitively know to click the "Reload configuration" button, and also do not know to check the Jira create/...
0
Shipped
1
VOTE
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...
0
Shipped
1
VOTE
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...
0
Shipped
4
VOTE
Automated Integration Migration for Aha! - Jira Server to Jira Cloud
Now that Atlassian has announced that Jira Server will not be supported by 2024, we need to find a way to migrate the existing Aha! - Jira Server integration without having to re-establish the connection. The recommended methods indicated in the l...
0
Shipped
20
VOTE
Synchronize logged time and remaining estimates from Jira back to advanced estimates
Using the Enterprise+ Capacity Planning for Teams feature, you can define an advanced estimate on a feature record and send it to the Jira. The total value of the advanced estimate is correctly reflected in Jira. However when the estimate is updat...
0
Shipped
16
VOTE
Ability to "lock" a custom field, so no user can edit it
Some of our fields in Aha are solely dictated by the field in Jira, for example Status.
Statuses in Jira have validations, which cannot be recreated in Aha. If we map Status bi-directionally, we run into errors because Aha is trying to overwrit...
3
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 ...
1
Shipped