jarvant ysabele enricah
Eboni Kleifgen
As this is the most common type, you are likely to be familiar with it however you may not know that the tasks you are scheduling do in fact fall into this dependency category. In order to help you recognize which types of project tasks fall under this dependency type, I have provided a number of examples.
All mistakes need to be fixed prior to printing the book to ensure no mistakes make it to the final copy. It is therefore crucial that printing does not begin until the editing process is complete, making this a finish-to-start task type.
It is important to know what type of relationship is held between tasks as it allows effective project scheduling therefore I hope this article has allowed you to gain a greater understanding of the most common dependency and when it would be used.
Using the Roadmap functionality you can create a finish-to-start relationship between issues. However, that does not necessarily cause any other action/event to occur automatically. Jira does not automatically change the start date of one issue based on the finish date of another.
What I am trying to accomplish - while creating new stories for the backlog that are not currently being assigned to a sprint, is that one story (predecessor) has to be completed before the successor/dependent story can be started. I am currently not interested in setting up a timeframe, but want to create the dependency while I am creating them and not have to make a manual note to remember this. I did add a "link" but that doesn't tell me which one needs to be done first and see the Dependency dropdown, but I only see "Option 1" in the list and not sure what that means.
What you are seeing as the Dependency field is a custom field that was added to your Jira system/project. That is not the field that is used to indicate a dependency between issues for the Roadmap function.
If you are working with a Company Managed project you can confirm it is a custom field by going to the Custom Fields screen (under Settings > Issues) and searching for the field. I have a Free Jira subscription and I don't see that field in my Custom fields.
You start by defining the type of custom field you are adding. It appears that you added it as a Drop Down field. You can learn more about the types of custom fields that can be added to a Team Managed project and what each type does here:
In that case you would need to be able to pick Issues in that field. Currently Team Managed projects don't support a custom field that allows you to select an issue like the Linked Issues feature does.
Though it's not good practice, only way I know to use FS and have same start date is to use Negative Lag. Assuming ID of Task A is 5, in the predecessor column, enter 5FS-2 (where is the duration of Task A).
Here are a couple of options. In this example a custom Project calendar was created based on the Standard calendar except Saturday and Sunday are normal working days. For the first two tasks, a Task Calendar was selected using the built-in 24 hour calendar. Keep in mind that Project only allows one definition for a "day" so with a default 8 hour workday, "task a" completes at midnight but "task b" then starts immediately on the same day (i.e. 1/13/23). For the second two tasks with the 7d workweek, "task d" will start on 1/13/23 as long as "task c" finishes before end of shift on 1/13/23.
You could also extend the work hours of the 7 day calendar (e.g. 9 hour workday) such that an 8 hour task will finish at 5:00 PM and a successor task will than start at 5:00 PM since there is still one hour left in the workday.
(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?
The predecessor is finishing on 10/02/15 while the successor will have to start on 10/04/15. I have a FS with 59d lag but a colleague (who is a planning consultant) advises that a lag should NEVER exist in FS relationship. Please assist in shedding more lights.
Lags on SS and SF relationships usually represent volume lags (even if the software does not have the functionality to distinguish between volume and time lags). As such, it is the volume of work in the predecessor activity that is adding the time to the project. To shorten the project, that volume of work in the predecessor must be performed faster (i.e., dig the first 100m. of trench faster so as to start laying the pipe). So the lag on an SS or SF relationship that is on the critical path will usually represent drag and drag cost that is in the predecessor activity.
which meant that you know the activity was going to be delayed by 59 days so instead of putting in the detailed activities that make up the 59 days with the proper logic you just wanted to use a lag of 59 days to represent your delay.
To shed more lights, the project is a Design and Build where it seems somehow difficult to accurately measure the exact duration to get client approval on designs. The 59d lag was added with an assumption that approval will be received within that horizon. Any better ethics to provide for such rolling-wave will be appreciated.
as FS relationships with a 59 day lag is generally not a good scheduling practice technique to use. One of the main reasons is that the lag is not defined anywhere and you will have to reduce the lag as time marches on. A lag this large is nebulous and can and will case confusion. Who other than you knows why the lag was put into the schedule ? you can not filter on a lag. it is difficult to trace back dates with a large lag in the schedule. What if the lag becomes larger or smaller ?
You have the solution in your second post. I do not understand why you do not add an activity with a 59 day duration for "design approval" or better yet add that whole chain of activities that comprise the 59 days. This will then be clear to all parties involved in the project and will give you the ability to track the delay or each item that makes up the 59 day "LAG"
even with the posts above concerning the 7 day lag to use for curing this also has issues. What calendar does the curing lag use ? Does it use the 5 days per week calendar ? You can set relationship lags to either use the successor activity calendar, the predecessors calendar, a 24 hour calendar or the default calendar. HOWEVER this setting is for ALL lags not individual lags such as curing.
Regarding my case, I am using lag because- Setting Out activities cannot start due to some site issues till after 59 days of completing the predecessor (design approval) but the consultant is rejecting on the basis of NO FS WITH LAG rule.
I agreed with your illustration regarding required lag for curing after casting but I got more confused due to this clause from the referenced link above CAUTION: It is highly unusual for Finish-to-Start (FS) relationships to have positive lags.. Can you give further analysis on what this means?
Lags never existing on an FS relationship is a little over the top in my view. -A classic example of proper use of a (time) lag is to allow for the curing time after a slab has been cast before putting anything on it, and this would typically be an FS+lag relationship.
By integrating project portfolio management, project controls and project management into a single enterprise solution, EcoSys provides an enterprise-wide perspective into what drives project success throughout the full lifecycle of projects.
Contruent is the premier capital project management software solution that empowers owners and EPCs to build large construction projects with precision and speed. Contruent is faster to deliver across the project lifecycle because it integrates cost and scheduling and comes project-ready out-of-the-box with 25 years of best practices built in. The result is higher accuracy, speed and cost efficiency. Founded in 1994 as ARES PRISM and renamed with the launch of an innovative SaaS platform, Contruent operates in 26 countries and serves professionals across many industries.
I am trying to allocate a secondary task (Task B) that should start at the same time that Task A, and finish at the same time too. Task A is the independent variable and Task B should follow (and adjust if Task A changes duration)
I'll try again and try to pay close attention to exactly what steps I am taking and in which order I take them. In the meantime, (entirely up to you) I would suggest replying to the email and referencing this thread again letting them know that it SHOULD be possible and there is an example of it working on here.
I opened a support ticket, but I can't close this pop-up no matter what I click or what browser I use and I'm wondering if anyone has any insight. I'm LOCKED OUT of my work because of some stupid UI refresh alert. ?
In other words I want task #20 to begin on the Effective date and to finish the same time as task #24. Why does Smartsheet show the start & finish date both as the finish date of task #24, when it should start on the Effective Date? Actually I think Finish-Start will start it the day after the Effective Date.
c01484d022