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!


If I move an Issue to a later Sprint on JIRA side, will the Sprint also update on Portfolio side?

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?

1 answer

0 votes
Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jul 15, 2019

Hi Matt,

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.


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events