It's helpful to be able to measure the complexity / effort of work compared to the value we expect it to bring to our users. While setting this for initiatives is useful, we also need to be able to do that for Epics and Features.

We use the idea board to gain insight into our customer needs. The sizes of our customer vary widely and when the larger companies submit an idea, they send an internal blast to their users to vote on the idea. This skews the data and makes it dif...

Our ideas portal is the go-to for crowd sourcing customer ideas, and will soon be the place we host our release notes (cool feature btw!) We still maintain a help centre from another provider, which currently contains our support knowledgebase, us...

Customers using API integration scripts will benefit a lot from this functionality. My script is based on individual Feature retrieval via API, but to get a linked Idea and its votes number I have to perform a number of sub-requests, which makes m...

I really like the new UI, but there are a few things I do regularly that seem to take more time now. The one that is the most annoying is having to select 'Saved Views', then wait for the modal to load and then choose the view I want to work /with...

The customer success team suggested I just use initiatives for user journeys and master features for user journey steps, which is a good temporary fix. However, defining a user journey is a pretty specific thing that I think should be set apart fr...

For me, it's difficult to use week numbers when trying to enter the number of hours I need to assign for a resource. My project plans use actual dates, not weeks, so I would rather use the week starting date. The way the capacity plan page current...

In program reviews, it is incredibly helpful to be able to surface up changes on initiatives from previous meeting. Being able to have a change date like what features have would enable to provide a report or view of initiatives that have dropped ...

Aha! provides a great functionality to change terminology in the idea portal, but it is not reflected back into Aha! idea functionality. Example. You can change 'Votes' to 'Likes'. The portal reflects the changes. The Aha! UI for ideas still say...

When creating a starter roadmap I like to drag and drop new features into release. If two features have the same start date they should auto vertically stack otherwise a user won’t see the feature below the other one.