Visual Studio Team Services is encouraging people to move to PATs from Custom Credentials in the integrations. They will probably deprecate it in the not-so-distant future, and it's a reasonable move in general as they're more secure and easier to...

As a Product Manager, I want the ability to show stakeholders a more robust roadmap so that I can show project plans at the epic/initiative level. Currently, this level of detail exists at the release level however, initiatives/epics often span re...

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...

Ability to edit Dependency types within the link. Currently, user needs to delete dependency and create new one. For example, as a user, if I label a dependency "Depends on" and the dependency type should be "relates to", I should be able to chang...

We wanted to send a pdf copy of the strategic roadmap to a partner however it would be nice to put a watermark on it so we can identify it's confidential. As a stretch if we could even customize it then we could put the partner's name on it.

Sometimes a requirement needs to be done one sprint before the related feature. So we need to promote it as a feature. The relationship between the new feature and the previous one is created as RELATES TO. This is a problem, as Gantt chart shows ...

As a power user, I want the progress to print to the screen in numerals (e.g. "1 of 250 features imported") so that the information prevents me from re-attempting an import. My current workaround: navigate to the Features -> Board and check the...

We are trying to bring our Cross functional partners into Aha and would like a way to easily request work from them. We had been copying our Feature and assigning the UX-specific Feature to them. This allows for the details from the Product Develo...

We use release to reflect our Product Increments. As we are synchronizing with AzureDevops we cannot take advantage of the Release Phases. Therefore It would make sense to be able to define a Hierarchy of Releases: e.g. Release PI-5 --> Release...

We would like to share documents with our private ideas portal users to help deliver additional information (release notes, FAQ's, etc.) Currently the Notes functionality does not include the attached documents.