This question is in reference to Atlassian Documentation: Configuring plan settings
I created my plan and added epics in Jira portfolio. How do I update the start and end dates. They are wrong and I need to change them. One would think I can simply click and change but not possible. @Martin Suntinger?
Portfolio for JIRA helps you do agile planning. Hence it's not really meant for planning with start end end dates as such, as it bases it's decisions off of other things.
You can assign issues to a sprint or release to place them roughly in a given time frame and then the scheduling algorithm will calculate their actual placement and duration based on ranking, estimation, child issues, capacity of the team, and many other signals.
We are currently working on a new feature, the earliest start date, which will allow to push an issue back to after a given date. So keep your eyes peeled for that!
I faced the same as Matt. It is not that I wanted to set start and end date for an epic in portfolio, but the system has done it probably like you wrote with the scheduling algorithm. However I'm just wondering based on what information is counting the algorithm an existing epic will start in 2025???
Screen Shot 2016-07-29 at 13.29.08.png
And just for fact, this is an in progress epic.
Is there a more helpful answer to this question? Is there any tutorial to watch?
I would like to understand the picture.
Thank you Allard that helps a lot.
What do you recommend for an agile team like mine that has to deliver feature functionality on firm due dates for our waterfall driven customers? I think you're saying we should assign the epic or release to the release that coincides closest to their due date?
In our case we service insurance companies who use on time delivery date as their success fail criteria. For example my team is working towards an October 8 deadline one of our customers has given us. The implications are we don't have to build everything right away, we can build it at a steady pace between now and that deadline in order to spread some of our resources across our other customers. In our case coming in early is not good and coming in late is also not good.
In that case I would advise mapping a release to your deadline and initially putting everything in there that you want to deliver. The release will then likely be overbooked at first. You can then descope your less important features by taking them out of the release until the release turns green.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
I am gathering information about resources available for Atlassian product knowledge transferring for a presentation in our local Atlassian User Group. I want to group them in four categories From ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG