My ideas: Jira

Showing 260

Add better error handling for 'unhandled error exceptions'

When using AHA to integrate with other platforms such as Jira, sometimes fields are not mapped correctly due to either changes in Jira or custom fields in AHA. When this mismatch happens, we are only presented with 'unhandled error exception. Plea...

Guest over 1 year ago in Jira 0 Future consideration

3 VOTE

Notification when an integration is down

Would like to see some way of setting user(s) to be notified if there is an interruption in communication between integrated system.

Guest over 1 year ago in Jira 1 Future consideration

3 VOTE

Allow Jira Epics to Integrate

When creating Epics in Jira, they don't integrate into Aha. They will only integrate if you create child records under them that integrate into Aha. Epics need to be able to be integrated into Aha on their own.

Guest about 2 years ago in Jira 0 Future consideration

3 VOTE

Improve integration job troubleshooting steps

To help me quickly troubleshoot background job logs: Tag each Update all linked records job type with the integration name. You are already doing this with Integration Import job types. In the case where a background job has failed, you write in t...

Alfred S over 2 years ago in Jira 0 Future consideration

3 VOTE

New "integration reference" custom field type to house read-only text reference to a field on other side of Jira (or other) integration

There are fields in Jira (and I imagine other integrated applications) that don't map cleanly to an Aha custom field type. I am proposing a new custom field type that is an always-readonly text field that can be mapped to any Jira field type, and ...

Gene Lewin over 2 years ago in Jira 0 Future consideration

3 VOTE

Need easier way to link to existing Jira records!

Current workflow from what we have determined and as was suggested by Aha support: 1. A new idea/suggestion comes in from a customer, we promote a new requirement in an existing Feature. 2. It is promoted to a new requirement. 3. Within about 30 s...

Jon DeLong over 2 years ago in Jira 0 Future consideration

3 VOTE

use Jira credentials of the user to record changes in Jira

In the Aha! user profile, request the Jira credentials of the user. When making updates to Jira tickets, use these credentials so that we can see in the JIra ticket who actually mae the update. Kendis does this.

Guest almost 4 years ago in Jira 0 Future consideration

3 VOTE

Add the "[Updating]" tag to Integration Reports where applicable

When you make a change to an Integration being used as a template by other workspace/integrations, while the update is progressing through the dependent workspace/integrations sometimes you see an "[Updating]" tag next to the name in the left navb...

Jor Bratko almost 4 years ago in Jira 1 Future consideration

3 VOTE

Assign Integration to Specific User

Need the ability to assign a JIRA integration to a specific Aha! user instead of having each PM need to navigate to the integration and select Run As.

Yancey Larochelle-Williams about 4 years ago in Jira 0 Future consideration

3 VOTE

Make fixed workflow transition enforcement optional for Jira integratations

Jira is our source of truth for synced items, so if Jira somehow allowed a status change to happen we don't want Aha! to [almost] silently ignore it. With the current behavior, any discrepancy makes Jira and Aha! grow apart and we really need A...

Daniel Hirschberg almost 5 years ago in Jira 0 Future consideration

Share your product feedback

Please enter your email address

FILTER BY CATEGORY