PINNED
Chrome extension to capture feedback from anywhere
What is the challenge? We work in many applications and Aha! can not build custom integrations for all of them. This makes it very hard to users of those applications to capture feedback and store it all in Aha! ideas. What is the impact? This res...
Integrate Aha Program Increment (PI) custom field with Rally Release field
Today in Rally, following an orthodox SAFe Portfolio model, we organize our work based on Product Increment (PI) intervals that include four(4) two week sprints and on two week sprint for Innovation and planning. Every ten weeks we hold another PI...
Guest
almost 7 years ago
in Rally
0
Future consideration
Update blank Jira fields on import to Aha! even if they are set up as a two-way sync
Currently only fields that are mapped one-way from Aha! to Jira will update when imported to Aha! - we import records from Jira to Aha! without a version set in Jira and Aha! automatically adds them to a default release in Aha! - we would like Aha...
Diane Metzger
8 months ago
in Integrations
0
Future consideration
Ability to view the specific development integration that an object is using
There are a few instances when it would be valuable to report on the name of the integration that an object is using to connect with an external development system.
This would help to identify when integrations are being 'cut over' in order to tra...
Guest
almost 7 years ago
in Integrations
1
Already exists
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 5 years ago
in Jira
1
Future consideration
Expose "Estimate" at story creation in AHA! and push to JIRA "story points" field
Expose "Estimate" at story creation in AHA! and push to JIRA "story points" field - prevents having to go to JIRA and add points individual after time spent planning in AHA! - efficiency for PMs and Engineering
Make popouts in embedded Aha! views in Confluence larger for easier visibility
When embedding an Aha! view that allows drilldown in Confluence, the popout boxes for the drilldowns are relatively small and make it difficult to view all of the content. The same popouts in a webpage or fullscreen view have a lot more room and m...
Maria Plotkina
about 2 years ago
in Integrations
1
Future consideration
The Jira integration should allow the sending of a release to Jira and properly map the feature types to Jira issue types.
Today, sending a release converts all the feature types to the default Jira issue type specified in the Jira integration mappings. This makes the release level integration useless if you manage different feature types in Aha (e.g. bug, defect, fea...
Andrew Sweet
over 6 years ago
in Jira
1
Future consideration