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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

How to define releases for sprint planning as well as long term plan with Portfolio

We ship features every two weeks and all the committed features should be shipped to customers by 19.08.02 ( 2-Aug-2019) I created a release “19.08.02" in JIRA , included all epics in it and portfolio has made the plan for me and assigned user stories and bugs to different sprints. For all the user story added to the release, the field “Fixed Version” has been updated to 19.08.02. Before we started using Portfolio we used to create a release for each sprint and ship the product every two weeks. Our QA and customer support team used to track "Fixed Version" field to track all deliverables. Now that we have to have a long term release plan along with by-weekly releases, what is the correct way to track by-weekly sprint deliverables so that QA and customer support team knows what is being released in each sprint to prepare release documents. My confusion is due to the assumption that if we continue to create by weekly releases, I cannot add a story in short team sprint release and the long term release. Is this understanding correct ? If yes , what should be my approach so that I can continue to see the long term plan prepared by portfolio and also track what is being released in each sprint. Is my presumption correct that we need different custom fields to track long term and short team releases. If I create separate releases for each sprint for the next three months and assign issues to them, then I'll be doing the scheduling instead of portfolio and this does not seem to be correct approach.  It is a common use case, but I’m doing this for the first time. Any pointer will be greatly appreciated. Many thanks in advance.

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Advanced Roadmaps

3 short videos to help you get started with Advanced Roadmaps

Hi community, I’m Roi, a product manager working on Advanced Roadmaps for Jira. While Advanced Roadmaps is a powerful tool to plan and track work at scale, we know it can be challenging to get star...

6,512 views 25 18
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