Key takeaways
- Jira has no dedicated milestone feature, so teams model milestones with releases, due dates, a custom milestone work type, an epic with a due date, or a workflow status.
- Releases (versions) are the closest thing to a native milestone: they have a release date, collect issues through Fix version, and show their progress.
- A milestone is a point in time, an epic is a body of work, and a release is a set of issues shipped together; mixing them up is the most common reason milestone tracking breaks.
- Native options work inside one project; seeing milestones across several projects and teams needs Jira Plans (Premium and Enterprise) or a Marketplace app.
- ActivityTimeline adds a Milestones panel that shows Fix Versions, sprints and due dates above your team's schedule. You can try it free for 30 days.
You know the moment: someone asks "are we still on track for the beta?" and nobody can point at the beta in Jira, because it isn't an issue, an epic or a sprint. It's a date the whole plan hangs on, and Jira doesn't have a field for it.
The good news is that you don't need one. Jira has four or five building blocks that work as milestones, and one of them, the release, is close enough to the real thing that most teams should start there. Below: what each option does, how to set it up, and when it stops being enough.
Does Jira have milestones?
No, Jira has no milestone field or milestone work type out of the box, in Cloud or Data Center. What it has are things you can use as milestones: releases (also called versions or Fix versions) with a release date, the Due date field on any issue, custom work types that an admin can add, and epics that carry their own dates.
A milestone just needs three things: a name, a date, and a way to see whether the work behind it is done. Each option below gives you all three, with different trade-offs.
How do you create milestones in Jira? 5 ways
1. Use releases as milestones
This is the option we recommend for most teams. A release has a name, a start and release date, and every issue tagged with that Fix version counts towards it, so Jira shows how many are done.
- Open your project and go to Releases in the sidebar.
- Click Create version (the button may read Create release).
- Name it after the milestone, for example "Beta", and set the start and release dates.
- Open each issue that belongs to the milestone and set Fix versions to it.
- Track it on the release page: done, in progress and to-do counts against the release date.
The limit: a release belongs to one project, so a milestone shared by three projects means three releases with the same name.
2. Create a Milestone work type
If your milestones aren't releases (a security audit, a client sign-off, a board review), a dedicated work type makes them searchable and visible.
- As a Jira admin, go to Settings → Work items → Work types and add a type called Milestone.
- Add it to your project's work type scheme.
- Create one Milestone per checkpoint and give it a due date.
- Link the issues that must be finished first with a "blocks" link.
- Save a filter like issuetype = Milestone ORDER BY duedate and add it to a dashboard.
3. Use the Due date field
Every Jira issue already has a Due date system field, so there's nothing to create. If you don't see it on the issue, an admin needs to add it to the project's screen. Set the date, then find upcoming deadlines with duedate <= 14d AND statusCategory != Done.
It's the quickest option and the weakest: a due date marks one issue, not a set of work, so it tells you nothing about progress.
4. Give an epic a due date
When a milestone is the end of a phase, the epic for that phase can carry it. Set the epic's start and due dates, and the timeline shows it as a bar with its child issues underneath and a progress bar for how many are done.
5. Add a workflow status
Some teams add a final status like Milestone reached. It records that a checkpoint happened, but it has no date and doesn't show up on any timeline, so use it alongside one of the options above, never instead of them.
What's the difference between a milestone, an epic and a release?
A milestone is a point in time, an epic is a body of work, and a release is a set of issues shipped together. "Beta is on 14 March" is a milestone. "Build the onboarding flow" is an epic. "Version 2.4" is a release, and it can also be your milestone if shipping 2.4 is the checkpoint everyone cares about.
The mix-up usually goes one way: teams create an epic called "Beta" and then can't tell when the beta is, because epics are about work, not dates. If the thing has a date and several pieces of work feed into it, make it a release.
How do you see milestones across several projects?
Native Jira stops at the project. Each release, timeline and calendar view shows one project or board, so a launch that depends on a mobile team, a backend team and marketing turns into three places to check.
There are two ways past that. Jira Plans, part of Jira Premium and Enterprise, puts issues and releases from several projects into one plan, including cross-project releases. And Marketplace apps add their own views. In ActivityTimeline, for example, a Milestones panel sits above the team's schedule and shows three things together: Jira Fix Versions on their release dates, sprints of the Scrum boards you pick, and issues on their due dates. You can also add your own milestone events (Milestone, Event, Release, Delivery, Deadline, or custom types), so a board review that isn't in Jira still shows up next to the work. Our guide to milestones in ActivityTimeline has the setup.
To be honest, if all your milestones live in one project, releases are enough and you don't need either.
Example: milestones for a website launch
A six-week website relaunch with three milestones: Design approved (end of week 2), Content complete (end of week 4), Launch (end of week 6). Launch is a release, because it's the day the site ships and 30 issues feed into it. Design approved is a Milestone work type with a due date, because it's a sign-off, not a delivery. Content complete is the due date of the content epic. Three milestones, three methods, each the right fit.
FAQ
Does Jira have a milestone feature?
No. Jira Cloud and Data Center have no milestone field or work type by default. Teams use releases (versions) with a release date, a custom Milestone work type, the Due date field or an epic's dates instead. Releases are the closest to a real milestone, because they also show progress.
Can I show milestones on the Jira timeline?
Epics with dates show as bars on the timeline, and any issue with start and due dates can too. VERIFY: how releases appear on the current timeline. For milestones across several projects, use Jira Plans or an app with a milestone view.
Should a milestone be an epic or a release?
A release, if the milestone is a delivery that several pieces of work feed into. An epic, if the milestone is the end of one body of work. If you can't say which issues belong to it, it's probably a Milestone work type with a due date.
How do I track milestones across several Jira projects?
Create releases with the same name in each project, use Jira Plans on Premium or Enterprise, or add an app. ActivityTimeline shows Fix Versions, sprints and due dates from several projects on one Milestones panel.
If you'd like to see your releases and deadlines next to who is actually working on them, ActivityTimeline has a 30-day trial, so you can check it against your own Jira before paying anything. Start the trial
