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
Interests
See all
Community resources
Top groups
Explore all groups
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

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.

Get started Tell me more
Atlassian Community about banner
4,560,360
Community Members
 
Community Events
185
Community Groups

Adding boards in Portfolio scenario

Dieter Eichert
Dieter Eichert Oct 16, 2017

I want to add an additional board/project in Scenario b of my portfolio planning. How can I do that? Reason: I want to separate specific projekt workload from Feature requests and want to show the impact of feature Requests

Thanks in advance

Answer
Watch
Like Be the first to like this
416 views

1 answer

0 votes
Jason Golden
Jason Golden
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Become a leader
Oct 20, 2017

This is not possible - Scenarios are fixed to the plan as you have it configured to boards/projects.

One way to accomplish what you're describing: include the feature requests in your board configuration. Then, associate these workload impacting feature requests to a unique Epic called "Pending Feature Requests" (so they're not at the bottom of the plan) and leave them unestimated and not assigned. Then, in Scenario B you can put estimates on them and see the impact to your schedule and workload.

-Jason Golden
Denver AUG Leader

Reply

Suggest an answer

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

Atlassian Community Events

See all events