Atlassian Marketplace REST API — Internal Reference (Versions, Resource Groups & Pricing)

Scope: Every current Marketplace API version, its resource groups, and where app pricing lives now. Owner: Engineering (DiViM). Last verified: 6 Jul 2026.

Cross-Team Dependencies: Why Most Scaled Agile Delays Trace Back to Them

A recurring theme in scaled-Agile discussions on LinkedIn this month: teams aren’t slow because they lack effort, they’re slow because they’re waiting on each other. Research backs the anecdote — a 2026 industry report found that nearly 70% of delays in scaled Agile initiatives trace back to unmanaged cross-team dependencies. The work gets done; it just gets done late because the blocking team finished on a different schedule, in a different tool, where nobody could see it coming.

Sprint Planning Anti-Patterns: 8 Traps That Quietly Wreck Delivery

Ask an experienced Scrum Master what kills a sprint and they rarely say “hard work.” They point to sprint planning anti-patterns — the quiet, repeatable habits that make a plan look complete on the board while it is already doomed. A recent LinkedIn thread on Stefan Wolpers’ sprint planning anti-patterns drew hundreds of practitioners trading the same war stories, so we pulled the eight that come up most and paired each with a concrete fix you can apply in Jira.

Release Planning Horizon: How Far Ahead Should You Actually Forecast?

“How far ahead should we plan?” is one of the most common questions in release planning discussions on LinkedIn — and the answers range from “the next two sprints” to “the whole fiscal year.” The useful framing isn’t a single number. It’s your release planning horizon: how far into the future you commit to detail, and where you switch from a firm plan to a probabilistic forecast. Get the horizon wrong and you either over-plan work that will change or under-plan and blindside stakeholders.

Managing Release Scope Creep Without Freezing the Backlog

Every release plan is under pressure the moment it’s published. A new request here, a “small” addition there, and the date that everyone agreed to quietly becomes impossible. But the answer to release scope creep isn’t to freeze the backlog and say no to everything — it’s to make every change a deliberate, visible trade-off. This is the defensive half of release planning.

Release Planning: A Complete Guide for Agile Teams in Jira

Release planning is where agile delivery meets the question every stakeholder eventually asks: “When will it be done?” Sprints keep the team moving two weeks at a time, but a release plan connects that motion to an outcome and a date. Done well, it gives stakeholders a forecast they can trust and the team a horizon to steer by. Done badly, it’s a wishful Gantt chart that’s wrong by the second sprint. This guide covers how to plan releases that hold up — and links to deeper articles on each part.

Release Planning vs Sprint Planning: What’s the Difference?

“Aren’t they the same meeting?” No — and conflating them is why some teams sprint busily for months without a credible delivery date. Release planning vs sprint planning is a question of altitude: one forecasts the destination, the other plans the next leg. Here’s how they differ and how they fit together. Both are covered in depth in our release planning guide and sprint planning guide.

Release Date Forecasting: How to Predict a Date You Can Defend

Most release dates are set by taking remaining story points, dividing by average velocity, and announcing the result as if it were a fact. It almost never is. Release date forecasting done properly treats delivery as a probability, not a single number — and that honesty is exactly what makes stakeholders trust you. It’s a cornerstone of solid release planning.

The Release Burndown Chart: How to Read It and Why It Matters

A release burndown chart is the simplest honest answer to “are we going to make it?” It plots the work remaining in a release against time, and its real power is showing not just whether you’re burning down, but whether scope is sneaking up. It’s a key tracking tool in release planning.

What it shows

The vertical axis is work remaining — in points or item count — and the horizontal axis is time, usually measured in sprints. A line trending down toward zero by your target date means you’re on track. The slope tells you your real burn rate; project it forward and you have a rough completion date.

Roadmap vs Release Plan: Why You Need Both (and How They Differ)

When a roadmap theme gets quoted back to you as a hard deadline, you’re living the cost of blurring roadmap vs release plan. They’re related but they are not the same artifact, and treating them interchangeably sets up broken promises. Here’s the distinction — part of disciplined release planning.

A roadmap communicates intent

The Sprint Planning Meeting Agenda That Keeps Sessions on Track

A sprint planning meeting goes sideways for one reason more than any other: there’s no agenda. People arrive, someone starts dragging stories onto the board, and an hour later the team has a list but no plan. A clear sprint planning meeting agenda fixes that by giving the session a shape, a sequence, and a timebox. Here’s a format that works for most teams, and how to run each part. It’s the operational companion to our complete guide to sprint planning.

How to Write a Sprint Goal Your Team Will Actually Rally Behind

Ask a struggling team what their current sprint goal is and you’ll often get a shrug or a recitation of ticket numbers. That’s the problem. A sprint full of stories but no goal gives the team no way to make trade-offs when reality intervenes, and no way to judge whether the sprint actually succeeded. A good goal is the difference between “we closed twelve tickets” and “we shipped the thing that mattered.” This is a core part of effective sprint planning.

The Sprint Planning Checklist: 10 Things to Confirm Before You Commit

