ADD A NEW IDEA

Jira

Showing 257

Show comments added in JIRA as part of a state transition.

Currently, when a comment is add to a JIRA issue as part of a state transition, the comment is not shown in AHA. This is a real issue for us since the Engineering team adds useful comments in JIRA when they move an issue between states. This means...
Michael Buonassisi about 5 years ago in Jira 2 Future consideration

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...
Wen-Wen Lin about 5 years ago in Jira 0 Future consideration

Support all types of JIRA text field formatting

The current JIRA integration doesn't support renderers other than the Wiki Style Renderer very well. Please add support for the other renderer types.
Guest over 7 years ago in Jira 0 Unlikely to implement

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...
Guest over 7 years ago in Jira 3 Future consideration

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 ...
Emily Yankush about 1 year ago in Jira 0 Future consideration

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

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 (...
Guest almost 5 years ago in Jira 1 Future consideration

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...
Kevin Burges over 6 years ago in Jira 0 Future consideration

Features and Epics should move to integrated parent Release upon updates

What is the challenge? If you introduce Version<>Release mapping to an existing integration or you link a record to an existing Jira record, subsequent updates are creating a new Aha! release (linked to the Jira issues's Fixed Version) but t...
Stephanie Lechner 6 days ago in Jira 0 Planning to implement

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...
Noor Akhtar 6 months ago in Jira 0 Future consideration