How do you create start-to-start, finish-to-finish, or start-to-finish dependancies

[Adam Hudson]

I am looking at moving our Project planning fully into JIRA plans. One feature I used a lot was adding traditional start-to-start, finish-to-finish, or start-to-finish relationships between tasks and activities. Not all tasks are one after another. I can not see how to do this in the plans. 

[Gor Greyan · Accepted solution]

Hi @Adam Hudson

Welcome to the Atlassian Community!

You're not missing a configuration option here. Jira Plans currently doesn't support the traditional dependency types Start-to-Start, Finish-to-Finish, or Start-to-Finish.
Dependencies in Plans are essentially treated as Finish-to-Start: work item A blocks work item B, so A is expected to finish before B starts. Atlassian also calculates dependency lead time between the end of the blocking item and the start of the dependent item.

You can still create and visualize dependencies between work items and manually overlap their dates where appropriate, but Plans won't enforce an SS, FF, or SF scheduling relationship in the same way that traditional project-planning tools do.

So if those dependency types are an important part of your planning methodology, this is currently a functional gap to consider when moving the planning process fully into Jira Plans.

You can check these sources.
https://support.atlassian.com/advanced-roadmaps-for-jira/kb/calculate-lead-time-in-jira-advanced-roadmaps-understanding-dependencies

https://support.atlassian.com/jira-software-cloud/docs/add-a-dependency-from-your-timeline-in-advanced-roadmaps

[Adam Hudson]

Thanks for the quick response.

I will have to manage it manually for the time being, then. Makes the auto-schedule almost useless until this is available. 

[Gabriela - LeanZero]

@Adam Hudson it does not have to cost you the auto-scheduler. You can run it over part of the plan rather than all of it. Pick the items you want it to work on before you start it, and leave out the pairs you are holding by hand. Atlassian's wording is that the ones you leave out "will still influence the auto-scheduler outcome as if they had been selected (e.g., by their dependencies, priorities, team capacity) but will not themselves be scheduled", so the rest of the plan still schedules around your fixed pairs. You do have to narrow it on purpose though, because the default is that it "schedules all work items in your plan, regardless of whether you’ve set dates for them". How the auto-scheduler works

The open request for real SS/FF/SF is JRACLOUD-88033, filed 2016 and still Gathering Interest on 55 votes. If the move goes ahead, add yours.

[Adam Hudson]

Thanks, I've just been playing with the selective auto-schedule, and it does improve the usage. 

I will have a look at the feature request. Tried to get ROVO to raise one as a Feature Request, but no joy.