ADD A NEW IDEA

FILTER BY CATEGORY

Jira

Showing 256

Ability to see more than the last 200 logs in Aha-Jira Integrations

Sometimes we need to investigate synchronisation errors between Aha! and Jira. We can find these errors long after an initial error might have happened. We might need to go back to the original error which may have happened months ago. The limitat...
Guest over 1 year 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, ...
Joe Watson over 1 year ago in Jira 1 Future consideration

Please Add a Setting to Turn Off the Automatic Imports of Unlinked Jira User Stories

I believe that the way integration is currently implemented is based on a faulty assumption, e.g. that customers want all user stories created in an integrated Jira project and board to be sync'd to Aha!. We'd much prefer that this not be the ...
Doug Wilson over 1 year ago in Jira 1 Future consideration

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...
Daniel Hirschberg over 1 year ago in Jira 0 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 1 year ago in Jira 0 Future consideration

Deleting a JIRA issue (story, epic) that is linked in AHA, should be deleted in AHA

When you have items linked from JIRA to AHA (example STORY->FEATURE, EPIC->MASTER FEATURE), the items deleted in JIRA should be deleted in AHA
Carlos Palminha over 1 year ago in Jira 6 Will not implement

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 overwrite ...
Guest over 1 year ago in Jira 2 Shipped

Ability to select only one user from the "User Field" custom field

Currently the "User Field" (custom field) in Aha! allows you to select one or more Aha! users. It would be useful to have a "User Field" whereby a user can only select one user. This is important for us, as one of our User Fields sycnhronises...
Guest over 1 year ago in Account settings / 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 1 year ago in Jira 0 Future consideration

Change Button Click to Dropdown for Integration Screen

When completing the Integration, a user is asked to click through the various buttons showing the direction of the integration. A user has to make several button clicks to change the option, which is not always convenient. A drop down menu would b...
Josh Tambor over 1 year ago in Jira 0 Future consideration