What is the logical rationale behind "Sync duration and milestone on insert/update" Business Rules?

MBarrott
Mega Sage

‎06-18-2024 08:32 AM

I've noticed that when created or updating tasks on the planned_task table and marking them as a milestone, it will trigger one of the two Business Rules:

 

- Sync duration and milestone on insert 

- Sync duration and milestone on update 

 

This seemingly sets the end_date field of the task to match the start_date field data of the task. Could someone explain what the logical reasoning is behind this? 

 

My team thinks we should disable these BR's as they want to ensure the end_date isn't being modified unnecessarily but I'd like to know the logic for such a BR so my team can get a better understanding. 

0 Helpfuls
  • 261 Views
1 REPLY 1

HrishabhKumar
Kilo Sage

‎06-18-2024 09:08 AM

Hi @MBarrott ,

After going your question and drilling into it, I'm concluding my findings below, hope they help you.

 

The business rules "Sync duration and milestone on insert" and "Sync duration and milestone on update" ensure that the end_date of a milestone task matches its start_date because:

  1. Milestones Represent Single Points in Time: Milestones in project management signify significant events or deadlines, which occur at a specific point in time without duration.
  2. Data Consistency: Ensuring start_date equals end_date prevents misinterpretation of milestones as tasks with a duration, maintaining data integrity.

Implications of Disabling These Rules:

  1. Inconsistent Milestone Representation: Without these rules, milestones might incorrectly appear to have a duration, causing confusion.
  2. Deviation from Best Practices: Milestones should remain single-point events to align with project management standards.

Recommendations:

  1. Educate Your Team: Explain that milestones are meant to have the same start_date and end_date.
  2. Review Specific Needs: If your team has valid reasons to change this behavior, consider if those tasks should be categorized differently.
  3. Modify with Caution: If you decide to disable these rules, ensure thorough testing and implement other measures to maintain data integrity.

 

Thanks,

Hope this helps.

If my response proves helpful please mark it helpful and accept it as solution to close this thread.