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,552,573
Community Members
 
Community Events
184
Community Groups

scheduled start date

All, we are new to Portfolio for Jira. We have been piloting the tool for a few months now and have been very excited about  the benefits it will provide for release planning and presenting scenarios that will drive decision making. I am currently running into an issue that I am sure is pilot error. Before we started using Portfolio for Jira we had fully planned sprints under Jira. Now we are trying to pull this data into portfolio.

 

We have our teams, skills, and capacities all setup in portfolio. Each of the teams is associated with an existing board in Jira. When I click the Calculate button the start date for the Epics that are in flight updates to a date a few weeks in the future even though there are stories under the epic that were closed a sprint or two back. Is there a way to configure portfolio to set dates based on the epic/story data?

 

I was expecting portfolio to look at the story data under the epic and figure out what is closed and when it was closed (which sprint) and then calculate the schedule based on this information. But this doesn’t look to be the case.

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events