Delivery

Showing 177 of 9568

Aha! Develop - support paid seat groups

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.

Dale Potter over 2 years ago in Account settings / Delivery 0 Likely to implement

1 VOTE

Sprint Planning: Ability to see multiple sprints at once

What is the challenge? As a product manager / scrum master role, I often do loose sprint planning projecting 3-5 sprints depending on the topics. Currently, I have to click into each sprint details to review the themes and notes, one at a time. Wh...

Guest 3 months ago in Sprints 3 Planning to implement

1 VOTE

Automation: require field based custom field option

What is the challenge? During the lifecycle of an Epic, we have fields that when a certain option is selected, another field should be required. What is the impact? Data is not complete so reporting is incorrect. We have features that that when a ...

Guest 3 months ago in Delivery 0 Future consideration

2 VOTE

Allow exit criteria for each status in a workflow board to help users understand when they should progress an item to the next status.

What is the challenge? this information is currently stored outside of the tool making it unlikely for users to follow company guidance What is the impact? teams are progressing items that are not ready. we are building exceptions reports to fulfi...

Guest 7 months ago in Workflow boards 1 Future consideration

10 VOTE

Aha! Develop - Reopen a completed sprint

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 about 3 years ago in Sprints 2 Future consideration

3 VOTE

Restrict ability to open or close sprints

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 12 months ago in Sprints 1 Future consideration

6 VOTE

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

Guest almost 2 years ago in Workflow boards 0 Future consideration

10 VOTE

Mermaid text generated diagrams

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.

Guest over 3 years ago in Delivery 0 Future consideration

9 VOTE

Consistency between Roadmaps and Develop for record workflow

For the following Record Types (Epic, Feature, Requirement) In roadmap we can set each record type with its own workflow. However in Develop you can only pick one workflow for all three record types. We would like to have a consistent process of h...

Guest over 3 years ago in Backlogs / Workflow boards 0 Future consideration

1 VOTE

Ability to auto-start or schedule a sprint

What is the challenge? I the Product Manager manually do sprint changeover each time we start a sprint. My team is distributed geographically, so by the time I start the sprint, part of my team has started their day. Because I manually do this, I ...

Guest 5 months ago in Sprints 0 Future consideration

Share your product feedback

Please enter your email address

FILTER BY CATEGORY