Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

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.

Atlassian Community about banner
4,460,656
Community Members
 
Community Events
176
Community Groups

Assigning dates to sprints

Has anyone figured out how Portfolio assigns dates to sprints? During the training class, it seemed as though Auto-Plan would assign dates and sprints to the issues. I was just wondering what fields in JIRA Portfolio uses to set the begin/end dates?

I did not see a way to explicitly assign dates to sprints other than starting the sprint, which we don't want to do for sprints that are months out. Our current process is to manually assign begin/end times to issues knowing that those dates are the begin/end dates for the sprint. Is there a better way to do this?

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events