Skip to Main Content
ADD A NEW IDEA

Jira

Showing 87

Ability to associate a feature created in JIRA to a Master feature in Aha!

We have Engineers that take the Customer focused epic and break that down into multiple epics (sometimes technical), so we don't want to have them to get out of the tool they work in (JIRA) and switch to Aha!, just to enter the new features for th...
Vanita Wolf about 7 years ago in Jira 0 Shipped

Support for Jira Embedded Images

Jira tickets support embedded images using the following format. !ImageURL! for example: !https://imageurl.png|width=50%,height=auto! Jira Image Formatting Notation We make very heavy use of this feature to pull our designs into the jira tickets...
Guest about 7 years ago in Jira 3 Shipped

Aha Rank should be sent to JIRA after every update

Aha Rank field in JIRA should contain the proper order that is placed in Aha. The dev team can at least see the information in JIRA. Note: I am not asking to re-sort JIRA items based on Aha ranking field. I am asking to simple display the updated ...
Guest about 7 years ago in Jira 0 Shipped

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 about 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 over 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 over 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 almost 8 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 almost 8 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 about 8 years ago in Jira 3 Shipped