Skip to main content
Version: Next

Changelog

Release 1.2.0 · Forge 3.4.0​

Minor release over 1.1.2 (Forge 3.3.0). Six visible changes. Licensing, sandbox, Blocks dependencies, saved plans, and the language of save errors do not change.

✨ New features

  • Native Parent fallback: if Parent Element is empty, the Gantt nests with Jira's native Parent. If the field has a value, that value wins. Stratify does not fill the field automatically. If the parent type is not allowed or the parent is not in the plan JQL, the work item goes to No parent.
  • Sub-tasks: sub-task types can be included in the hierarchy as children and appear in the Gantt under their native Parent. They cannot have children. Their ⋯ menu does not show the Parent Element picker. Effort and date roll-ups include them.
  • Parent Element picker: search by key or summary, recent or suggested results, and clearing the value. In the field, each option shows KEY: summary (Type). In the Gantt, the type icon, key, and summary, grouped by sections. Only parent types allowed by the hierarchy appear.
  • Work item preview: the row key or a click on the bar without dragging opens the details inside the Gantt, with real data. It closes with Close or Escape and does not block plan editing. It does not show budget or cost.

🔧 Behaviour changes

  • Space: the UI says Space / Espacio in the Gantt grouping, the group with no space, and the messages shown when creating a work item. The example JQL still uses project.
  • Sub-tasks and Parent Element: a sub-task is not reassigned with Parent Element; it always hangs from its Jira native Parent.

🛠 Fixes

  • Theme: Stratify follows Jira's light or dark theme in Command Center, the Gantt, dialogs, filters, the preview, the hierarchy admin, and the Parent Element field. The light theme does not change. The Review changes count badge is readable in dark mode.

📝 Technical notes (public)

  • Direct upgrade from 3.3.0 (1.1.2). No migration. The hierarchy, plans, and existing drafts are preserved.
  • Without an active license, features remain blocked, as in 1.1.2.
  • Team capacity, budget, and objectives remain outside the app.
  • Sub-tasks only appear after their type is included in the hierarchy and the plan JQL returns them.

Release 1.1.2 · Forge 3.3.0​

Gantt save error notices follow the site language. No new features: hierarchy, licensing, sandbox, roll-ups, Blocks, saved plans, and Gantt fields do not change.

🔧 Fixes

  • Gantt save: if a change cannot be saved, the failure reason is shown in es-ES or en-US, according to the site language. The notice for a non-editable end date (or start date) field includes the work item key and points to Gantt Settings or the work item type screen.

Release 1.1.1 · Forge 3.2.0​

Command Center UI fixes in the Gantt. No new features: hierarchy, licensing, sandbox, roll-ups, Blocks, and language do not change.

🔧 Fixes

  • Fields: the Gantt fields menu is fully visible. The search box and the field names (Status, Assignee, and the rest) are no longer clipped.
  • Review changes: the dialog opens inside the Gantt. The dimmed backdrop no longer blocks the screen: close it with Escape or by clicking the backdrop.

Release 1.1.0 · Forge 3.0.0​

First version ready for the Marketplace. Stratify for Jira is now a paid app.

✨ New features

  • Hierarchy panel: define levels and containers (OKR, SAFe, or another site model) with Parent → Children rules.
  • Parent Element: the picker only offers parents allowed by that hierarchy.
  • Gantt in Command Center: nesting, Blocks dependencies, date and estimate roll-up, and conflict alerts.
  • Sandbox (Draft): edit on the Gantt, keep the draft, and sync to Jira when the plan is ready.
  • Language: Spanish and English UI according to the Jira locale.
  • Paid app: without an active license, Command Center, the hierarchy panel, the Parent Element field, and the Gantt are blocked. A Marketplace evaluation counts as an active license. The license covers the whole app.

🔧 Fixes

  • Sandbox persistence and save: each plan’s draft is restored after a reload. On sync, only changes Jira accepted are cleared. Blocks and is blocked by are saved in the direction you chose. A finished child counts as complete in progress, and the ghost bar shows the original Jira dates without repeating the percentage.

Documentation 1.0.0 (Forge 2.0.0) already described Gantt planning. This release adds Marketplace licensing and the draft adjustments. Team capacity, budget, and real objectives remain outside the app.

Release 1.0.0 · Forge 2.0.0​

First public release of Stratify for Jira: a configurable hierarchy and Gantt planning, with a sandbox before writing to Jira.

✨ New features

  • Configurable hierarchy: Parent Element / Elemento Superior field and Parent → Children admin panel (a type tree, not a linear list).
  • Multi-project Gantt: one JQL feeds bars from several projects (according to permissions), with zoom/pan, start and end dates, and saved plans.
  • Nesting: bars group according to the hierarchy and the Parent Element field; levels can be expanded and collapsed. Issues without a parent in the view are grouped explicitly.
  • Sandbox (Draft): dragging, stretching, or editing dates does not write to Jira until Sync. You can discard the draft.
  • Bulk sync: send every draft change to Jira, with a per-issue summary. On partial failure, successful drafts are cleared and failed drafts are kept with the error.
  • Estimate roll-up: each parent shows the sum of Story Points or hours of visible children.
  • Optional date roll-up: toggle (off by default) that extends the parent in Draft when a child slips past its finish date.
  • Blocks dependencies: Blocks / is blocked by arrows and red visual alerts if a blocked task sits before its blocker. The alert does not block save or sync.
  • Language: UI in es-ES (default) and en-US, according to the Jira locale.

🔧 Scope of this version

  • First install on Jira Cloud (Forge). After install, associate the Parent Element field with screens and configure the hierarchy.
  • Does not include team capacity, budget, or real objectives. Those features do not appear in the app.
  • Compatible with Jira Cloud. Requires JQL read permission and date-edit permission to sync.
Last updated on