Integrations 2.0: Support importing unmapped issue types
In 1.0 you could map Features to Stories but also set the JIRA integration to support importing unmapped types.
This meant that bugs, tasks, etc created in JIRA could be imported as Features in Aha!
This is important, without this we have no way t...
Support for "Select list (cascading)" field type in JIRA
JIRA has a custom field type that supports cascading. This is a very useful field type that is currently not supported in Aha. Due to this, we cannot make the field required in JIRA and thus compliance drops off. The JIRA API supports this field s...
JIRA Portfolio allows for the notion of Initiatives. Portfolio is good for provide views for about 3 months (short-term), beyond that we have found it to struggle. It will be good to sync initiatives so it is possible for engineering to see what i...
Project Parker
over 6 years ago
in Jira
11
Shipped
Provide ability to map Created by user to Reporter field in the JIRA integration
When sending or linking a Aha feature to a Jira Epic the system uses the name of the person who created the Jira integration record instead of the user who created the epic. This results that all Jira issues now show up as Reported By with the nam...
Currently, we need two Jira integrations - one for Bugs, and one for everything else. But when importing/linking Bugs, they get linked to a regular ol' Feature of "New" type.
As someone in this situation, i want imported/linked Jira Bugs to set t...
Aha Needs to Utilize JIRA API Token Based Authentication, Not Basic HTTP, for the JIRA Integration
There are security vulnerabilities associated with Basic HTTP.
JIRA offers a Token based authentication with their API. This needs to be utilized for a more secure integration.
Setting this idea as "need it yesterday" because of security concerns ...
Tom McCormick
almost 7 years ago
in Jira
2
Shipped
When syncing Epics to Jira- please add the ability to Sync the tags
Syncing Aha! with Jira using the following mapping:
Initiatives> Epics
Features>Story
Requirements>Sub-task
There is no way right now to sync the tags associated with the Initiative to Jira as Initiatives do not allow custom field mapping...
Allow me to not sync requirements when syncing features with Jira.
We use Jira sync to keep bugs (jira bugs) and dev work (aha features) in sync and up to date. However, when the dev work gets defined (aha requirements), these requirements show up in jira (sub-tasks). I would rather not have them push into and cl...
When I got ready to add a new product and link it to a new project in Jira I went into my original Jira integration in Aha to see the features. When I accidentally clicked the option to "Use template JIRA" it completely erased all my selections in...
Features created due to integration to appear on Releases - Overview, Details view
This would be very helpful since without it Product Manager doesn't get to know if Dev team has added any new stories during grooming. Currently such stories although result in creating features, they are only visible on Feature Board view under r...