Planning in Jira
Jira is the planning source of truth for AeroSim. Use this page to follow the planning process, not to inspect a second copy of the backlog. Current work, priorities, owners, dependencies, decisions and progress belong on the existing Jira issues.
Open the AeroSim Jira board · Find AeroSim issues · Release 2.0.0 work
You need access to the AeroSim (AERS) Jira project. If access is denied, request access from the project administrator; do not create another project or backlog.
1. Select the release and existing work
Filter by Fix Version, then follow the existing Epic → Feature → implementation-item relationships. Preserve the Jira key and any original AeroSim ID. Search before creating an issue: reuse the release-specific records and their linked Tasks or Subtasks rather than duplicating Features or creating a parallel requirements register.
Scope owns the product outcome, acceptance criteria and release scope. Record proposed changes on the relevant issue for its human owner to decide. A release filter or board position is not approval.
2. Make the work executable
On each implementation item, record or link:
- its parent Feature, intended outcome and acceptance criteria;
- the approved design and architecture package, including relevant requirements;
- an assignee or responsible delivery owner;
- the agreed Fix Version and priority;
- blocking dependencies, unresolved questions and their owners;
- exact approval evidence and any conditions on starting work;
- verification steps and the evidence needed for handoff.
Architecture owns solution contracts and dependencies; UI/UX owns design decisions. Keep their decisions attached to the existing Jira work. This guide does not approve scope, design, architecture or implementation.
3. Prioritize and select the next work
Review unfinished work and blockers in Jira. Finish work already underway before opening another delivery wave. Order the next wave by satisfied dependencies and agreed release priority; use available capacity for independent, approved items. Record the selection and any sequencing conditions on those items rather than maintaining a documentation-based wave table.
Reuse existing exact-item approvals. Do not request the same admission again, but do not treat a backlog status, assignment or board position as proof that approval and dependencies are satisfied. A missing decision or dependency stays visible with an owner.
4. Update progress and hand off with evidence
Use the transitions available on the exact Jira issue type. Record a start only when work is actually claimed. Attach the PR, review and exact-revision CI evidence, then the verified development deployment and UAT handoff as work progresses. Keep blocker reasons and next actions on the same issue.
Jira's AERS issue types do not share one status set. A read-only configuration check on 9 November 2026 found READY_FOR_DELIVERY absent; Subtask exposes IN_PROGRESS and TO_BE_RELEASED, while Task uses a different set. Do not invent a Jira transition or equate similarly named statuses. Carry readiness and admission evidence in the issue's description, comments and links, and ask the workflow owner to resolve configuration mismatches without waiving the gates.
Implementation completion is not UAT acceptance or production release approval. UAT records its verdict against the exact deployed revision; Releases owns authorized promotion and final closure. Preserve rejected results, conditions and prior decisions instead of overwriting them with a later success.
Keep one planning record
Update Jira, not a copy of Board, Focus or a release task list in these docs. Agent execution tracking may link to the original Jira issue, but must not become another product backlog or an independent approval source. Link execution evidence back to that issue.
The former Kanban pages now lead here. Their historical text remains in Git history; existing source records and evidence are not deleted or reclassified by this documentation change. This page does not certify migration completeness or alter Jira workflows, issue states, permissions, approvals or historical release acceptance.