Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How can i define milestones with JIRA Portfolio

Hello Experts, 

we are currently evaluating Portfolio, 

We would like to manage product implementation projects, and for that we need to define milestones

Can you please advise how can I define them in Portfolio?



5 answers

1 accepted

0 votes
Answer accepted

Your milestones are effectively your release dates, you could create epics for certain stages of your project and assign these to releases which match your milestone dates.

That isn't a very good approach. There can be a lot of issues tied to a milestone in different ways including:

  • Cannot start until the date
  • Milestone cannot be met unless issues are accepted

Those "stakes in the ground" can be moved independently of other works and may or may not impact a release. They may be a date that a tool arrives from a 3rd party or almost any other thing, and there can be many of these special dates in a release cycle. 

I can see that using releases can do some of the same thing, but conceptually it is better to keep a "release" with a specific meaning and a milestone with its own specific meaning and not muddy them together. 

Like # people like this

Just some examples of dates("milestones") that are not releases.... feature/code freeze, trade show dates, scheduled maintenance on environments... to work around things, you have to be able to see them alongside your release schedule. 

Like # people like this

It is just to add in the Gantt view similar to today´s day a vertical line for specific milestones indicating the iD or the name as a visual representation of the milestones. In 2014 it was posted the following suggestion with 125 votes:

Please solve this issue and enable milestone visualization and add suitable features as requested with ticket  JPOSERVER-2825. I really don´t understand how a tool can be called advanced roadmap without adding the possibility to visualize milestones. At least it should be possible to show naming of the fix versions/releases, create abbreviation of the name and blend in/out milestones as needed.

Hi, has this matter been solved? Any other suggestion, how to add milestones in Portfolio without using releases? Thanks in advance :)

I do not see that it has been resolved. Key dates and milestones within a release are a useful mechanism. 

The issues is still not resolved unfortunately!

There is always a need to see dates different than release dates in a project plan.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events