+10

+1

+1

Currently we use Confluence / Spreadsheet to maintain milestones and map out the Jira tickets. Very cumbersome. This feature will help a ton and help adopt the roadmap use across all stakeholders.

This will be a valuable addition as our management want to view milestones within plans

When can we get an update on the prioritization of this feature and development timeline? My company is inclined to use another platform if we cannot add something as simple as a milestone to our roadmaps. 

A suggestion for an additional (optional) functionality

• User can link a milestone to Epic, Task, or Story and see the dependency on the roadmap 

+1

Hi all -  Rathesh here from the Jira Software Cloud team. Thanks for your votes on this ticket! 
This is currently under consideration in our roadmap, but we'd love your help! We have a few milestone concepts that we would like to show you to get some quick feedback on how it could help you or your team plan and track more effectively. 

If you are interested in being part of the solution and providing feedback on some concepts, feel free to book in a 30min call here: https://calendly.com/ratheshr/planning-convo

Cheers,

Rathesh Richards, Product Manager - Jira Software Cloud

PLEAASSSE add this!!! 

Can't believe such a basic feature has been missing for years.

Well, happy birthday to this item! Another year, another 365 days of nothing happening. But hey, at least it's still on the backlog collecting dust. Here's to hoping for some actual progress in the next year. (But let's be real, that's probably not going to happen).

(Sorry, I missed this yesterday)

+1

This feature is necessary if the Roadmap wants to become a proper project management tool. Without this, I cannot find a good use of Roadmap 

+1 to this feature.  We have a large multi-quarter project on Jira and would love if we could add our milestones in Jira itself. 

Seems like a fairly basic feature of a roadmap. Please add.

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1 for this. Surprised it isn't already there.

+1 This would be a great feature to break up Releases into MVPs, etc

+1 love to see this feature soon

+1, this is a much-needed feature. I am longing for Microsoft Projects, that probably says a lot. 

I agree with Hugo Winder. Maybe, as users of Atlassian, we call on Atlassian boycott. We can call it "-1" boycott for Atlassian.  

It's highly doubtful that this will ever happen. If it's been stuck on the backlog for three years, it's clear that it's not a priority. And let's be real, even though we're throwing money at Atlassian, it's not like we have any real say in what goes on around here.

+1

+1

+1

I can't believe that this proposal is still under consideration after being created 3,5 years ago, making around 200 people leaving comments and asking for it.

This is critical for tracking "hard" dates.  We'd like to move off of Product Plan and this feature would allow us to do so.

Idem ! Do you have an idea if/when will this feature be available? 

Thanks 

+1

C'mon Atlassian engineers and project managers, you don't use milestones?!

The one thing actually useful in management.

I have grown old watching Atlassian miss the opportunities to actually follow the PMBOK, but this is just unprofessional.

What is the threshold that any feature is implemented?

having milestones on basic and advanced roadmaps would make a big difference for us, as we need to breakdown long-term projects in a visual way that's less dependent on sub-tasks, aka beyond relying on the progress bar (by issue count).

+1

+1 We could really benefit from this!

Would love this feature

This feature is a must to handle projects in JIRA. It should be release at the earliest and should part of standard license.

+ 1

+1

+1, it really helps team.

+1

Upvote from me too.  This would take a little pain out of my day and visually improve the project view.

Upvoting as well. We have a team that just changed system because of this type of feature missing.

upvote! 

pls also add keydates and the possibility to add dependencies on keydates like in roadmunk

Yes, milestones feature helps us to identify major work done in any project. It's must-have feature in any SDLC. 

Would be really nice to have this feature in basic roadmaps!

A roadmap without milestones is quite unusable for my team.

it's essential to have this feature

Agreed! Please add this functionality. I am currently using releases as a workaround but it is confusing to the team. 

Azure Dev Ops have this feature in the planner. A great feature!

This is an important function for Roadmap. It will be quite useful if you can provide this shortly.

Actually, a special built-in issue type Milestone would be quite appropriate.

Lack of this and failure to visualize any issue dependencies except "blocks" makes Roadmap very difficult to maintain and interpret, almost useless for long-term planning.

This is very important functionality.

Please add this natively and put some reporting on it too across projects!  I had to create a new issue type "Milestone" and try tracking things that way.

Do I get the right impression here that this feature is still not available - as one of the most basic project management use cases and 3 years after the initial request?

Milestone would be beneficial in reporting target dates for events or rollouts. 

