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
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,639,044
Community Members
 
Community Events
196
Community Groups

change of minimum work package size is not visible in plan

Edited
Sabine
Sabine May 03, 2019

I have planned future sprints with user stories.

In order to prevent them from filling up automatically, I set "Minimum work package size" to 100.

If I set the value to 1 or 100, I can see no difference in the plans. 

The sprints will be filled up with stories from the backlog.

What do I have to do, that planned sprints will be untouched?

Answer
Watch
Like Be the first to like this
283 views

0 answers

Suggest an answer

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

Atlassian Community Events

See all events