Disable calculation (sprint auto assigning) in Portfolio

[Johan]

We leave some issues unresolved even though the sprint the were in is closed, due to not yet being released. (Not recommended, I know..)

These issues are being assigned to the coming sprints where there is free capacity, ending up in overbooked sprints even though this isn't the case. 

Is there a way to avoid this?

[Thomas]

Hi @Johan,

Assuming the "releasing" part of the process does not represent any work on a planning point of view, setting the estimate to 0 would ensure the issue no longer gets scheduled (new sprint/release/dates/team member...).

Another possibility is to exclude those issues if they are no longer impacting your plan. Excluding the release would exclude all issues assigned to that release.

Cheers,

Thomas

[Johan]

Hi Thomas!

Thanks for the quick feedback. 

Excluding the issues from the release would not work since it is not yet released. This is the way to understand what issues to 'really' close when actually releasing.

To remove the estimation might work, but then obviously remove the estimation when going back if needed (even though it is traced in the history of the issue). I guess this would work.. I assume the sprint report will not be affected if the estimation is changed after the sprint is closed, right?

Just to confirm, there is no way of not letting portfolio 'assuming' things like assigning issues to sprints, but rather use what is explicitly stated in JIRA?

I do understand that this is one of the key points in Portfolio, but if needed it would be great to be able to chose whether this kind of things should implicitly be assigned..

BR

/Johan

[Thomas]

Hey @Johan,

When I mentioned excluding, I actually intended "Excluding the issues from the plan", you can achieve this by selecting the issue in your plan (checkbox) and clicking the "Exclude from Plan". I understand excluding the whole release would be a bit of an overkill.

Regarding estimates, Jira has 2 estimates field: Original Estimate and Remaining Estimate. Portfolio estimate field is linked to the remaining estimate one so you shouldn't be losing that historical track record. This also explains why your Plan insists on having it scheduled as it has remaining work.

Closed sprints should not be impacted by changes in the remaining estimate fields if done after the sprint is closed.

Regarding being more flexible on what is scheduled and what isn't, I'd suggest having a look at the early access to our new planning experience introduced in Portfolio for Jira Server/DC v.2.18.0 (https://confluence.atlassian.com/jiraportfolioserver/portfolio-for-jira-new-experience-952623566.html)

Cheers,

Thomas

[Johan]

Hi!

Thanks, makes perfect sense.

BR

/Johan

[Johan]

Hi again!

It seems that it issues still is scheduled in coming sprints even though remaining estimate is set to 0. However, we are using story points. But, even if I set story points to 0 it is still scheduled in the coming sprint.

BR

/Johan

[Thomas]

Hey @Johan,

If the plan estimate is set to Story points (so those are the fields you see in your plan and not the time estimates one) then the only other reasons for something to be scheduled:

• It has one or more children with some estimate
• It has a sprint assignment -> This trumps everything.
• It has target start/target end fields set

Hopefully, that will help!

Cheers,

Thomas