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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

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!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,461,858
Community Members
 
Community Events
176
Community Groups

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

Atlassian Community Events