Jira
Sort by:
Popular
Filter by:
Status
Showing 245 of 8631
7
VOTE
Add Product Name to JIRA Integration
The Product Name contains an import department work categorization that we would already use to filter reports in Aha and would like to be able to do the same in JIRA. There is a similar request to have Product Name in the Slack integration. I won...
0
Future consideration
7
VOTE
7
VOTE
Allow auto-import of JIRA issue without the need for a "parent record" (or just a pre-defined default like with manual import)
I was a bit confused when I could import items from JIRA manually, and webhooks were working both way, but when I made a new issue in JIRA, it was not getting auto-imported. I read through lots of really long explanations about the need for "paren...
3
Future consideration
6
VOTE
Allow for parent-child linking across Jira projects without using an integration template
Some organizations that use SAFe store high-level records in one Jira project and the tactical work in team-specific Jira projects. These are often integrated to the same Aha! workspace. Today, you have to use the same integration template in the ...
0
Future consideration
6
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...
3
Future consideration
6
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 ...
1
Future consideration
6
VOTE
Integrate Master Features and related features to different JIRA projects
In this scenario, there is one Program product workspace in Aha! and one Program project in JIRA which contains Master Features per Agile Release Train. All Stories (Aha Features) and sub-tasks (Aha Requirements) are with one or many Agile Teams (...
1
Future consideration
6
VOTE
Ability to configure integrations not to create new records in Aha
In the 1.0 integrations I had configured it to not try to create new Aha! records when records were created in JIRA.
I would like to be able to do the same in the 2.0 integrations. Currently when someone creates a new issue in JIRA I see this appe...
0
Future consideration
5
VOTE
Epics that aren't selected for import in the Import list should be saved or maintained in Aha for later import.
What is the challenge? Once an epic is ignored on the import list in Aha it cannot be retrieved to be imported at a later date. What is the impact? Doubles the work of having to create the corresponding feature for the epic in Aha and then link it...
0
Future consideration
5
VOTE
