ADD A NEW IDEA

Jira

Showing 261

Change Button Click to Dropdown for Integration Screen

When completing the Integration, a user is asked to click through the various buttons showing the direction of the integration. A user has to make several button clicks to change the option, which is not always convenient. A drop down menu would b...
Josh Tambor almost 5 years ago in Jira 0 Future consideration

Features assuming the same release as its parent master feature when importing from Jira

Given that I have an epic in Jira, linked to a Master Feature in Aha And the Master Feature is found in "Release X", When I create a story beneath that epic in Jira, Then the story should be imported as a child to the Master Feature, AND assume ...
Guest almost 5 years ago in Jira 0 Future consideration

Working with JIRA worklog dimension (worklog date)

Dear aha, in order to resolve reporting of time spent on features within specific timeframes, it might be useful to think about including worklog date of JIRA issues into synchronized aha backlogs. This would enable creation of reports where not o...
Daniel Pokrývka almost 5 years ago in Jira 0 Future consideration

Allow Feature or Master Feature to be pushed to Jira when the Aha! state is mapped but blocked when it is un-mapped

Our product management team wants to plan features prior to making the feature available via Jira Integration. For example while a feature is under consideration or in planning/grooming state it would only exists in Aha. Once the feature is ready ...
Guest almost 5 years ago in Jira 0 Future consideration

Have features push a status to a field in Jira when deleted

As a product manager I would like the ability to keep track of which items in JIRA/AHA have been deleted in each system. I know Aha! will not likely implement a feature to delete issues in Jira when respective items are deleted in Aha! However it ...
Guest about 5 years ago in Jira 0 Future consideration

Update the JIRA sprint field with better import

Currently if a story has belonged to more than one sprint, the sprint field concatenates the sprint. For example, a story was in sprint 2019.5 and then moved to 2019.16 and then moved to unscheduled. In JIRA the story is none +2 indicating that ...
Guest about 5 years ago in Jira 3 Already exists

After Importing Feature from Jira, show reference # id(s) for imported item(s).

Today, after importing a Jira item into our Feature list, the import completion screen just indicates the number of features imported. I'd like to be able to go directly to that imported item so that I can make some changes to it, but instead I ha...
Zayna Schaffer over 5 years ago in Jira 0 Future consideration

Integration with Jira: Ability to filter imported Jira releases/versions by date

Integration with Jira: Ability to filter imported Jira releases/versions by date Problem: A lot of manual clean up is required when integrating with Jira projects that have many past releases. There is no functionality to filter out old releases. ...
Guest over 5 years ago in Jira 0 Already exists

JIRA integration: support mapping of “Release name” into custom field

Mapping of “Release name” towards custom fields in JIRA integration instead of “fixed version” or “affected version” only currently the AHA-Jira integration only allows a mapping of "release name" values in either "fix version" or "affects versio...
Florian Kette about 6 years ago in Jira 1 Unlikely to implement

Aha should support multiple "types" in Jira (epic, bug, use case, tasks) in one single Aha query

Hortonworks uses following Types in Jira application: Epic, New feature, PRD, Tasks, Doc. Currently, we have to create multiple queries using Development tool in order to bring the above Jira tickets to Aha. Requirement: The query should bring a...
Guest about 6 years ago in Jira 0 Unlikely to implement