Feedback issue: Duo Planner agent (Beta)
Welcome to the Duo Planner Beta! 🚀
The purpose of this feedback issue is to collect your experiences with Duo Planner (Beta), a new AI-powered Product Manager agent for GitLab. Our goal is to understand how Duo Planner (Beta) is helping (or hindering) your planning workflows, identify bugs and improvement areas, and prioritize enhancements based on real usage. Your feedback will directly influence how we evolve this agent from Beta to GA.
Limited Beta Availability
- Only available in SaaS in 18.5
- Accessible via Duo Chat side panel within projects, not groups
- During Beta, Duo Planner is in Read Only mode
What is Duo Planner?
Duo Planner is a specialized PM agent available in the Duo Chat side panel that acts like a product management teammate. It combines Agile/PM expertise with context-awareness of GitLab work items (epics, issues, tasks).
Current Beta capabilities (18.5)
Current Beta capabilities
- Analyze and prioritize your project backlog using PM frameworks
- Break down epics into features and user stories
- Identify dependencies and blocked work
- Generate executive summaries and status reports
- Understand work item relationships and hierarchies
- Apply common prioritization frameworks like RICE and MoSCoW
- Analyze backlog health
- Read-only access to your data (cannot edit/create items)
- No cross-project dependency analysis
- Not available on boards, roadmaps, or wiki
- May not understand custom workflows or fields
- Cannot create embedded views (aka GLQL)
- Cannot access milestones or iterations
Planned GA features
- Edit/create capability for work items
- Expanded context awareness (boards, roadmaps, lists)
- Relationship management (create blocking/blocked by links)
- Self-Managed and Dedicated platform support
🎯 Feedback we're especially interested in
- Accuracy: Does Duo Planner understand your planning context correctly?
- Usefulness: Which responses save you time vs. create more work?
- Frameworks: Are RICE/MoSCoW/other prioritizations helpful and correct?
- Tone: Is the PM voice appropriate for your team?
- Missing capabilities: What planning tasks can't you accomplish?
📝 How to give feedback
-
Check existing feedback: Review threads below to see if your issue is already reported. Add a
👍 or comment to show support. - Start a new thread: Use a descriptive title like "RICE calculations incorrect for GitLab scale" or "Blocked work analysis misses cross-project dependencies"
-
Include context:
- Your prompt to Duo Planner
- The response you received
- What you expected vs. what happened
- URLs or screenshots (sanitized as needed)
- Rate the response: On a scale of 1-5, how useful was it?
Example feedback format
- Title: Wrong priority order suggestion for sprint planning
- Prompt: "Help me prioritize these 10 issues for our next sprint"
- Context: [Link to issue list or description]
- What happened: Duo Planner didn't consider factors like how much work remains on an item, popularity, and other contextual factors.
- Expected: Should be able to consider all available data when making recommendations about priority.
- Usefulness: 2/5 - Had to redo the prioritization manually
- Screenshots: [If applicable]
🤝 What you can expect from us
- We will read all feedback during the Beta period
- We will prioritize fixes for GA based on feedback patterns
- We will create issues for reproducible problems with severity/priority labels
- We may reach out for clarification on complex issues
🐛 Known Beta Issues
- Duo Planner may occasionally reference capabilities it doesn't have (e.g., "I'll create an epic")
- May not recognize all custom labels or workflows
- Complete list of known Duo Planner bugs here