Make fixed workflow transition enforcement optional for Jira integratations
Jira is our source of truth for synced items, so if Jira somehow allowed a status change to happen we don't want Aha! to [almost] silently ignore it.
With the current behavior, any discrepancy makes Jira and Aha! grow apart and we really need A...
Daniel Hirschberg
about 5 years ago
in Jira
0
Future consideration
Default JIRA Imports to Parking Lot, when there is no Fixed Version/Release
Regarding importing features into Aha! that are not part of a fixed version in Jira....Today, When you import these features, they will land in the left most active release. If there is not an active release, they will land in the left most parkin...
Josh Tambor
about 5 years ago
in Jira
0
Already exists
Ability to select only one user from the "User Field" custom field
Currently the "User Field" (custom field) in Aha! allows you to select one or more Aha! users.
It would be useful to have a "User Field" whereby a user can only select one user. This is important for us, as one of our User Fields sycnhronises wi...
Ability to enforce mandatory fields on Starter Roadmap, User Story Map, Strategy Roadmap, and Gannt
We have mandatory fields when creating initiatives, master features and features. These can be avoided when creating records via the Starter Roadmap, User Story Map, Strategy roadmap and Gantt views (there are probably some others I'm missing here...
Guest
about 5 years ago
in Jira
0
Future consideration
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
about 5 years ago
in Jira
0
Future consideration
When comments are added to Aha from the Jira integration, they show up as having been created by Integration: Jira even though the comment includes the following:
Created in Jira by Matthew Monahan (****@****.com)
When I dig into the values in t...
Matthew Monahan
about 5 years ago
in Jira
0
Future consideration
When configuring a new Product in Aha to integrate with Jira: The backlogs are already in priority order in Jira. However, when syncing over to Aha!, the priority order does not carry over upon the first sync. I understand how to use the rank fiel...
Guest
about 5 years ago
in Jira
1
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
about 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
about 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
about 5 years ago
in Jira
0
Future consideration