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; } } }

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

Adam Hudson_n3v8rk

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.

Accepted answers

Gor Greyan

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

All comments

Gor Greyan

Hi @Adam Hudson

Welcome to the Atlassian Community!

Adam Hudson_n3v8rk

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_n3v8rk

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.

Gabriela - LeanZero

@Adam Hudson on the Rovo attempt — feature requests land on jira.atlassian.com, which is Atlassian's own public tracker rather than one of your sites. Rovo's Jira tools each take a cloudId and act on the sites your account can reach, so that one is a manual filing with your Atlassian account, not something it can do for you.

Nothing to raise anyway. JRACLOUD-88033 is the request and it's still open, 55 votes and 14 comments as of this morning, Gathering Interest. Worth a comment alongside the vote. Most of what's on it is a variation of we need this too, so naming which of the three you actually need, and what holding those pairs by hand costs you across a plan that size, is the part that stands out.

Adam Hudson_n3v8rk

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

Gabriela - LeanZero

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

plans