Currently the Capacity report provide a view per Month. If we need to have a smaller view in order to see the workload it would be useful to have the possibility to see it per week.

As we estimate Features in days, and these that roll up to Epics, I want to view charts and graphs in days rather than have the system multiply them by 8 automatically to show them in hours.

I need the ability to look at tag fields like arrays for calculated columns so I can filter tags as a combination of values Example: Create a calculated field count([self.features tag == “TEAM1”]) + count([self.features tag == “TEAM2”]) + count([s...

Please add 'share as a webpage' and iFrame link capabilities to strategic models and positioning. Our internal users do not always want to share this information in a presentation or a different report format. They may want to show/share their ent...

We are a large enterprise organization that makes extensive use of Aha across several hundred products. We would like to empower our users to share reports, dashboards, and roadmaps with external parties, however, we need a way to vet those links ...

When we go through our PI planning, the feature board is a very powerful tool to move items across and keep a constant watch on the capacity. Every release of ours has sprints and phases but since we do not have the phases or sprints available, we...

What is the challenge? Need all fields updated from a Jira item, but the only current options are update all from Jira or "Resend all fields". What is the impact? Users have to manually go into each field in Jira they want to update, chang...

What is the challenge? Attio is a newer approach to CRM focusing on ease of use and adoption. What is the impact? We have to manually sync customers from CRM Describe your idea Support customer sync from attio for Ideas

What is the challenge? cant fill necessary field out. What is the impact? hinders me at work. multiple reloads are necessary Describe your idea show all field

We're operating in a CI/CD environment, and prefer to release "releases" (especially API's) as soon as they clear integration and performance testing. Forcing all of the sub-releases in a Master Release to inherit that release date is not meeting ...