Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

More instructions and Best Practices

We have a dozen Themes, 45 or 50 Initiatives, and over 1000 issues on our Advanced Roadmap. Here are a few of my questions:

1. To show the Roadmap and only show the current Sprint, selecting the Sprints -> Current Sprints causes much of the Themes, Initiatives, and even some epics and issues to be display grayed out. Is there a better way to only show what is involved in the current Sprint and not show so much outside the Sprint?

2. I have tried to limit what would be displayed on the Roadmap with a Filter and adding it to the Issue Sources. I have a dozen different Scrum boards as issues as well. Does the filter work across all of the Issue Sources? If not, how does it work?

3. There is a debate on whether Target start and Target end dates need to be entered for issues below an Epic. I know you can inherit from the Sprint, but would it be better to enter the Sprint Target dates on all the issues, or is that overkill?

I'll stop here to see what wisdom you can share with me. Thank you very much!

1 answer

1 accepted

2 votes
Answer accepted
Curt Holley Community Leader Jun 03, 2021

Hi @Don Hames 

Regarding 1. In the filters section (at the bottom) untick the "Show full hierarchy" box.

Regarding 2. Adding a filter doesn't filter the existing Issue sources, it adds another issue source. So by adding your new filter, you have just added everything that the filter retrieves into your plan. Each Issue source is....a source for adding issues to the plan. Think Filter Query for a Jira board, but 3 dimensional (i.e. Whole Projects, Boards or Filters)

Regarding 3. It is a fair debate....no perfect answer, so it depends on what you want from the plan, current team ways of working etc.

If all teams work in sprints, then perhaps sprint data is good enough. If not, then adding dates makes sense....though may well incur an overhead if teams are not used to adding such info currently.

Hopefully this helps?

It does, thank you, Curt. I am sure I will have a couple of other questions once I try your recommendations tomorrow. Thanks for your reply.

Like Curt Holley likes this

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

193 views 6 7
Read article

Community Events

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

Events near you