feat(tracker): Gantt — #5 tier-2 (undo/redo, saved views, bulk-select, auto-scheduling)

models/tracker/src/index.ts

@@ -196,7 +196,9 @@ function defineFilters (builder: Builder): void {
         key: 'milestone',
         component: view.component.ObjectFilter,
         showNested: false
-      }
+      },
+      'startDate',
+      'dueDate'
     ],
     ignoreKeys: ['number', 'estimation', 'attachedTo'],
     getVisibleFilters: tracker.function.GetVisibleFilters
@@ -596,6 +598,35 @@ export function createModel (builder: Builder): void {
     tracker.ids.IssueRemovedActivityViewlet
   )
 
+  //  — Activity-Log Remove-Detail Fix.
+  // Three symmetric viewlets so IssueRelation add/remove/update show up in
+  // the issue activity feed with a kind+lag+target.title snapshot instead
+  // of the previous empty "removed related to:" row. The
+  // RelationActivityPresenter reuses IssueRelationPresenter, which is
+  // already registered as the ObjectPresenter for tracker.class.IssueRelation
+  // (models/tracker/src/presenters.ts).
+  builder.createDoc(activity.class.DocUpdateMessageViewlet, core.space.Model, {
+    objectClass: tracker.class.IssueRelation,
+    action: 'create',
+    icon: tracker.icon.Issue,
+    label: tracker.string.AddedRelation,
+    component: tracker.component.RelationActivityPresenter
+  })
+  builder.createDoc(activity.class.DocUpdateMessageViewlet, core.space.Model, {
+    objectClass: tracker.class.IssueRelation,
+    action: 'remove',
+    icon: tracker.icon.Issue,
+    label: tracker.string.RemovedRelation,
+    component: tracker.component.RelationActivityPresenter
+  })
+  builder.createDoc(activity.class.DocUpdateMessageViewlet, core.space.Model, {
+    objectClass: tracker.class.IssueRelation,
+    action: 'update',
+    icon: tracker.icon.Issue,
+    label: tracker.string.UpdatedRelation,
+    component: tracker.component.RelationActivityPresenter
+  })
+
   builder.createDoc(
     activity.class.DocUpdateMessageViewlet,
     core.space.Model,

models/tracker/src/migration.ts

@@ -38,16 +38,20 @@ import { DOMAIN_SPACE } from '@hcengineering/model-core'
 import { DOMAIN_TASK, migrateDefaultStatusesBase } from '@hcengineering/model-task'
 import tags from '@hcengineering/tags'
 import task from '@hcengineering/task'
-import tracker, {
+import {
   type Issue,
+  type IssueRelation,
   type IssueStatus,
   type Project,
   TimeReportDayType,
   trackerId
 } from '@hcengineering/tracker'
+import view, { type ViewOptionModel } from '@hcengineering/view'
 
 import { classicIssueTaskStatuses } from '.'
+import tracker from './plugin'
 import { DOMAIN_TRACKER } from './types'
+import { ganttViewOptions } from './viewlets'
 
 async function createDefaultProject (tx: TxOperations): Promise<void> {
   const current = await tx.findOne(tracker.class.Project, {
@@ -181,6 +185,40 @@ export async function migrateAddStartDate (client: MigrationClient): Promise<voi
   )
 }
 
+// Phase 1 (Visual Polish) adds four new ViewOptions to the IssueGantt
+// viewlet (ganttBarLabelLeft/Inside/Right + ganttQuickInfoOnClick).
+// builder.createDoc is idempotent, so existing workspaces don't pick
+// up the new entries on upgrade-workspace. Re-add the missing ones by
+// merging on `key`, preserving the user's groupBy/orderBy and any
+// already-stored entries. Idempotent — a re-run is a no-op.
+//
+// Mirrors models/card/src/migration.ts:addShowAllVersionsViewOption.
+async function addGanttPhase1ViewOptions (client: MigrationUpgradeClient): Promise<void> {
+  const txOp = new TxOperations(client, core.account.System)
+
+  const viewlets = await client.findAll(view.class.Viewlet, {
+    _id: tracker.viewlet.IssueGantt
+  })
+  if (viewlets.length === 0) return
+
+  const desiredOther = ganttViewOptions().other ?? []
+
+  for (const v of viewlets) {
+    const current = v.viewOptions ?? { groupBy: [], orderBy: [], other: [] }
+    const currentOther: ViewOptionModel[] = current.other ?? []
+    const existingKeys = new Set(currentOther.map((o) => o.key))
+    const missing = desiredOther.filter((o) => !existingKeys.has(o.key))
+    if (missing.length === 0) continue
+
+    await txOp.update(v, {
+      viewOptions: {
+        ...current,
+        other: [...currentOther, ...missing]
+      }
+    })
+  }
+}
+
 async function migrateDefaultStatuses (client: MigrationClient, logger: ModelLogger): Promise<void> {
   const defaultTypeId = tracker.ids.ClassingProjectType
   const typeDescriptor = tracker.descriptors.ProjectType
@@ -375,6 +413,66 @@ async function migrateIssueStatuses (client: MigrationClient): Promise<void> {
   )
 }
 
+/**
+ *  — Activity-Log Remove-Detail Fix.
+ *
+ * Legacy IssueRelation removals went through `ops.removeDoc`, which emits
+ * a bare TxRemoveDoc without parent-issue attachment. The activity
+ * pipeline therefore wrote a DocUpdateMessage whose attachedTo is the
+ * relation itself, never showing up in the issue's activity feed. This
+ * migration re-attaches such DUMs to their parent issue by looking up the
+ * original TxCreateDoc of the now-removed IssueRelation. Best-effort:
+ * when the create-tx is missing (db compaction) the DUM still gets
+ * `updateCollection='relations'` so the activity feed at least shows
+ * "removed dependency" without the target detail.
+ *
+ * Idempotent — once a DUM has Issue-side attachment + `updateCollection`,
+ * the predicate skips it on subsequent runs. The predicate is a local
+ * 4-LOC copy of `isBrokenRelationDum` in
+ * `plugins/tracker-resources/src/components/gantt/lib/relation-activity-migration.ts`
+ * (cannot import across package layers — models/tracker is below
+ * tracker-resources). The helper module is the one with unit tests.
+ */
+async function migrateRelationActivityAttachment (client: MigrationClient): Promise<void> {
+  const issueClass = tracker.class.Issue
+  const dums = await client.find<DocUpdateMessage>(DOMAIN_ACTIVITY, {
+    _class: activity.class.DocUpdateMessage,
+    objectClass: tracker.class.IssueRelation,
+    action: 'remove'
+  })
+  if (dums.length === 0) return
+  for (const dum of dums) {
+    const isBroken = dum.attachedToClass !== issueClass || dum.updateCollection !== 'relations'
+    if (!isBroken) continue
+    // Find the create-tx for this relation. The relation objectId remains
+    // the same across the doc's whole life — that's the key we look up.
+    const createTxes = await client.find<TxCreateDoc<IssueRelation>>(
+      DOMAIN_MODEL_TX,
+      {
+        _class: core.class.TxCreateDoc,
+        objectId: dum.objectId as Ref<IssueRelation>
+      },
+      { limit: 1 }
+    )
+    const createTx = createTxes[0]
+    const patch: Partial<DocUpdateMessage> = {}
+    if (createTx?.attachedTo !== undefined && createTx.attachedToClass !== undefined) {
+      patch.attachedTo = createTx.attachedTo
+      patch.attachedToClass = createTx.attachedToClass
+      patch.updateCollection = createTx.collection ?? 'relations'
+    } else {
+      // Placeholder: ensure the DUM at least shows up in the parent
+      // issue's feed by giving it the collection name; we leave
+      // attachedTo as-is (the runtime DocUpdateMessageObjectValue will
+      // still try buildRemovedDoc with objectId, which often succeeds
+      // even when the create-tx for the *DUM's* attachedTo is gone).
+      if (dum.updateCollection === 'relations') continue
+      patch.updateCollection = 'relations'
+    }
+    await client.update<DocUpdateMessage>(DOMAIN_ACTIVITY, { _id: dum._id }, patch)
+  }
+}
+
 export const trackerOperation: MigrateOperation = {
   async preMigrate (client: MigrationClient, logger: ModelLogger, mode): Promise<void> {
     await tryMigrate(mode, client, trackerId, [
@@ -414,6 +512,22 @@ export const trackerOperation: MigrateOperation = {
         state: 'gantt-add-startdate',
         mode: 'upgrade',
         func: migrateAddStartDate
+      },
+      {
+        // Phase-2 working-days calendar. The property is optional and
+        // additive — every existing Project keeps `workingDaysConfig =
+        // undefined` (legacy calendar-day semantics). The migration entry
+        // exists only so the tracker state-tracker registers the schema
+        // version bump; no data is touched.
+        state: 'gantt-add-working-days-config',
+        mode: 'upgrade',
+        func: async () => {}
+      },
+      {
+        //  — Activity-Log Remove-Detail Fix.
+        state: 'relation-activity-attached-v1',
+        mode: 'upgrade',
+        func: migrateRelationActivityAttachment
       }
     ])
   },
@@ -425,6 +539,10 @@ export const trackerOperation: MigrateOperation = {
           const tx = new TxOperations(client, core.account.System)
           await createDefaults(tx)
         }
+      },
+      {
+        state: 'add-gantt-phase1-view-options',
+        func: addGanttPhase1ViewOptions
       }
     ])
   }

