You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
If I have a Portfolio Plan calculated with Sprint allocations, and I commit the changes to JIRA, it puts the backlog issues into planned/future Sprints on the JIRA Scrum board side to match the Portfolio. If the team then moves the story on their JIRA Scrum Board to a later or earlier Sprint, will this update be automatically reflected back on the Portfolio side?
Yes, the data portfolio side should be reflecting what you are setting Jira side, but some operations require a calculation to fully update.
When you commit data in Portfolio you are verifying a write operation to jira and when you view a Live plan in Portfolio portfolio you're asking for a read from Jria's live data set, and then when you run a calculate you are requesting the portfolio specific data lines up with any updates to the Jira data and re-runs the scheduling algorithm to define the projected scope.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.