ADD A NEW IDEA

Jira

Showing 84

Allow Aha! and JIRA integration with SSO users

We currently use Google SSO for our JIRA system. The Aha! integration however requires a username/password user account & not an SSO user. I need to be able to use an SSO user for the integration, since that is the only option that our JIRA ...
Guest almost 7 years ago in Jira 8 Shipped
172 VOTE

Please add support for Master Features within the Aha <=> JIRA interface.

Given "Aha! is for the "why" and "what" and JIRA is for the "how."; Master Features are useless unless we can implement them alongside JIRA.
Guest about 7 years ago in Jira 28 Shipped

Enable user mapping to Jira based on Aha user name and not Email (prevent privacy breach)

To map a user from Aha! to Jira the user's email is used by Aha!. This only works if Jira is configured such that the Jira option "User email visibility" is set to "Public" or "Logged in users only". For details see: (https://confluence.atlassian...
Guest about 7 years ago in Jira 0 Shipped

Release Roadmap Start On & Due On not working well with JIRA

We're using custom fields "Start Date" and "Planned Done Date" on our JIRA epics extensively, and we sync JIRA epics with Aha features. And we've added "Start Date" and "Planned Done Date" as custom fields in Aha features. When we use the Releases...
Brian Carr over 7 years ago in Jira 1 Shipped

Two Way Jira Sync for Initiative/ Epic custom fields

As far as I am aware you can only map feature custom fields, and I'd like to be able to maintain due dates, team and other custom fields at the Initiative level.
Guest over 7 years ago in Jira 1 Shipped
166 VOTE

Support aggregating Features into Sprints - and pushing into JIRA as a SPRINT

We need to be able to manage our Features, grouping them into SPRINTS and then pushing the sprint and features into JIRA as a complete set, ie. creating the SPRINT and associated JIRA Tickets. Because the support for SPRINTS doesn't exist in Aha, ...
Cynthia Countouris over 7 years ago in Jira 17 Shipped

Sync releases with epics in the JIRA integration

Like many other users, we map features to tasks and requirements as sub-tasks in our integration. For us it logically makes sense that JIRA Epics are therefore bound to releases (as tasks sit under Epics, and features sit under releases) - we use ...
Guest over 7 years ago in Jira 3 Shipped

Re-enable conversion of Features to Requirements when JIRA integration is active

In some cases, people add stories in JIRA for a release linked to Aha that are not part of an Epic. This can result in the JIRA story appearing in Aha as a Feature (at the same level as JIRA Epics), due to how the integration is set up. Previously...
Mike Ward almost 8 years ago in Jira 4 Shipped

Mapping of Initiatives to other ticket types in Jira

Currently Aha! allows only mapping of initiatives to Jira Epics. Now that Jira enables unlimited hierarchy, custom defined by portfolio managers, it would be nice to be able to load ticket types from Jira and map Aha! initiatives to ticket types o...
Ray Yee almost 8 years ago in Jira 1 Shipped

allow clicking on JIRA ticket-id in feature_grids view

right now if i add the column "jira key" (or even jira-link), and i want to see the ticket in jira, i have to copy it from the UI, and go to JIRA to paste it (or my browser's URL) to see the ticket in JIRA.this can be solved by making the col to b...
Guest almost 8 years ago in Jira 0 Shipped