models/tracker/src/plugin.ts

@@ -71,6 +71,7 @@ export default mergeIds(trackerId, tracker, {
     IssueList: '' as Ref<Viewlet>,
     IssueTemplateList: '' as Ref<Viewlet>,
     IssueKanban: '' as Ref<Viewlet>,
+    IssueGantt: '' as Ref<Viewlet>,
     MilestoneList: '' as Ref<Viewlet>,
     ComponentList: '' as Ref<Viewlet>,
     ProjectList: '' as Ref<Viewlet>,

models/tracker/src/presenters.ts

@@ -34,6 +34,15 @@ export function definePresenters (builder: Builder): void {
     presenter: tracker.component.NotificationIssuePresenter
   })
 
+  //
+  // IssueRelation — single-line "FS +Nd → OSTRO-29 Title" presenter so
+  // the activity feed shows which dependency was added or removed
+  // (instead of the generic "Dependency" class label).
+  //
+  builder.mixin(tracker.class.IssueRelation, core.class.Class, view.mixin.ObjectPresenter, {
+    presenter: tracker.component.IssueRelationPresenter
+  })
+
   builder.mixin(tracker.class.Issue, core.class.Class, view.mixin.PreviewPresenter, {
     presenter: tracker.component.IssuePreview
   })

models/tracker/src/types.ts

@@ -74,7 +74,8 @@ import {
   type RelatedIssueTarget,
   type RelatedSpaceRule,
   type TimeReportDayType,
-  type TimeSpendReport
+  type TimeSpendReport,
+  type WorkingDaysConfig
 } from '@hcengineering/tracker'
 import tracker from './plugin'
 import { type TaskType } from '@hcengineering/task'
@@ -137,6 +138,9 @@ export class TProject extends TTaskProject implements Project {
 
   @Prop(Collection(tracker.class.RelatedIssueTarget), tracker.string.RelatedIssues)
     relatedIssueTargets!: number
+
+  @Prop(TypeRecord(), tracker.string.WorkingDaysConfig)
+    workingDaysConfig?: WorkingDaysConfig
 }
 /**
  * @public
@@ -242,6 +246,15 @@ export class TIssue extends TTask implements Issue {
   @Prop(TypeDate(DateRangeMode.DATETIME), tracker.string.DueDate)
   declare dueDate: Timestamp | null
 
+  // Phase 1.B — soft deadline, independent of dueDate. Optional.
+  // When set, the Gantt renders a flag marker at this date and flags the
+  // issue as overdue when dueDate > deadline. Undefined for existing issues
+  // until the user opts in via the Issue editor (Phase 1 ships the
+  // inline ControlPanel field; a Gantt context-menu shortcut is a
+  // separate follow-up, see Out-of-scope section).
+  @Prop(TypeDate(DateRangeMode.DATETIME), tracker.string.Deadline)
+    deadline?: Timestamp | null
+
   @Prop(TypeRef(tracker.class.Milestone), tracker.string.Milestone, { icon: tracker.icon.Milestone })
   @Index(IndexKind.Indexed)
     milestone!: Ref<Milestone> | null
@@ -263,6 +276,19 @@ export class TIssue extends TTask implements Issue {
 
   @Prop(Collection(time.class.ToDo), getEmbeddedLabel('Action Items'))
     todos?: CollectionSize<ToDo>
+
+  /**
+   *  — Auto-Scheduling-Toggle.
+   *
+   * Optional property so existing issues stay on the default cascade
+   * behaviour with no migration. `@Hidden` keeps the field out of the
+   * generic filter/sort UI in `getFiltredKeys`; the dedicated toggle in
+   * `ControlPanel.svelte` is the supported entry point. Cascade-time
+   * checks live in `gantt/lib/scheduler.ts` (Step 5b filter).
+   */
+  @Prop(TypeString(), tracker.string.SchedulingMode)
+  @Hidden()
+    schedulingMode?: 'auto' | 'manual'
 }
 /**
  * @public