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

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. 

@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.

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.  

Im so new to this im not even sure how to find JRACLOUD-88033 to vote and add a comment. 

@Adam Hudson straight there: https://jira.atlassian.com/browse/JRACLOUD-88033 — or paste the key into the search box on jira.atlassian.com and it'll find it.

Sign in first, top right. It's Atlassian's own tracker rather than one of your sites, but the login hands off to id.atlassian.com, so it's the same Atlassian account you're already using. That's the step people miss: read it signed out and you get a Log In button where the vote and watch controls would be, which looks like they aren't there.

Once you're in, vote and start watching it, then leave the comment. The status line on the ticket is worth reading because it tells you what actually moves one of these — it says the suggestion needs more unique domain votes and comments before it gets reviewed. Unique domains, so another vote from a company already counted moves very little, and a first comment from a new one moves more.

On what to write, Atlassian's own new features policy puts it plainly: the most helpful information you can provide us when commenting on issues is how a particular suggestion would help you. So which of the three you actually need, and what holding those pairs by hand is costing you. You said it makes the auto-schedule almost useless. That is the kind of thing they are asking for.