Even experienced teams miss sprints for avoidable reasons: a vague goal, an unchecked calendar, a hidden dependency. A short sprint planning checklist turns those recurring failures into a few seconds of verification. Run through this before you commit each sprint. It pairs with our sprint planning meeting agenda and the full sprint planning guide.

Story Points vs Hours: Which Should Your Team Estimate In?

Few agile debates are as durable as story points vs hours. One camp says points free teams from false precision; the other says points are mystical and stakeholders want time. Both have a point, and the practical answer is less either/or than most arguments suggest. Here’s how to think about it — part of estimating well during sprint planning.

7 Common Sprint Planning Mistakes (and How to Fix Each One)

Most missed sprints aren’t bad luck — they’re a handful of repeatable sprint planning mistakes made over and over. The good news: each one has a known fix. Here are the seven we see most, and how to correct them. Consider it a troubleshooting guide for the sprint planning process.

1. Planning without a sprint goal

Sprint Planning: The Complete Guide for Agile Teams in Jira

Sprint planning is the meeting that decides whether the next two weeks go smoothly or unravel. Done well, it produces a clear sprint goal, a commitment the team actually believes in, and a shared plan for how the work gets done. Done badly, it produces an overstuffed board, a burndown that lies, and a review full of unfinished stories. This guide walks through every part of sprint planning that matters — and links to deeper articles on each — so you can run it as a repeatable process rather than a recurring argument.

Scrum Ceremony Overhead: Cut the Sprint Admin Without Losing the Cadence

“Do we really need all these meetings?” is one of the most common Scrum challenges a team will voice out loud. Standups run long, sprints get opened and closed by hand, reports are assembled manually, and the cadence starts to feel like a tax. But the ceremonies usually aren’t the real cost. Scrum ceremony overhead is mostly the manual administration bolted onto them — and that part is eliminable.

Managing Dependencies in Scrum: Spot Blockers Before They Derail a Sprint

Ask a room of Scrum Masters why their last sprint missed and you’ll rarely hear “the work was too hard.” You’ll hear that a story was waiting on another team, a shared service, or a ticket that wasn’t finished. Among the Scrum challenges that derail delivery, hidden dependencies are the quietest and the most expensive. Managing dependencies in Scrum well comes down to one principle: make them visible before you commit, not at the review.

Scrum Estimation Challenges: Why Story Points Miss and How to Fix Them

Of all the Scrum challenges teams raise, estimation is the one that quietly poisons everything else. Get it wrong and the sprint is overcommitted, the burndown lies, and trust with stakeholders erodes. The hard truth behind most Scrum estimation challenges is that story points are a relative measure of complexity — but teams keep trying to use them as a measure of how much will fit, which is really a question of capacity.

The Biggest Scrum Challenges in 2026 — and How to Solve Them in Jira

Scroll through any agile community on LinkedIn and the same complaints surface again and again. The framework is simple to read and hard to run, and the Scrum challenges that trip teams up are rarely about the rules themselves — they’re about estimation, dependencies, meeting overhead, weak metrics, and releases that slip. This guide pulls together the challenges practitioners raise most often and maps each one to a concrete fix you can put in place inside Jira.

Planning Sprints Around Federal Holidays, PTO, and Training Days

Open a federal calendar in any given quarter and you will find it pockmarked with days your team is not actually working. Juneteenth, Independence Day, a Monday holiday that creates a “use-or-lose” travel weekend, a mandatory cybersecurity training block, two engineers detailed to an inspector-general data pull, and a contractor whose badge renewal eats half a day. None of that shows up in a story-point estimate. Yet it is precisely why sprints in government slip when, on paper, the math looked fine.

Velocity vs. Capacity: What Government Agile Teams Get Wrong

Picture a quarterly program review at a state agency. The scrum master proudly reports that the team’s velocity has climbed from 28 to 34 story points over the last three sprints. Leadership nods. Then the next sprint lands in the middle of the July 4th week, two engineers are pulled onto a security-audit response, and the team delivers 19 points. Suddenly the “trend” looks like a collapse, and a program manager has to explain to a steering committee why delivery “dropped 44%.”

How to Calculate Team Capacity When Half Your Team Is Part-Time or Detailed Elsewhere

Ask a private-sector scrum master how big their team is and you get a number: “Eight engineers.” Ask a government program manager the same question and the honest answer is a paragraph. Two analysts are detailed to a surge effort across the agency through the end of the quarter. One developer is GS-staff at 30 hours a week on a flexible schedule. A contractor splits time 60/40 across two task orders on different contracts. Someone is in mandatory security training Thursday and Friday. “Eight” is a roster count, not a capacity number — and planning a sprint against the roster count is how government teams quietly overcommit, miss fiscal-year milestones, and end up explaining a slipped deliverable to a contracting officer.

Aligning Sprint Planning with Capacity Planning: A Practical Guide for Public-Sector Teams