Milestones are something that is really missing to improve the visibility of a bigger plan - it's pretty often you move some US here and there, but there are still some deadlines in the process to unblock other teams etc.

It would be great to be able to see this feature on the basic roadmap screen! This is needed.
Also, using the roadmap view without milestones is not useful

very much needed!

Please add this! Currently it's almost impossible to track and visualize different stages in a project. We're using workarounds by creating several epics and linking them, which is not great and bloats the visual roadmap unnecessarily. What we imagine is a possibility to split epics in different stages –also visually on a roadmap– and add markers for milestones.

That'd make our lives a lot easier

This is definitly needed

Big flaw that we can not roll up tasks or epics into milestones!!! This is needed

actually it is possible to display milestone using release date but in the advanced roadmap

Rolling up tasks or Epics into a milestone is paramount. We are using Cloud Jira and there is absolutely NO WAY for me to represent burndown on milestones to stakeholders and leadership within a specific release. This may not be the way to solve this specific issue, however it would work towards being able to project if we are on track and sanity check whether were making the right progress.

I would see a milestone as a gatekeeper to the list of tasks/issues below it.  All tasks would roll up into that Milestone.  Once all tasks are completed, I could proceed to the next Milestone.  For example.  Phase 1 - Project Introduction has a number of smaller (like child to parent) tasks but I want the ability to mark off this milestone as completed.  Then I would proceed to Phase 2 - Build - Where again a number of smaller tasks would appear that roll up to the Build phase only.  The main milestones could then be filtered on the timeline view.  Matched with dates also, the timeline would show us the tasks due dates and status of how it is tracking.  Really just like a gantt chart I guess.    From my pic below, Project Introduction is the milestone.  The rest are the tasks below it.  

Agreed with @kamil.bubak and @ahafellner that milestones should be visualizations of distinct points in time. That would offer the flexibility to mark a release if so desired, but also to mark external events with fixed dates that are important, like industry tradeshows, etc.

As a Project Manager or Program Manager, I want to roll up all projects of a certain type by standardized milestones so that I can see: we have 20 projects in this phase of the project that have not reached X Milestone; we have an additiional 30 projects in this phase that have not passed Y milestone. Milestones are the culmination of a project phase in standard project methodologies.  The Project Manager should have the ability to standardize these milestones against project templates (I know not yet available) with a standard set of tasks and roll these all up against milestone reporting in a roadmap. 

in regard to the comment of @Janic Mikes -> without (2) it is kind of useless for us as we do not only manage releases but serveral different Milestones with different meanings

For me a milestone is pretty much equivalent to a release (version).

A vertical bar indicating the due date of a milestone would give a nice overview on the big picture on what's going on in the project.

I do see two scenarios for the roadmap:

1. Visualize release versions (I commonly use these as my milestones)

• Can span over a period (if start and release date are specified) -> show up like sprints
• Will only show up if they have a release date specified

2. Add arbitrary vertical markers on a specific date on the roadmap and give it a name, description

• could also be issues with a specific issue type (would require the possibility to configure "Milestone Issue Types" on the roadmap) (Issue type could be "Milestone")
• Using issues would allow to use all the other functionalities like linking or commenting. (The due date is used for the marker)

Both should render a vertical line at the due date to indicate those fixed points in time.

For me the first scenario would probably be sufficient. But the second one would provide additional flexibility.

From my perspective important this is that Milestones are just points in time, not periods. So I would like to see them as points on the Roadmap's timeline (what make a difference between them an Initiatives for example). With rest I totally agree with ahafellner

In the same way an Epic expands/collapses to show issues, I would love milestones to expand/collapse to show Epics, that would then make for a much neater presentation of the roadmap to a client of being able to go in to the detail without having to navigate the clutter.

my point of view in regards to Milestones:

1. have a name, due date and description
2. are an issue type which I can query for and give additional fields 
3. can be related to other issues
4. show on a roadmap with a vertical line like the current day so that I see that we are approching that milestone and if specific ecpis end before or after that milestone
5. several of them can be set with the same due date and still show correctly on a roadmap like marks in azure devops
6. perfect would be if a release could be generate a milestone on my demand

I would add a mock so that you can see exactly what I mean but I am not allowed to add attachments

Hi folks, 

Thanks for your continuous interest in the "Milestone" concept and your feedback to help us improve the product experience. 

