Earlier this year, we launched the all-project dashboard that we call Project Explorer. This view compiles all the work currently being done by your team, giving managers the ability to track the health of projects and risks to your sprint goals. Users can see who is working on which issues, which tickets were added on top of sprint goals, and get metrics about project health, like bug activity.
Since the launch of the Project Explorer, we’ve invited feedback and used these insights to innovate. The latest updates give deeper visibility into project activity, sprint progress, and deployment risks.
Project Explorer now features callouts (look for the ⚠️ ) on higher priority items that might need your attention. Get ahead of potential roadblocks before they derail your sprint.
- ⚠️ Filter by sprint: Set the date range based on sprint timelines, not calendar dates.
- ⚠️ Scope creep: Identify issues that were added mid-sprint.
- ⚠️ Stalled tickets: See issues that have been open during multiple sprints, potentially due to stuck tickets or unclear needs.
- ⚠️ Stuck PRs: Quickly find pull requests that need reminders or further assistance.
- ⚠️ Identify non-sprint work: View team activity that lives beyond sprint goals, potentially challenging bandwidth.
Each of these features enables engineering managers and individual contributors to better understand current and past sprints. At a glance, teams can see what’s happening, who’s working, and why certain issues are lagging.
From here, we continue to evolve. The future of Project Explorer is a firmer focus on sprint risk—and adding new tools that help remove roadblocks to overall sprint health.