I was just wondering, how do you implement milestones in your projects? Looking for a way of painting the big picture on the roadmap.
For example, September first, we want the MVP up and running. First I thought of using an epic, but the project part is bigger than just 1 epic.
Any ideas how to visualize such a milestone on a roadmap?
(Yes, quite new to using roadmaps inside Jira)
This feature request is gathering interest. You can read about it and vote for it here.
Until then there are workarounds in which this an be achieved, with addons, like structure (to create a milestone) or Big Picture that has this feature in built.
Or maybe you create an issue type called Milestone and link/associate features to it.
Hi @Hugo Winder
Thank you @marc_koppelaar for mentioning BigPicture. App apart from scheduling, managing, and tracking projects allows for tracking project milestones (represented as diamonds that do not have any duration) and quickly identifying them on the info bar.
In addition or instead, you can use markers to highlight important dates that call for special care and attention.
Please let me know if you would like to learn more.
Hi @Hugo Winder
What we do/have done is:
This creates an easy to view Timeline (including which sprint the milestone is expected to occur in) see below.
HI @Hugo Winder
This type of hierarchy requires an app. This could be the already mention option of Structure, but there are more options like BigPicture or Jira Advanced Roadmap and even more.
These options can be searched for on the Atlassian Marketplace, use search terms like portfolio or roadmap
Unfortunately, there are no quick answers for this one in terms of a Roadmap view without and add-on, like Structure. I would also recommend that you keep the Milestone separate from your Epic>Story relationship. These issue types have a purpose and you want to keep it that way.
I do like @bertrand_drouhard suggestion of using the Release as this can be tracked and reported on quite easily. And, anytime you can leverage base functionality, the easier things are. If you need to track more information on the Milestone and feel an issue type is the way to go, then I would suggest implementing a standard for establishing that relationship. Then use an issue link to connect that Milestone to you Epic or Story (relates to, supported by, etc). Now, I will say this from experience. If you do not set the standard early on, then you are opening yourself up to potential problems down the road. When we implemented the Milestone early on, we did not dictate how that relationship should be established. So, when we needed to report against the Milestone, it was almost impossible because teams would use different links types and they didn't connect to single issue type. We had to basically create this massive query to find everything in order to present the data. Not fun.
So, think about your downstream impacts when implementing this. That way, should you implement an add-on or attempt any type of reporting, it will be easy.
Hope this helps.
for visualisation of planned terms I am using combination of labels and epics - so if for the milestone are more epics needed to be finished give them the milestone label and in road map than you can use that filter for the label and se the targeted deadline.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events