Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
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

Join now to unlock these features and more

Reassigning stories to QA and impact to reporting

Gus Panagiotopoulos
Gus Panagiotopoulos Jun 05, 2018

Noticed on my instance of portfolio (cloud) that my current sprint capacity is not reflecting what is in JIRA.  Are there best practices when reassigning stories to other members of a cross-functional team that will manage the reporting accordingly?

 

Any thoughts will be appreciated.

Answer
Watch
Like Be the first to like this
363 views

0 answers

Suggest an answer

Log in or Sign up to answer
Portfolio for Jira
Advanced planning
TAGS
AUG Leaders

Atlassian Community Events

See all events