Skip to content

Releases

0.3.0

Choose a tag to compare

@github-actions github-actions released this 18 Nov 06:59

What's new

  • Connect to Jira Data Center/Server with its REST API v2, Bearer personal access tokens, company-hosted Jira URLs, and optional proxy base paths such as /jira.
  • Forecast Data Center epics through the Epic Link field and read issue status history from expanded changelogs. Cloud REST API v3 remains supported.
  • Test the configured project's issue search and changelog access directly. Proxy authentication and HTML SSO responses now produce clearer errors without displaying response contents.
  • Store Jira tokens in Obsidian SecretStorage. Existing tokens in plugin settings migrate on load; only the secret name remains in plugin data.
  • Read epic timelines more easily with distinct P80 milestone markers, a today guide, and clearer environment date cards. Private calendar feed URLs are no longer included in connection errors.

Upgrade notes

Choose Data center / server in Path to Prod settings if automatic detection does not match your company's Jira URL. Leave the email field blank for a Data Center personal access token. Obsidian 1.13.0 or later is required. Older backups of the plugin's data.json may still contain a token from previous releases; handle those copies under your company's credential policy.

If Jira truncates an expanded Data Center changelog, Path to Prod stops instead of calculating from incomplete history. The Data Center path has automated tests but has not been verified against your company's live Jira instance.

0.2.1

Choose a tag to compare

@github-actions github-actions released this 17 Nov 19:41
  • Add an optional Ko-fi support link to the Obsidian plugin listing and GitHub repository.

0.2.0

Choose a tag to compare

@github-actions github-actions released this 17 Nov 06:23
  • Forecast Jira epics from their child tickets and an adjustable reserve for unrefined work.
  • Show each epic in a color-coded development, staging, and production Gantt timeline with P50, P80, and P95 dates.
  • Label the timeline with ISO week numbers and clear P80 dates for every environment.
  • Flag important epics and tickets manually or through configurable Jira priorities and labels, then watch their epic forecast against Jira due dates or Scrum sprint targets.
  • Adjust sprint length and important-work targets from the dashboard.
  • Copy an email-ready forecast with colored stage cells and a plain-text fallback, or open an email draft with a suggested subject.
  • Document that each epic assumes full team capacity independently and ticket alerts use their parent epic forecast as a scope-level signal.

0.1.4

Choose a tag to compare

@github-actions github-actions released this 16 Nov 15:01

Full Changelog: 0.1.3...0.1.4

0.1.3

Choose a tag to compare

@github-actions github-actions released this 16 Nov 14:54

Full Changelog: 0.1.2...0.1.3

0.1.2

Choose a tag to compare

@github-actions github-actions released this 16 Nov 14:52

Full Changelog: 0.1.1...0.1.2

0.1.1

Choose a tag to compare

@github-actions github-actions released this 16 Nov 12:21

Full Changelog: 0.1.0...0.1.1

0.1.0

Choose a tag to compare

@alex3l3t33 alex3l3t33 released this 16 Nov 12:09

Initial public release of Path to Prod. Forecast development, staging, and production milestones from Jira history, team capacity, Scrum or Kanban flow, holidays, and crew availability.