Jira

Showing 270

Deleting a feature or requirement should delete the linked Jira issue(s)

When I delete a feature or a requirement in Aha!, I then have to go to Jira and delete the corresponding epic or story. Would love it if deleting a feature in Aha! deleted the linked epic in Jira and all stories for that epic. Likewise, deleting a...

Guest almost 11 years ago in Jira 11 Will not 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 almost 9 years ago in Jira 3 Unlikely to implement

2 VOTE

Ability to import child records when connecting to an existing record in Jira

What is the challenge? We often have the use case where we need to connect an Aha! epic to an existing Jira record, and that Jira record will also likely have child tasks/stories. The existing connection logic will only sync with the epic record, ...

Nerissa Muijs over 1 year 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 over 5 years ago in Jira 1 Future consideration

11 VOTE

Expose "Estimate" at story creation in AHA! and push to JIRA "story points" field

Expose "Estimate" at story creation in AHA! and push to JIRA "story points" field - prevents having to go to JIRA and add points individual after time spent planning in AHA! - efficiency for PMs and Engineering

Guest almost 8 years ago in Jira 1 Already exists

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 6 years ago in Jira 1 Future consideration

8 VOTE

Integration history

Would like to track when a feature was sent to JIRA and by who? Can you please let me know how I can accomplish this? JIRA_KEY (I am able to pull) JIRA_KEY_CREATE_DATE (Not known) JIRA_KEY_CREATED_BY Thank you //Need this for SOC compliance//

Sasi Ravichandar almost 6 years ago in Jira 0 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 over 6 years ago in Jira 2 Future consideration

8 VOTE

"Make everything OK" button on feature that triggers insert/update/delete/move JIRA->AHA

Hello, it would be very helpful if in scenario, where aha records are linked to dev tool records (e.g. JIRA), there would be a possibility to trigger full record update for a single record. Example: integrations config: Features linked to Epics in...

Daniel Pokrývka about 6 years ago in Jira 10 Future consideration

14 VOTE

When sending a Feature to JIRA, automatically move the new JIRA epic/story into the JIRA project's Backlog

When we sync Aha! Features into JIRA, we're ready to begin planning sprints that will include the resulting JIRA epics/stories. Extend the JIRA integration so when new epics/stories are created from Aha!, automatically move them into the JIRA proj...

Guest almost 11 years ago in Jira 1 Already exists

Share your product feedback

Please enter your email address

FILTER BY CATEGORY