What is development in Jira Cloud?
This feature is currently in beta.
This means that the feature may not be available to everyone, the functionality may be limited, and it will change as we continue to develop it.
The development feature in Jira is a single place that gives engineering managers and team leads a unified view of their team’s software development and security data directly in their software project in Jira. It provides key metrics, proactive work suggestions, and your team’s related work in a single, actionable view, helping software teams and engineering leaders move from insight to impact across the entire software development lifecycle (SDLC).
Explore the Development page
Get to know how different sections on the Development page help you move from insight to action.
Key metrics
Key metrics provide a snapshot of your team’s software delivery health. These metrics help you quickly see how your team is tracking, what’s progressing, and where work might be stuck. For example, if you notice a spike in open bugs or slow pull request reviews, you’ll know where to investigate further. By surfacing trends and potential risks early, you can make informed decisions and keep your team’s momentum high.
Work suggestions
Work suggestions are context-aware, actionable recommendations designed to highlight work that requires your attention. These suggestions are tailored to the project and specifically identify actions you, as a team lead or manager, can take to help advance your team’s progress. Examples include reviewing issues due soon or addressing stuck pull requests—prioritized to help you and your team focus on the work that will have the biggest impact. By proactively surfacing stalled work and delivery blockers, work suggestions reduce context-switching and help your team deliver faster.
Related work
The related work section contains details of work from apps connected to Jira, for example, pull requests and security vulnerabilities. This is where you can drill down into the specifics, see who’s working on what, and jump straight to the code details if you need to. It helps ensure you always have the context to support your team and drive delivery. You stay close to the actual work, making it easy to investigate issues, monitor risks, and track progress to help your team ship secure, reliable code faster.
Was this helpful?