Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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!


Approaches to Milestones, Key Dates, Releases... Versions vs. Sub-Issue? (Migrated from Roadmunk)

Howdy all... we are eyeballs deep in onboarding our product team (4 product groups of 2-5PMs each) into Jira Software + Advanced Roadmaps. Our engineering teams have been using Jira Software for a while, but our Product Team has not historically used Jira.

Previously, we used Roadmunk, which we did not like, and would not serve our needs for operational excellence, consistency, and scalability.

In Advanced Roadmaps, we are using the following hierarchy:

  1. [Portfolio] Legend
  2. [Product Group] Initiative
  3. [Product Group] Epic
  4. [Product Group] Story

However, one feature we definitely liked in Roadmunk was the ability to add milestones / key dates for any stream of work. A couple Roadmunk articles are referenced below and at the bottom of this post, I will add a couple images for visual reference.

As I understand it, Atlassian intends "Releases" to be used for milestones. However, this does not really work for us because it seems to create visual havoc in AR when looking at group and portfolio views. Releases seems to work for larger-scale, portfolio-wide release planning, but not all the other, variable milestones. 

For us, different workstreams have different milestones depending on scope + product group + engineering team.

Has anyone figured out alternate ways of accomplishing milestones / key dates within Advanced Roadmaps?

One of our PMs had the idea to create a sub-issue type: Milestone ... that could be associated with any issue type in a more ad-hoc way depending on need. 


Roadmunk Screenshots for visual reference

Roadmunk: Working with Key Dates




Roadmunk: Working with Milestones




Log in or Sign up to comment
AUG Leaders

Atlassian Community Events