Skip to content

Add SCHEDULED and DEADLINE timestamps to org entries - #19

Open
bobrowadam wants to merge 2 commits into
anegg0:mainfrom
bobrowadam:feature/scheduled-deadline-timestamps
Open

Add SCHEDULED and DEADLINE timestamps to org entries#19
bobrowadam wants to merge 2 commits into
anegg0:mainfrom
bobrowadam:feature/scheduled-deadline-timestamps

Conversation

@bobrowadam

@bobrowadam bobrowadam commented Jan 3, 2026

Copy link
Copy Markdown

Summary

Adds org-mode SCHEDULED and DEADLINE timestamps to issue entries so they appear in org-agenda views.

  • DEADLINE: Uses cycle end date (cycle.endsAt) - shows when work should be completed
  • SCHEDULED: Uses startedAt, or today's date as fallback for backlog items - ensures all issues appear in agenda

Without timestamps, Linear issues don't appear in org-agenda. This change ensures all synced issues are visible in daily/weekly agenda views, making it easier to track Linear work alongside other org tasks.

Changes

  • Extended GraphQL queries with dueDate, startedAt, createdAt, and cycle fields
  • Added linear-emacs--format-date-as-org helper for date conversion
  • Modified org entry formatter to include planning line in standard org format

@bobrowadam
bobrowadam force-pushed the feature/scheduled-deadline-timestamps branch from 033d83f to 1e8e5d5 Compare January 3, 2026 18:35
- Add cycle, startedAt, createdAt, dueDate to GraphQL queries
- Use cycle.endsAt as DEADLINE for issues in a cycle
- Use startedAt as SCHEDULED, fallback to today for backlog items
- Format planning line correctly for org-agenda compatibility
@bobrowadam
bobrowadam force-pushed the feature/scheduled-deadline-timestamps branch from 1e8e5d5 to 3d1b3f2 Compare January 3, 2026 18:37
- Update default state mapping to use basic org keywords:
  Todo/Backlog -> TODO, In Progress -> NEXT,
  In Review/Blocked -> WAITING, Done -> DONE
- Fix file header: move #+keywords outside PROPERTIES drawer
- Fix property extraction to use org APIs (org-entry-get, org-get-todo-state)
- Fix description to be single-line (org properties requirement)
- Add forward-line to prevent infinite loop in sync
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant