Jira

Showing 261 of 9073

Don't Allow Jira Integration to Fail Based on One Field

What is the challenge? I have a Jira integration that integrates many standard and custom fields. If there is an issue with one of those fields for whatever reason, the entire integration fails and will continue to do so even if there is nothing w...

Guest 7 months ago in Jira 0 Future consideration

9 VOTE

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 wi...

Guest almost 5 years ago in Account settings / Jira 1 Future consideration

10 VOTE

Allow for Delete of Jira Issue

Sometimes it is difficult to keep Jira and Aha Requirements up to date when/if a requirement is deleted. I'd like to see a Mapping that is allow to delete and you can select which direction that can occur.

Kenny Burnham over 5 years ago in Jira 2 Unlikely to implement

2 VOTE

Add more filters to integrations import

Who would benefit? aha admins What impact would it make? keeping Aha in sync with JIRA on the release. This would also help other internal stakeholders informed. How should it work? The integrations import desperately needs additional filtering cr...

Shri Iyer about 1 year ago in Jira 0 Already exists

15 VOTE

Support for Jira Code Markup

Need to support the Jira code markup option. If the developer enters sample code as part of the description in Jira, the description gets updated in Aha! However the code markup is translated into very large tables in Aha! At some point, Aha! upda...

Guest over 8 years ago in Jira 2 Future consideration

9 VOTE

Allow requirements to be associated with the release record

The Problem: Jira requires each User Story type to have a Fix Version associated with it, similar to the Epic. The Epic will have Stories with various Fix Version ( the User Stories don’t inherit the Epic Fix Version as story releases are weekly o...

Guest over 5 years ago in Jira 0 Future consideration

8 VOTE

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 ca...

Doug Wilson almost 5 years ago in Jira 1 Future consideration

9 VOTE

The Jira integration should allow the sending of a release to Jira and properly map the feature types to Jira issue types.

Today, sending a release converts all the feature types to the default Jira issue type specified in the Jira integration mappings. This makes the release level integration useless if you manage different feature types in Aha (e.g. bug, defect, fea...

Andrew Sweet over 5 years ago in Jira 1 Future consideration

14 VOTE

When an Idea is Promoted to a Feature, Automatically Copy Idea's Subscribers (as well as Watchers) to the Feature. And, Sync the Watchers & Subscribers to JIRA

Hi All, We are having some trouble keeping an idea's subscribers & watchers in the loop on the idea ticket from its conception through completion. The fact that people can subscribe & watch ideas is great (we find the email updates very he...

Guest almost 9 years ago in Ideas / Jira 4 Unlikely to implement

13 VOTE

Send release phases to JIRA as proposed sprints

We would like to have a means to integrate Aha! release phases with JIRA sprints, as features included in phases are sent to JIRA.

Donna Sawyer about 8 years ago in Jira 3 Unlikely to implement

Share your product feedback

Please enter your email address

FILTER BY CATEGORY