Some communities in my company are a little more sensitive and want more control over the ideas that are shown to the public. I think it might be helpful to have an option for ideas to be held for review by staff before being shown on a public ide...
As a central organization delivering many capabilities across many of our products, I need to be able to create a report that shows all of the dependencies for that program on my team, but I can't because there is not a way to put a "where clause"...
Allow reporting to add the goal field on the initiative and initiative roll-up records (without related record)
When creating list/pivot reports, the goal field is available on the feature record. However, the goal field is not available for reporting on the initiative record or roll-up initiative records. It would be helpful to be able to see the goal fiel...
The fancy, flippy dippy transition in the Notebook web pages is more than annoying . Can you please do one of the following?
1. Make it a simple scroll so the user does not have to jump pages. If there are multiple pages, the user has to remember ...
As a product manager, I must have the ability to accept enhancement requests from different stakeholders who have different types of information to provide, so that I can collect the right type of information needed to address the requirement.
We ...
Norah Brennan
over 7 years ago
in Ideas portal
7
Shipped
TFS (a.k.a. VSO) Automatically create new stories in TFS as requirements in Aha! when stories are created under a linked feature.
If a feature has been sent to TFS as a feature and requirements as stories, when I create a new story under the linked feature I would like it to be automatically created in Aha! as a requirement.
The integration with TFS has a lot of potential, but it's still work to have to remember to click the Action then Update TFS. If some product owners forget, then we have to audit what features and requirements are in both systems and see which one...
Allow a Feature (epic) in Aha! to have Requirements (stories) that live in a different Jira project
The use case is that we create features in Aha! and sync them to Jira as epics. The development team will then break the epics down further into stories in the appropriate Jira projects for the teams that need to work on them. In Jira, these stori...