Schema-only foundation for the upcoming Gantt-chart view in tracker.
No UI in this PR.
Changes:
- Issue.startDate: Timestamp | null (interface + IssueDraft + @Prop with @Index)
- Milestone.startDate: Timestamp | null (interface + @Prop, reusing the
existing tracker.string.StartDate IntlString)
- New DependencyKind type ('finish-to-start' | 'start-to-start' |
'finish-to-finish' | 'start-to-finish')
- New IssueRelation AttachedDoc class with kind: DependencyKind, signed
lag: number — registered in models/tracker via TIssueRelation
- 7 new IntlString keys: IssueStartDate, GanttDependency,
GanttDependency{FinishToStart,StartToStart,FinishToFinish,StartToFinish},
GanttLag — all 13 locales updated
- Cross-plugin literal updates in importer + github sync to satisfy the new
required Issue.startDate / Milestone.startDate fields:
- packages/importer/src/importer/importer.ts: AttachedData<Issue> literal
- services/github/pod-github/src/sync/issueBase.ts: 'startDate' added to
GithubIssueData Omit list (github sync does not own scheduling)
- services/github/pod-github/src/sync/issues.ts + pullrequests.ts:
AttachedData<Issue|GithubPullRequest> literals
Out of scope (deferred to follow-up PRs):
- UI for Gantt view, drag/resize, dependency editor, critical path
- blockedBy → IssueRelation migration (ships atomically with the writer
redirect in the dependency-UI PR)
- LinkIssues permission (tracker uses forbid-style permissions; needs
maintainer discussion)
- Activity-feed wiring for IssueRelation (needs a producer to test against)
- IssueTemplate.startDate (template propagation semantics undecided)
Signed-off-by: Michael Uray <michaeluray@users.noreply.github.com>
* add readonly support to MarkupEditor and improve hierarchy-based attribute resolution and locking logic
Signed-off-by: Denis Bykhov <bykhov.denis@gmail.com>
* perf: implement caching for card lookups in process-resources functions
Signed-off-by: Denis Bykhov <bykhov.denis@gmail.com>
* refactor: update TagSelector to use tag IDs in selection set and optimize hierarchy access
Signed-off-by: Denis Bykhov <bykhov.denis@gmail.com>
---------
Signed-off-by: Denis Bykhov <bykhov.denis@gmail.com>
* Do not set migration state in case of mode mismatch and add duration
Signed-off-by: Artem Savchenko <armisav@gmail.com>
* Bump model version
Signed-off-by: Artem Savchenko <armisav@gmail.com>
---------
Signed-off-by: Artem Savchenko <armisav@gmail.com>
* Exclude guests from space owners
Signed-off-by: Artem Savchenko <armisav@gmail.com>
* Show guest if he is in owners
Signed-off-by: Artem Savchenko <armisav@gmail.com>
---------
Signed-off-by: Artem Savchenko <armisav@gmail.com>
The check_model_version.js CI step was commented out, which allowed
v0.7.413 to ship with MODEL_VERSION=0.7.343 baked into the desktop
client. This causes a blocking "New version is available" dialog for
self-hosted users whose servers have MODEL_VERSION > 0.7.343.
Re-enabling this check will catch future model/version.txt drift
before it reaches a release.
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Michael Uray