Skip to Main Content
ADD A NEW IDEA

My ideas: Jira

Showing 171

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 almost 2 years ago in Jira 0 Future consideration

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 almost 2 years ago in Jira 0 Future consideration

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 about 2 years ago in Jira 0 Future consideration

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 about 3 years ago in Jira 0 Future consideration

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 over 3 years ago in Jira 1 Future consideration

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 over 3 years ago in Jira 0 Future consideration

Ability to enforce mandatory fields on Starter Roadmap, User Story Map, Strategy Roadmap, and Gannt

We have mandatory fields when creating initiatives, master features and features. These can be avoided when creating records via the Starter Roadmap, User Story Map, Strategy roadmap and Gantt views (there are probably some others I'm missing here...
Guest over 4 years ago in Jira 0 Future consideration

Better display of user info from Jira integration

When comments are added to Aha from the Jira integration, they show up as having been created by Integration: Jira even though the comment includes the following: Created in Jira by Matthew Monahan (****@****.com) When I dig into the values in...
Matthew Monahan over 4 years ago in Jira 0 Future consideration

JIRA integration Import of only linked epics

When stories in JIRA are moved between epics they are not automatically updated in aha. Also, for stories created prior to mapping a JIRA epic the stories are not automatically imported to aha. The import can be used to pull these in but the Impor...
Guest over 4 years ago in Jira 0 Future consideration

Integration with JIRA needs better Error handling support

Aha! integration with JIRA does not notify users on errors that would have happened during the integration (i.e. push/pull). This keeps the users in dark on what would have gone wrong and requires manual intervention to detect errors.
Guest over 4 years ago in Jira 1 Future consideration