My ideas

I have certain fields that need to be filled in before moving to the next status in my workflow. The data for these fields is not known in the previous statuses, so it can't be set as a required field before the record reaches a certain status. Th...

We have "Same as" functionality for certain field types now available for automations. It would be helpful to see the same ability extended for number fields, so related/promoted records can be populated with these when they are created or updated.

What is the challenge? Checking on the health of an integration isn't a straightforward process and isn't readily available. You need to be incredibly technical or using it everyday to know if something is wrong with your integration. It would ...

What is the challenge? If you have a record assigned to one sprint and it later gets pushed to a later sprint, the date range (when set to calculate from sprints) does not reflect the full time spent in multiple sprints What is the impact? ...

What is the challenge? Teams love the experience of prioritizing in Aha! software. Teams like it so much, users who are responsible for organizing sprint-level priorities (often product owners) want to use Aha! to help prioritize requirements go...

What is the challenge? Customers build complex scenarios to add their capacity estimates. It could be time, points, named ranges, or headcount across many teams and timeframes (monthly, quarterly, yearly, etc). This complexity is needed for the ...

What is the challenge? My team runs an annual planning process of initiatives from Aha! Roadmaps. We use team capacity planning to estimate the expected headcount required for each team per quarter for our upcoming FY. We like to run 2 rounds ...

What is the challenge? The "Convert to release" option currently requires opening the parking lot drawer to then click "...". It is not on the parking lot column "..." menu options. What is the impact? It is a common use cases to convert t...

What is the challenge? Teams are usually assigned requirements from roadmaps, not features. This means they get no advantage from using the timeline board as the board requires a feature to be assigned to the team to then nest the requirements ...

What is the challenge? We currently only align key results to epics but cannot see them as options to add to our epic card layout. What is the impact? Teams are required to click into the cards to view what the details are instead of seein...