Paid seat groups are useful for managing the assignment of seats to Roadmaps users. It would be great if this could be extended to support the assignment of Develop seats as well.
What is the challenge? On some teams, only certain team members are allowed to start or close a sprint. Currently anyone with contributor access can open or close a sprint. What is the impact? Sprints are open or closed in error. Describe your ide...
Emily Yankush
9 months ago
in Sprints
1
Future consideration
What is the challenge? Getting estimates from people is a slow process, they are rarely correct and are often influenced by politics or hidden agendas. What is the impact? Plans are rarely accurate, estimates are padded to make people feel safe. O...
Epic/Feature boards using custom fields than versions
What is the challenge? Today we are not using Aha! out of box Releases and using a custom field for Release at Enterprise wide. So existing Aha! boards is forcing us to create versions at workspace but ideally we would like to use our custom field...
Shiv Shankar Vedharajan
7 months ago
in Workflow boards
0
Future consideration
What is the challenge? I want to define the template for Acceptance Criteria so that it can be used in project. What is the impact? Project usage Describe your idea Need template.
Guest
7 months ago
in Development
1
Future consideration
It is possible to re-open a shipped release to make changes that should have been included. The same logic should apply to sprints as there are various reasons I may need to make changes.
Dale Potter
almost 3 years ago
in Sprints
2
Future consideration
Allow customization of sprint dates when generated by a Program Increment (PI)
It's great that it's possible to auto-generate sprints based on the PI that they belong to. However, there are times we need to adjust the dates of sprints based on various factors, such as holidays. It's not currently possible to adjust the sprin...
Dale Potter
over 1 year ago
in Sprints
0
Future consideration
Allows much easier to iterate, more standard, and simpler to follow along version of diagrams/charts within documentation. GitHub and Notion have recently adopted the same library (mermaid) allowing for standardization across tooling.
Barnett Klane
almost 3 years ago
in Development
0
Future consideration
Enable automations to work with custom "One to Many Relationship" tables
It would be great if we can have automation rules working with "One to Many" relationship type of custom tables. We use a custom table to track risks in issues in multiple record type and would be great to add new records based on a trigger at the...
Edgar Holguin
over 1 year ago
in Workflow boards
0
Future consideration
I really like the ideas overview page, however for collaboration and triage, it would be useful for us to be able to view the ideas in the workflow (kanban) view.
Nerissa Muijs
over 2 years ago
in Workflow boards
2
Future consideration