nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

What sets the "Scheduled start" date?

David Doria

In the Scope panel, issues have a column called "Scheduled start". Unlike "Target start" and "Target end", this does not seem to be editable. Presumably this date is getting pulled from some information on the actual issue - is there a way to change this date?

Comments

Victor Florin Pana

https://confluence.atlassian.com/jiraportfoliocloud/scheduling-behavior-828785428.html

David Doria

So is the answer "no"? There seem to be some things, like the list of sprints that this issue has been in, that are part of the "history" and cannot be changed - is this correct? Thew view for "Scheduled range: Full" is goofy because of this, where something extends back many months just because it has been pushed to future sprints a few times.

Thomas_rff8bi

The scheduled start and end columns you are mentioning are not part of a Jira issue data and represent the scheduling calculation result. It is not possible to change those currently.

More generally the values given by the calculation are not modifiable as they represent the idealistic dates decided by Portfolio for the data currently in your plan.

Florian Friedebold

Have you tried editing the start date of your first or concerned 'Version' resp. 'Release' ?That's accessible via your board, where you can also see your epics.

If you have the dependencies set up properly between your epics and tasks, the 'Scheduled Start' should recalculate to a new date.

Best regards

Surbhi Soni_6ovgtl

Hi @David Doria , Its probably late and already have answer to it but still want to share my findings.

The "Scheduled Start" & "Scheduled End" date picks up data from the "Target Start" & "Target End" dates respectively.
"Target Start" & "Target End" are Locked Date field specifically created for Portfolio in JIRA.

One way is you add both of the fields in the JIRA tickets screens and then update the dates.

In Plan, you can choose any other custom date field suitable to display the start and end date in configuration Setting of Plan.
So by this you are basically telling Plan to consider the custom date field.
Make sure the custom dates you select here is present in all issue screen & is populated.

Note: I tested this in JIRA DC version 8.20.

Hillary Moore

Which date fields are used by the scheduling calculation? Which dates fields have to be populated in order to calculate a schedule?