I'm happy to share that it's absolutely one of the top commitments for the Jira Roadmaps team at the moment. At this stage, we'd be keen to collect not just your interests, but requirements, so to help us better define this feature.

If I may ask you a few questions on how you'd see Milestones help in your road-mapping context:

• What's in the Milestone that you'd been keen to learn about?
• Imagine Milestones can already be seen on the timeline, how would work with them (what tasks do you do around them)?
• How is a Milestone different from releases (or versions)?

Thank you so much for your attention. We'll keep you posted on any updates on this feature.

Warm regards,

Shuchen

Roadmaps Team

It would be great to get some feedback if this is somewhere to be seen in one of the next versions!

Is there any update as to where this is in your roadmap?

so, this feature request from 2019, with now 1200 votes, in fact the feature with 3rd most votes , a feature which already exists in your other products / parts of your application...
I duno what to say - I really don't want to rant - so I'll just leave this comment here...

I'm surprised this isn't a feature. Atlassian documentation for a "generic" roadmap even shows milestone markers (https://www.atlassian.com/agile/product-management/roadmaps) 

This feature would save a lot of manual effort for me. Currently I am exporting the roadmap view to PowerPoint and manually add the milestone lines.. Please add this feature!

@Peter Morawski, as a workaround whilst this is being looked at, could you not create your own Milestone issue type and have the start and end date the same? I have done this just using the task issue type as a test.

I would say that a visual cue in the roadmap would be the minimum would be the most basic implementation of a "milestone". A more advance implementation would be a special type of Issue of type "milestone", as described in the comment of @Peter Morawski.

As this is gaining traction, I'd like to support here, too by adding following thoughts to your question "is a milestone just a visual cue that you need to communicate on your roadmap, or would other teams need to see it elsewhere in Jira?":

To me, the way I repeatedly tend to look for this feature, is to either be able to click onto the grey week/month/quarter area to see if I can add a visual cue; the next would be to look for kind of a ticket type "milestone" with start/end date being more or less the same. That, in turn, would give the opportunities to e.g. filter for "ticket type = milestone" e.g. in Confluence, or in Issues list, etc. I guess there are more advanced ideas, but this could be the "MVP" type start.

As a Program Manager, I would also like to be able to create a template with standardized Milestones and Objectives, so that every project using that scheme has to meet the same criteria prior to passing the Milestone. 
I would want the ability to display many projects within a Roadmap and identify their progress between milestones via a Roadmap display on Confluence.

Hi 2639f03d8bac thanks for your suggestion. Unfortunately, if we review this feature, it would only be for the cloud version of Jira Software, to help customers migrate to the cloud. 
Happy for you to send your slides/suggestions to be me directly at rrichards@atlassian.com 

9c6e4df95cf8 and 9aea4b7ec152 , is a milestone just a visual cue that you need to communicate on your roadmap, or would other teams need to see it elsewhere in Jira? 

I am evaluating a migration to Jira, and this is one of the first issues we were looking for. Please, implement it

Hello 762b441b532a, I suppose you will release the same functionality for milestones for the Server/Database version the same time as for the Server version. See also the other ticket JPOSERVER-2825. Please give feedback there as well. By the way, I already sent several times a slideset with improvement ideas, use cases, MVP etc. to the Atlassian account for our company, but it seemed nobody is unfortunately really interested. Hopefully it changes now soon.

Please also link this ticket to the JPOSERVER-2825.

Thanks.

Dear Rathesh, you could get some inspiration from the "structure gantt" app, that we started using because Jira classic and next-gen were not offering the milestone (and other) functionalities. In my company we have also some "waterfall" projects, that we still manage with Jira, so it is useful have a kind of "MS project" view for the work to do.

Also showing visually the dependencies helps (not only at epic level, but also at user story level).

Hi all - Thank you for your valued feedback. 
I'm a Product Manager on the Jira roadmaps (simple) team. We are considering this request on our 2022 roadmap and if/how it could be utilized within Jira Software. 

If you have specific use cases, please comment on this ticket. If you would like to have a chat in detail about how your team plans or communicates progress towards milestones, you can book in some time here: https://calendly.com/ratheshr/planning-convo. I'd love to understand any pain points and see how Jira can better support your team's needs in the future.

I want to reiterate that your feedback is appreciated and reviewed, and we’d love to keep hearing from you. Keep an eye on this ticket for updates in the near future.

What is the threshold number after which the status for this goes into consideration?