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!


Advanced Roadmap - integrating milestones


We work in 2 weeks sprints, using the SCRUM methodology.


There is interest from our external stakeholders in our Advanced Roadmap to represent the Design, Implementation phases.


Our User Stories are really Dev Tasks currently, and Epics are the top level defined story from Product.


I can certainly have a set of Stories for the 'design' of various components and services and just assign them to a release as a milestone.


I believe our stake holders are concerned with the current Design, and next phase implementation and want to know when we will have a better sense for the remaining implementation.

2 answers

1 accepted

0 votes
Answer accepted
Dave Mathijs
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 07, 2023

Hi @Neil Wills until Atlassian really acknowledges and implements the concept of Milestones in Advanced Roadmaps, the best workaround is indeed to work with versions/releases as they represent a point-in-time.

Creating a specific issue type for milestones wouldn't resolve that issue as you can only place 'markers' on a plan with releases, not with the (target) end date or due date of an issue.

Using Releases for significant milestones for actual release to UAT, Staging, Product


But it does not seem worth it for design, implementation phases for each dev task or story.


To define a story or milestone to communicate that during a sprint that some or all of the stories related to design or implementation is an anti scrum pattern

0 votes
Eddie Meardon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Apr 11, 2023

Hi @Neil Wills

As @Dave Mathijs said, it's currently not possible to do what you're asking, and his advice around a workaround is the best we have right now. 

BUT. We have a feature request ticket open for Milestones, and it's currently being explored as a new feature. Here's the link to the feature request ticket. Vote for it to express your interest (we do watch these totals), and Watch the issue to be notified when there's updates. 

Hopefully we'll have a better solution to your problem in the not-too-distant future. 



Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events