Release notes and known limitations

Current documentation version#

This portal documents the repository at application version label v2.0.0. The documentation branch was reconciled with production-RBAC baseline d6d65c1 before shipping.

The repository does not define a formal semantic-version release process or public changelog. The version in the application sidebar and the older README-v2.md are the available product-version signals.

Verified v2 capabilities#

• Taiga and Jira connection setup.
• Dry-run-first organization settings.
• Cycle selection and on-demand runs.
• Run history, cycle summaries, action logs, and exports.
• Approvals, run confirmation, and execution gates.
• Trends and project comparisons.
• CSV or Markdown backlog import.
• Guided epic, story, and task creation.
• Backlog proposal decisions.
• Schedule preference storage.
• Stripe checkout and customer portal integration.
• Installable web application assets.
• Self-hosting templates for Docker, Railway, and Fly.io.
• Server-enforced Admin, Manager, Scrum Master, Product Manager, and read-only Member roles.
• Administrator-managed operational roles and delegated permissions under Settings → Access & Roles.

Known limitations#

• Production Clerk activation and role-management smoke testing still require the approved production domain, DNS, and provider configuration.
• Clerk password, MFA, invitation, and session behavior is deployment-controlled and not documented in code.
• Dashboard schedule preferences do not by themselves prove a durable external schedule.
• The public and signed-in billing screens contain conflicting price copy.
• The n8n workflow is an unvalidated import artifact and needs security hardening.
• The migration documentation contains a stale statement about Alembic revisions.
• Support, service status, browser policy, accessibility conformance, and several legal policies are not approved.
• The observed hosted API reports environment: development in readiness output.

Maintaining release notes#

For each customer-visible release, add the date, version or commit, added behavior, changed behavior, fixed defects, migration needs, deprecations, and known issues. Do not mark a deployment complete until CI, provider status, and smoke checks reach terminal success.