Skip to Main Content

Share your product feedback

ADD A NEW IDEA

My ideas: Jira

Showing 268

Filter noise from Jira integration logs

The log file currently reports on Jira tickets that are out of scope for the integration (e.g., bugs, stories, tasks) as defined by the integration template. These log entries typically end with "No changes made in Aha!" If I'm trying to find the ...
Sandy Kobayashi over 2 years ago in Jira 0 Future consideration

Ability to create JIRA integration thorough Aha API

We have teams with several projects and creating it through templates is not practically scalable, hence require an API to create JIRA integration manually
Guest about 8 years ago in Jira 3 Future consideration

Have users in Jira and Aha matched for comments, updates etc

I realise this is not Aha's fault, but if we put the issue here with more info, users will be more likely to go to Jira to vote for the issue there. Currently whenever someone comments on an issue in Jira, in appears in Aha as a comment from the p...
Guest over 10 years ago in Comments / Notifications / Jira 1 Unlikely to implement

Automatically push Epics/Features in Aha! to JIRA

What is the challenge? As a product manager using Aha!, I want to be able to create an Epic or Feature and have it automatically push to JIRA (even it's a shell that is not definition complete), so that it is represented on the JIRA board where I ...
CJ Jacobs 12 months ago in Jira 0 Future consideration

Automatically send feature(s) to integrated system

As a product manager I want to have a feature I just created be automatically created in my integrated system, such as Jira. Adding a check box in the integration configuration for "Automatically send issue to integrated system" would be an easy w...
Guest almost 7 years ago in Jira 5 Unlikely to implement

Support mapping Asset object fields through Jira integration

Who would benefit? Customers using the Asset object through Jira Service Management. What impact would it make? When these Asset fields are added to Jira issue screens, this would allow users to map these fields to Aha! fields through the Jira int...
Stephanie Lechner over 1 year ago in Jira 0 Future consideration

Auto Resend all Fields per release

Right now, even after we manually click "Send to JIRA" for the first time for a release, subsequent changes to that release ( for eg. Addition of a feature under that release) do not automatically go through to JIRA. We'd want to have all changes ...
Guest over 6 years ago in Jira 2 Future consideration

Support mapping tags to JIRA multicheckboxes

Problem Overview It is possible to bi-directionally map tags in Aha! with custom multicheckboxes in Jira. However, it is not possible to configure how the values should map on each side. This creates errors when the two fields attempt to sync. Pro...
Austin Merritt over 6 years ago in Jira 0 Future consideration

Allow the JIRA integration to support mapping to more than one JIRA issue type and in Aha provide the ability to select the JIRA issue type to sync with

We use Aha for both Feature Requests and Defects and need to be able to designate if the JIRA issue type is an Epic, Story or Bug when linking to JIRA.
Kevin Konishi about 9 years ago in Jira 11 Already exists

Including Dependencies in Jira integration at requirements/story level

We have been really enjoying the newer ability to include dependencies for features in our Aha-Jira integration, but are running into the issue not getting the same level of transparency for the user stories - to combat this, we would like the abi...
Trey S over 3 years ago in Jira 0 Future consideration