Jira

Showing 262

Sync story points to Jira without Capacity Planning

My teams doesn't use capacity planning, as we have the same team members each week, but we'd like to be able to automatically link story points to Jira. Currently this is only accomplishable when you have enabled capacity planning, which causes me...

Michael Clinton over 8 years ago in Jira 1 Future consideration

10 VOTE

Update API integrations with JIRA to add Created Date and Resolved Date

We would like to be able to map the created date as well as the resolved date to fields within aha from JIRA.

Guest over 3 years ago in API / Jira 1 Future consideration

10 VOTE

Ability to create a report of integration errors across multiple workspaces

Currently the only way to look at the integration errors across multiple workspaces is to bring up the Integration Updates dialog and use the Send outgoing changes tab. But you can't filter on error text, or expand the window to see the everything...

Jor Bratko over 3 years ago in Jira 5 Future consideration

10 VOTE

Custom scorecard components/elements are available for reports but NOT for integrations.

We actually would like to display the individual pieces that comes our WSJF scorecard for our initiatives in Aha. Right now, I can pull the individual scores into an Aha report, but I'm not able to send the same data to JIRA. We use dashboards in ...

Wen-Wen Lin about 5 years ago in Jira 3 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

10 VOTE

Allow users to refresh all Aha! features from a linked JIRA integration.

Currently, only the changes made to a JIRA issue are sent over to Aha! through the webhooks. We should have a way to force Aha! to synchronize all descriptions and fields from JIRA for an entire release.

Alex Bartlow about 9 years ago in Jira 0 Already exists

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

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

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

9 VOTE

Auto-sync of sprint field between JIRA and Aha

We implemented the sprint field mapping and have found that the sync isn't quite automatic. When we rename a sprint in JIRA - that shows up as a new sprint value along with the old one. This happens a lot and currently we run into a lot of confus...

Guest almost 6 years ago in Jira 2 Future consideration

Share your product feedback

Please enter your email address

FILTER BY CATEGORY