Skip to Main Content
ADD A NEW IDEA

Jira

Showing 248

bi-directional epic status mapping with Jira

I want to be able to map 1-way a specific status change between Aha and Jira
Guest almost 2 years ago in Jira 3 Future consideration

When importing records from JIRA, allow Aha! to overide the directionality of fields configured in the integration

I have a JIRA 2.0 Integration with Aha! Features mapped to Epics in JIRA. I set the directionality of the name and description fields to be one way from Aha! to JIRA. Other fields can be mapped as required. When I perform an import from developmen...
Justin Woods about 4 years ago in Jira 2 Future consideration

Update Jira integration when Jira custom fields were added

It looks like if you add a custom field in JIRA, Aha will not recognize it unless you delete the integration and add a new one, which means you need to relink everything. You should be able to go through the integration UI and add new field mappi...
Christian Stark about 6 years ago in Jira 1 Already exists

When sending an Epic to Jira, allow sending of all /updates to Features

Currently, when you send an Epic to Jira, all of its features are sent, but they are sent as the default Feature type instead of the types that they were actually categorized. Often the product person is working in Aha! and doesn't want to yet sen...
Karie Kelly about 2 years ago in Jira 0 Future consideration

Synchronising JIRA backlog with Aha ordering

Currently I use the feature board loads - organise all my features into releases with certain priorities and I use capacity planning and it's great. And I have a JIRA integration so anything I create in Aha is pushed out to JIRA with the correct r...
Guest about 4 years ago in Jira 1 Future consideration

Sync with Jira include ability to link back to Aha Item

When configuring sync between Aha and Jira, it should include the ability to have a URL back to the associated Aha idea inserted in Jira field. This would allow Product and Engineering a better way to trace stories back to the original Features, O...
Joe Watson over 4 years ago in Jira 2 Future consideration

Default JIRA Imports to Parking Lot, when there is no Fixed Version/Release

Regarding importing features into Aha! that are not part of a fixed version in Jira....Today, When you import these features, they will land in the left most active release. If there is not an active release, they will land in the left most parkin...
Josh Tambor over 4 years ago in Jira 0 Future consideration

The Aha <->Jira Integration Mappings should be Transparent to User

Presently, the record level mappings between Aha and Jira are opaque to the user. This makes it quite difficult for the user to debug the syncing.Without this info, it is quite challenging to get the Integration working. If the integration does no...
Guest about 2 years ago in Jira 1 Already exists

JIRA integration without admin account rights

At the moment, for the JIRA integration the JIRA account used to connect must have admin rights. This doesn't work for our security protocols because that would mean we're opening up access to secure projects that live in the same JIRA instance th...
Guest about 9 years ago in Jira 0 Already exists

Filter which JIRA issues get reflected back to Aha!

Aha! allows product managers to stay at the 40k foot level, while JIRA is used by our development team, which means it contains lots of small implementation details. If all the bugs and tasks being logged by my developers in JIRA reflect back into...
Ely Greenfield over 9 years ago in Jira 4 Already exists