Two weeks into a sprint, a state agency’s modernization team realized the sprint was already lost. The board looked full and ambitious at planning. What nobody checked was that two of their five developers were detailed to a separate audit response, one was carrying mandatory annual security training, and the contractor’s option year hadn’t been renewed yet. The work was committed against people who weren’t actually available. By the retrospective, the team had carried over more than half the sprint — and the program manager had to explain the slip to a steering committee that only remembered the original commitment.

Jira Now Auto-Manages Sprints Natively — Here’s What It Still Doesn’t Solve

Atlassian has rolled out auto-managed sprints in Jira Cloud. You can now pick a start and end date for a sprint, choose Start and complete automatically, and decide where open issues land when the sprint closes — the backlog, a brand-new sprint Jira creates for you, or an existing future sprint. For a single team that just wants a sprint to begin and end on schedule without someone clicking the button, this is a real, welcome improvement — and for a lot of teams it will be enough.

Sprint Automation: Smarter Logs — Sort Memory, CSV/JSON Export, and a Fuller Audit Trail

We’ve shipped an update to Sprint Automation for Jira Cloud focused entirely on the Application logs page — making it easier to review, keep, and audit what the app has done in your Jira site. No configuration is required; the new options appear automatically.

Your log sort order is now remembered

The column and direction you sort each log table by is now saved in your browser and restored automatically next time you open the page. Each table remembers its own setting — set it once and it stays the way you like it.

Three Divim Apps Are Now Both “Runs on Atlassian” AND Cloud Fortified

We’re thrilled to share a milestone that very few Atlassian Marketplace partners reach: three of our Jira Cloud apps now hold both of Atlassian’s top cloud trust signals at the same time — Runs on Atlassian and Cloud Fortified.

• Advanced Release Planning, Roadmaps & Management for Jira (v2.10.0)
• Cycle Time, Time in Status & Productivity Reports for Jira (v6.1.0)

Why Sprint Capacity Planning Matters More in Government Than Anywhere Else

A missed sprint in a startup costs a demo. A missed sprint in a government program can cost a fiscal-year deadline, a public commitment, or a line item in next year’s budget justification. That’s the uncomfortable truth behind agile in the public sector: the cost of overcommitting is higher, the room to recover is smaller, and the people you answer to are rarely in the room when the sprint is planned. This is exactly why capacity planning — not just sprint planning — deserves a front seat in government agile.

[Moved] Sprint Planning with Capacity Planning for Jira — Resource Hub

Retrospective Release Planning: Forecast Agile Releases From Your Team’s Real Track Record

“When will it ship?” is the question every development team dreads — and the one it answers worst. The usual ritual: add up the story points, divide by an optimistic velocity, and harden the result into a deadline before anyone leaves the room. Then a developer gets sick, a “small” API integration turns into a three-week saga, priorities shift, and the date everyone signed up for quietly slips.

How Release Planning for Jira Complements Jira Align

Jira Align is where enterprise agile organizations connect strategy to delivery. It rolls your teams’ work up into portfolio roadmaps, runs Program Increment (PI) planning, ties execution to OKRs, and makes dependencies visible across the whole organization. It is, rightly, the system of record for what you’re building and why.

Announcing Release Planning 2.9.0: The Enterprise Portfolio Update

We are thrilled to announce the rollout of Release Planning Version 2.9.0. While previous updates perfected single-team forecasting and capacity management, this release zooms out.

Version 2.9.0 elevates Release Planning from a single-release tool into a comprehensive, portfolio-level enterprise planning suite. We are bringing our signature Monte Carlo forecasting engine to the macro level, empowering Product Managers, RTEs, and Delivery Leads to orchestrate massive, multi-release portfolios with mathematical confidence.

Untangle Your Release Architecture: Mastering Dependency Mapping in Jira

Nothing derails a well-planned release faster than a hidden dependency. You’ve been there: the code is ready, the QA team is prepped, and suddenly someone realizes that Team B hasn't even started the API update that Team A needs to launch. Cue the frantic Slack messages and the late-night sprint planning sessions. (Efficiency-Obsessed Workaholics Rejoice, we’ve found a better way!)

Dependency Management for Jira Cloud

Sprint Planning

Technical Documentation

Sprint Automation

Coming soon: Enhanced Sprint & Team Management Updates

Version Flexible Capacity Planning posted on 27 Jun 2024

Latest Enhancements to Elevate Your Sprint Planning

Coming soon: Flexible Capacity Planning

Posted on 27 Jun 2024

Release Notes Highlights: Exciting enhancements are on the horizon! Sprint Planning and Capacity Planning for Jira, and Backlog refinement and Sprint planning will soon be providing options to adjust each sprint capacity with Personal days off, Team days off and Adjusted team member capacity.

Improved navigation

Posted on 23 Jun 2024

Make issueKey a link to edit the issue

Issue keys now function as direct links to the issue's edit page, simplifying navigation and improving efficiency. When viewing issues, you can click on the issue key to jump straight into editing mode, eliminating the need for additional clicks and page loads. This enhancement streamlines your workflow, allowing for quick modifications and updates to issues directly from the list view or any other interface where issue keys are displayed.