KINDA · weekend project
price $7.91/moyou'd save $94.92/yrbuild time multi-daycategory 🗂️ project managementreplaced by 0 people
Issues, workflows, a backlog, sprints, and a board are a credible multi-day build for one small team. The replacement stops being small when Jira is the company's system of record: custom schemes, permissions, automation, reporting, marketplace apps, two-way integrations, and years of workflow history are the product people are actually paying not to migrate.
the project pack5 files · written for this build, step by step
You are building a lean indie version of Jira. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Jira · indie build Build a focused issue backlog with explicit workflow transitions and sprint history. Estimated effort: **multi-day**. Work `BUILD_PLAN.md` top to bottom · every phase ends in a check that has to pass before the next one starts. ## Stack | Part | Choice | Why | | --- | --- | --- | | Runtime | Python 3.12+ and Flask | A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. | | Storage | SQLite through Python sqlite3 | Local ownership with explicit transactions and a portable backup path. | | Interface | Jinja HTML templates, CSS and vanilla JavaScript | Implement the specified screens directly with labelled controls and progressive enhancement. | | Verification | Python unittest and browser acceptance fixtures | Check invariants and the actual user workflow before the next phase. | ## Before you start Have every one of these ready. The plan assumes them from step one. - [ ] **Python 3.12 or newer and a terminal** · Python is free; this local prototype requires no hosting subscription. - Why: The local backend, tests and storage use Python. - Get it: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. - Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. - [ ] **A current desktop browser and text editor** · No paid service required for this local step. - Why: You need to view the local interface and edit generated project files. - Get it: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. - Verify: You can create a text file in the project folder and open browser developer tools. - [ ] **Jira acceptance sample** · No paid service required for this local step. - Why: This fixture makes the first end-to-end check reproducible. - Get it: Create synthetic sample data before implementation: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. - Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. - [ ] **Confirm the bounded replacement** · No paid service required for this local step. - Why: The full commercial product is larger than this guide. - Get it: The deliverable is a focused issue backlog with explicit workflow transitions and sprint history. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. - Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. ## Quick start ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` Then copy `.env.example` to `.env` and fill in the values it documents. ## Honest limits This build deliberately does not replace: - This is a focused issue backlog with explicit workflow transitions and sprint history; full Jira feature parity, vendor hosting and support are not included. - the Atlassian Marketplace and its long tail of organization-specific apps - deep two-way integrations with source control, chat, support, and CI systems - advanced roadmaps, reporting, automation, and cross-project dependency planning - enterprise identity, permissions, audit, data residency, and support guarantees - migration fidelity for years of custom fields, workflows, links, and issue history If one of those is essential to you, that is the reason to keep paying for Jira, and the README should say so rather than pretend. ===== BRIEF.md ===== # Build brief · Jira The one-shot brief this plan expands. `BUILD_PLAN.md` (or `MILESTONES.md`) is the same sequence broken into steps and checks; where the two disagree, the plan wins. Build me a focused issue backlog with explicit workflow transitions and sprint history as a bounded replacement for Jira. Build it in phases in the order below. Do not write the whole product in one pass. Finish the current phase, run its Done when checks, fix failures, then continue. Indie mode completes Phases 1-5. Phase 6 is required before shared or public deployment. ### Stack (fixed, do not substitute) - Runtime: Python 3.12+ and Flask. A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. - Storage: SQLite through Python sqlite3. Local ownership with explicit transactions and a portable backup path. - Interface: Jinja HTML templates, CSS and vanilla JavaScript. Implement the specified screens directly with labelled controls and progressive enhancement. - Verification: Python unittest and browser acceptance fixtures. Check invariants and the actual user workflow before the next phase. ### Data model (create this before Phase 1) - projects(id,key) - issues(id,project_id,number,title,type,status,estimate,sprint_id,revision) - transitions(from_status,to_status) - sprints(id,project_id,start,end,state) - events(id,issue_id,at,kind,payload) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. ### Prerequisites and configuration - Python 3.12 or newer and a terminal: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. Cost: Python is free; this local prototype requires no hosting subscription. - A current desktop browser and text editor: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. Verify: You can create a text file in the project folder and open browser developer tools. Cost: No paid service required for this local step. - Jira acceptance sample: Create synthetic sample data before implementation: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. Cost: No paid service required for this local step. - Confirm the bounded replacement: The deliverable is a focused issue backlog with explicit workflow transitions and sprint history. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. Cost: No paid service required for this local step. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL. Ship .env.example, replace placeholders and exclude secrets from git. ### Phase 1 · Local foundation and data contract Build: Create the runnable local foundation for a focused issue backlog with explicit workflow transitions and sprint history, including the real schema and acceptance fixture. - Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Commands, after creating the named files: `python -m venv .venv`; `python -m pip install Flask Flask-WTF python-dotenv waitress tzdata`; `python -m pip freeze > requirements.txt`; `python -m flask --app app run --host 127.0.0.1`. - For database-backed state create schema.sql and db.py using this model: projects(id,key); issues(id,project_id,number,title,type,status,estimate,sprint_id,revision); transitions(from_status,to_status); sprints(id,project_id,start,end,state); events(id,issue_id,at,kind,payload). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Re-running init must not erase data. Commands, after creating the named files: `python manage.py init`; `python manage.py seed`. - Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. - Trap: The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. Done when: The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. Restarting preserves the seeded records or canonical files; running init again deletes nothing. A cross-origin state-changing request to an admin route is refused. Do not build yet: Do not start issue keys and workflow until these checks pass. ### Phase 2 · Issue keys and workflow Build: Issue keys and workflow for Jira: Allocate monotonically increasing issue numbers per project in a transaction; support bug, story and task types. - Allocate monotonically increasing issue numbers per project in a transaction; support bug, story and task types. - Define allowed transitions as data and validate them server-side; record status events with the old and new value. - Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Two concurrent creates receive distinct APP keys. Then check: A forbidden transition returns a reason and leaves status unchanged. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Never derive issue numbers from the current row count. Done when: Two concurrent creates receive distinct APP keys. A forbidden transition returns a reason and leaves status unchanged. Do not build yet: Do not start backlog and sprint commitment until these checks pass. ### Phase 3 · Backlog and sprint commitment Build: Backlog and sprint commitment for Jira: Order backlog issues and move selected ids into a sprint with a start/end date; snapshot committed estimates when starting. - Order backlog issues and move selected ids into a sprint with a start/end date; snapshot committed estimates when starting. - Render a sprint board and record scope added or removed after start without rewriting the original commitment. - Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Adding a five-point issue mid-sprint appears as scope added, not original commitment. Then check: An issue cannot belong to two active sprints. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Current estimates cannot reconstruct historical sprint scope. Done when: Adding a five-point issue mid-sprint appears as scope added, not original commitment. An issue cannot belong to two active sprints. Do not build yet: Do not start close and report until these checks pass. ### Phase 4 · Close and report Build: Close and report for Jira: Close a sprint with an explicit choice to return unfinished issues to backlog or move them to a named future sprint. - Close a sprint with an explicit choice to return unfinished issues to backlog or move them to a named future sprint. - Compute completion and daily remaining points from dated events; label this a simple project report. - Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Closing moves unfinished work exactly once and preserves completed issue history. Then check: A reopened issue increases remaining work on its reopen day. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Velocity is a team planning measure; do not turn it into an individual performance score. Done when: Closing moves unfinished work exactly once and preserves completed issue history. A reopened issue increases remaining work on its reopen day. Do not build yet: Do not start portable delivery and clean-start proof until these checks pass. ### Phase 5 · Portable delivery and clean-start proof Build: Finish the Jira replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Issue keys and workflow; Backlog and sprint commitment; Close and report. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. - Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for jira. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. - Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Commands, after creating the named files: `python -m pip install -r requirements.txt`; `python -m unittest discover -s test`. - Trap: Export without an import or restore rehearsal is not verified portability. Done when: A new folder reaches the documented fixture outcome using only README instructions. A backup restored in isolation preserves the proof data and can be opened. Do not build yet: Do not start operate and share with access controls until these checks pass. ### Phase 6 · Operate and share with access controls (product-builder only) Build: Product-builder only: make a focused issue backlog with explicit workflow transitions and sprint history operable for its stated audience before allowing remote access. - Add owner/member/viewer authorization as appropriate, password hashes through Werkzeug, expiring server-side sessions, CSRF and login rate limits. Add users, sessions and audit schema migrations plus an owner-init command prompting securely for its password. Enforce ownership on every private read/write/download and fail closed when product setup is incomplete. Existing learner or admin identities must use this same boundary. - Serve app:app with Waitress on loopback behind Caddy HTTPS. Configure trusted proxy headers narrowly, Secure/HttpOnly/SameSite cookies, upload limits, request ids and structured logs without private content. Run background jobs as a separate supervised process when the domain workflow requires them. Commands, after creating the named files: `waitress-serve --listen=127.0.0.1:5000 app:app`. - Add a scheduled encrypted off-host backup using this procedure: Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for jira. Monitor health, disk space, failed jobs and backup age. Stop the service to test an alert; rehearse recovery with outbound effects disabled and record recovery time. Rotate any exposed credentials and require reconciliation before resuming queues. - Trap: Product mode is additional engineering, not a switch that makes a local prototype production-ready. Done when: An unauthenticated visitor cannot read private records, download private files or mutate the admin surface. A viewer cannot mutate data by making a direct request, and guessed ids cannot cross ownership boundaries. Stopping the service triggers the configured alert and the latest off-host backup restores the fixture in isolation. Do not build yet: Do not add new providers or vendor-scale features until the release gates are recorded. ### Out of scope (and why) - This is a focused issue backlog with explicit workflow transitions and sprint history; full Jira feature parity, vendor hosting and support are not included. - the Atlassian Marketplace and its long tail of organization-specific apps: retain the paid product if this capability is essential; it is outside this bounded build. - deep two-way integrations with source control, chat, support, and CI systems: retain the paid product if this capability is essential; it is outside this bounded build. - advanced roadmaps, reporting, automation, and cross-project dependency planning: retain the paid product if this capability is essential; it is outside this bounded build. - enterprise identity, permissions, audit, data residency, and support guarantees: retain the paid product if this capability is essential; it is outside this bounded build. - migration fidelity for years of custom fields, workflows, links, and issue history: retain the paid product if this capability is essential; it is outside this bounded build. ### README must contain - Exact install, configure, initialize, start, test and recovery commands for a clean folder. - The schema, fixture, acceptance results, private data locations and export format. - Every prerequisite and secret source, actual running costs and deliberately excluded capabilities. - An honest distinction between tests actually run and checks still awaiting real credentials or deployment. - Dependency documentation reviewed 2026-09-05: https://flask.palletsprojects.com/en/stable/installation/ ; https://docs.python.org/3/library/sqlite3.html ; https://flask-wtf.readthedocs.io/en/1.2.x/csrf/ ; https://docs.pylonsproject.org/projects/waitress/en/stable/usage.html. Recheck before upgrading; freeze the versions actually tested. ===== AGENTS.md ===== # Agent instructions · Jira indie build - Read `README.md` and `BUILD_PLAN.md` before writing code. The stack is fixed: Python 3.12+ and Flask, SQLite through Python sqlite3, Jinja HTML templates, CSS and vanilla JavaScript, Python unittest and browser acceptance fixtures. Do not substitute. - Work one phase at a time, in order. Do not start a phase until every "Done when" item of the previous one passes. - Prefer the fewest moving parts that satisfy the step. No frameworks, services or dependencies the plan does not name. - Secrets live in `.env`, never in source or logs. Keep `.env.example` current when a variable is introduced. - Do not invent cryptography, security guarantees, APIs or compliance claims. - Add a focused test for every destructive, security-sensitive or data-loss path the plan names. - Run the project checks before declaring a phase complete, and record any deliberate shortcut in the README under "Tradeoffs". ## Known traps - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. - Never derive issue numbers from the current row count. - Current estimates cannot reconstruct historical sprint scope. - Velocity is a team planning measure; do not turn it into an individual performance score. - Export without an import or restore rehearsal is not verified portability. ===== BUILD_PLAN.md ===== # Build plan · Jira Build a focused issue backlog with explicit workflow transitions and sprint history. Phases are in dependency order. Each ends in a "Done when" list; treat an unticked item as a blocker, not a note. ## Phase 1 · Local foundation and data contract Create the runnable local foundation for a focused issue backlog with explicit workflow transitions and sprint history, including the real schema and acceptance fixture. ### Steps 1. Create and start the local application Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Files: `app.py`, `requirements.txt`, `.env.example`, `.gitignore` ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` 2. Implement storage and seed the named fixture For database-backed state create schema.sql and db.py using this model: projects(id,key); issues(id,project_id,number,title,type,status,estimate,sprint_id,revision); transitions(from_status,to_status); sprints(id,project_id,start,end,state); events(id,issue_id,at,kind,payload). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Re-running init must not erase data. Files: `schema.sql`, `db.py`, `manage.py`, `fixtures/README.md` ```sh python manage.py init python manage.py seed ``` 3. Protect the local request boundary Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. Files: `app.py`, `templates/base.html`, `test/test_foundation.py` ### Done when - [ ] The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. - [ ] Restarting preserves the seeded records or canonical files; running init again deletes nothing. - [ ] A cross-origin state-changing request to an admin route is refused. ### Watch out - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. ## Phase 2 · Issue keys and workflow Issue keys and workflow for Jira: Allocate monotonically increasing issue numbers per project in a transaction; support bug, story and task types. ### Steps 1. Allocate monotonically increasing issue numbers per project in a transaction; support bug, story and task types. Allocate monotonically increasing issue numbers per project in a transaction; support bug, story and task types. Files: `features/issue_keys_and_workflow.py`, `templates/issue_keys_and_workflow.html` 2. Define allowed transitions as data and validate them server-side; record status events with the old and new value. Define allowed transitions as data and validate them server-side; record status events with the old and new value. Files: `features/issue_keys_and_workflow.py` 3. Exercise the acceptance fixture Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Two concurrent creates receive distinct APP keys. Then check: A forbidden transition returns a reason and leaves status unchanged. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_issue_keys_and_workflow.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Two concurrent creates receive distinct APP keys. - [ ] A forbidden transition returns a reason and leaves status unchanged. ### Watch out - Never derive issue numbers from the current row count. ## Phase 3 · Backlog and sprint commitment Backlog and sprint commitment for Jira: Order backlog issues and move selected ids into a sprint with a start/end date; snapshot committed estimates when starting. ### Steps 1. Order backlog issues and move selected ids into a sprint with a start/end date; snapshot committed estimates when starting. Order backlog issues and move selected ids into a sprint with a start/end date; snapshot committed estimates when starting. Files: `features/backlog_and_sprint_commitment.py`, `templates/backlog_and_sprint_commitment.html` 2. Render a sprint board and record scope added or removed after start without rewriting the original commitment. Render a sprint board and record scope added or removed after start without rewriting the original commitment. Files: `features/backlog_and_sprint_commitment.py` 3. Exercise the acceptance fixture Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Adding a five-point issue mid-sprint appears as scope added, not original commitment. Then check: An issue cannot belong to two active sprints. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_backlog_and_sprint_commitment.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Adding a five-point issue mid-sprint appears as scope added, not original commitment. - [ ] An issue cannot belong to two active sprints. ### Watch out - Current estimates cannot reconstruct historical sprint scope. ## Phase 4 · Close and report Close and report for Jira: Close a sprint with an explicit choice to return unfinished issues to backlog or move them to a named future sprint. ### Steps 1. Close a sprint with an explicit choice to return unfinished issues to backlog or move them to a named future sprint. Close a sprint with an explicit choice to return unfinished issues to backlog or move them to a named future sprint. Files: `features/close_and_report.py`, `templates/close_and_report.html` 2. Compute completion and daily remaining points from dated events; label this a simple project report. Compute completion and daily remaining points from dated events; label this a simple project report. Files: `features/close_and_report.py` 3. Exercise the acceptance fixture Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Closing moves unfinished work exactly once and preserves completed issue history. Then check: A reopened issue increases remaining work on its reopen day. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_close_and_report.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Closing moves unfinished work exactly once and preserves completed issue history. - [ ] A reopened issue increases remaining work on its reopen day. ### Watch out - Velocity is a team planning measure; do not turn it into an individual performance score. ## Phase 5 · Portable delivery and clean-start proof Finish the Jira replacement with a documented first-run path and a recoverable export. ### Steps 1. Write the user-facing runbook Document prerequisites, every configuration variable, data locations and the three domain workflows: Issue keys and workflow; Backlog and sprint commitment; Close and report. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. Files: `README.md`, `.env.example` 2. Create and rehearse a recoverable backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for jira. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. Files: `OPERATIONS.md`, `scripts/backup.py` 3. Reproduce the first-run experience Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Files: `README.md`, `verification.md` ```sh python -m pip install -r requirements.txt python -m unittest discover -s test ``` ### Done when - [ ] A new folder reaches the documented fixture outcome using only README instructions. - [ ] A backup restored in isolation preserves the proof data and can be opened. ### Watch out - Export without an import or restore rehearsal is not verified portability. ## Not in this build - This is a focused issue backlog with explicit workflow transitions and sprint history; full Jira feature parity, vendor hosting and support are not included. - the Atlassian Marketplace and its long tail of organization-specific apps - deep two-way integrations with source control, chat, support, and CI systems - advanced roadmaps, reporting, automation, and cross-project dependency planning - enterprise identity, permissions, audit, data residency, and support guarantees - migration fidelity for years of custom fields, workflows, links, and issue history ## After v1, if you want it - Extend close and report only after the fixture and recovery checks pass. - Before adding another integration, document its credentials, limits, cost and failure behavior with primary-source links. ===== .env.example ===== # Copy to .env and fill in. Never commit .env; this file documents it. # Required. A new private folder this application creates on first run; never serve it as static files. DATA_DIR=./data/jira # Required · secret. Generate with python -c "import secrets; print(secrets.token_hex(32))" and save only in .env. SECRET_KEY=replace-with-a-random-secret # Required. Use indie for loopback-only personal work. Product mode must refuse to start until owner login and the deployment gates are configured. APP_MODE=indie # Required. The origin used for local forms and links; replace with the chosen HTTPS origin in product mode. SITE_URL=http://127.0.0.1:5000
You are building a lean indie version of Jira. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Jira · indie build Build a focused issue backlog with explicit workflow transitions and sprint history. Estimated effort: **multi-day**. Work `BUILD_PLAN.md` top to bottom · every phase ends in a check that has to pass before the next one starts. ## Stack | Part | Choice | Why | | --- | --- | --- | | Runtime | Python 3.12+ and Flask | A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. | | Storage | SQLite through Python sqlite3 | Local ownership with explicit transactions and a portable backup path. | | Interface | Jinja HTML templates, CSS and vanilla JavaScript | Implement the specified screens directly with labelled controls and progressive enhancement. | | Verification | Python unittest and browser acceptance fixtures | Check invariants and the actual user workflow before the next phase. | ## Before you start Have every one of these ready. The plan assumes them from step one. - [ ] **Python 3.12 or newer and a terminal** · Python is free; this local prototype requires no hosting subscription. - Why: The local backend, tests and storage use Python. - Get it: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. - Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. - [ ] **A current desktop browser and text editor** · No paid service required for this local step. - Why: You need to view the local interface and edit generated project files. - Get it: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. - Verify: You can create a text file in the project folder and open browser developer tools. - [ ] **Jira acceptance sample** · No paid service required for this local step. - Why: This fixture makes the first end-to-end check reproducible. - Get it: Create synthetic sample data before implementation: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. - Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. - [ ] **Confirm the bounded replacement** · No paid service required for this local step. - Why: The full commercial product is larger than this guide. - Get it: The deliverable is a focused issue backlog with explicit workflow transitions and sprint history. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. - Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. ## Quick start ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` Then copy `.env.example` to `.env` and fill in the values it documents. ## Honest limits This build deliberately does not replace: - This is a focused issue backlog with explicit workflow transitions and sprint history; full Jira feature parity, vendor hosting and support are not included. - the Atlassian Marketplace and its long tail of organization-specific apps - deep two-way integrations with source control, chat, support, and CI systems - advanced roadmaps, reporting, automation, and cross-project dependency planning - enterprise identity, permissions, audit, data residency, and support guarantees - migration fidelity for years of custom fields, workflows, links, and issue history If one of those is essential to you, that is the reason to keep paying for Jira, and the README should say so rather than pretend. ===== BRIEF.md ===== # Build brief · Jira The one-shot brief this plan expands. `BUILD_PLAN.md` (or `MILESTONES.md`) is the same sequence broken into steps and checks; where the two disagree, the plan wins. Build me a focused issue backlog with explicit workflow transitions and sprint history as a bounded replacement for Jira. Build it in phases in the order below. Do not write the whole product in one pass. Finish the current phase, run its Done when checks, fix failures, then continue. Indie mode completes Phases 1-5. Phase 6 is required before shared or public deployment. ### Stack (fixed, do not substitute) - Runtime: Python 3.12+ and Flask. A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. - Storage: SQLite through Python sqlite3. Local ownership with explicit transactions and a portable backup path. - Interface: Jinja HTML templates, CSS and vanilla JavaScript. Implement the specified screens directly with labelled controls and progressive enhancement. - Verification: Python unittest and browser acceptance fixtures. Check invariants and the actual user workflow before the next phase. ### Data model (create this before Phase 1) - projects(id,key) - issues(id,project_id,number,title,type,status,estimate,sprint_id,revision) - transitions(from_status,to_status) - sprints(id,project_id,start,end,state) - events(id,issue_id,at,kind,payload) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. ### Prerequisites and configuration - Python 3.12 or newer and a terminal: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. Cost: Python is free; this local prototype requires no hosting subscription. - A current desktop browser and text editor: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. Verify: You can create a text file in the project folder and open browser developer tools. Cost: No paid service required for this local step. - Jira acceptance sample: Create synthetic sample data before implementation: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. Cost: No paid service required for this local step. - Confirm the bounded replacement: The deliverable is a focused issue backlog with explicit workflow transitions and sprint history. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. Cost: No paid service required for this local step. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL. Ship .env.example, replace placeholders and exclude secrets from git. ### Phase 1 · Local foundation and data contract Build: Create the runnable local foundation for a focused issue backlog with explicit workflow transitions and sprint history, including the real schema and acceptance fixture. - Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Commands, after creating the named files: `python -m venv .venv`; `python -m pip install Flask Flask-WTF python-dotenv waitress tzdata`; `python -m pip freeze > requirements.txt`; `python -m flask --app app run --host 127.0.0.1`. - For database-backed state create schema.sql and db.py using this model: projects(id,key); issues(id,project_id,number,title,type,status,estimate,sprint_id,revision); transitions(from_status,to_status); sprints(id,project_id,start,end,state); events(id,issue_id,at,kind,payload). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Re-running init must not erase data. Commands, after creating the named files: `python manage.py init`; `python manage.py seed`. - Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. - Trap: The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. Done when: The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. Restarting preserves the seeded records or canonical files; running init again deletes nothing. A cross-origin state-changing request to an admin route is refused. Do not build yet: Do not start issue keys and workflow until these checks pass. ### Phase 2 · Issue keys and workflow Build: Issue keys and workflow for Jira: Allocate monotonically increasing issue numbers per project in a transaction; support bug, story and task types. - Allocate monotonically increasing issue numbers per project in a transaction; support bug, story and task types. - Define allowed transitions as data and validate them server-side; record status events with the old and new value. - Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Two concurrent creates receive distinct APP keys. Then check: A forbidden transition returns a reason and leaves status unchanged. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Never derive issue numbers from the current row count. Done when: Two concurrent creates receive distinct APP keys. A forbidden transition returns a reason and leaves status unchanged. Do not build yet: Do not start backlog and sprint commitment until these checks pass. ### Phase 3 · Backlog and sprint commitment Build: Backlog and sprint commitment for Jira: Order backlog issues and move selected ids into a sprint with a start/end date; snapshot committed estimates when starting. - Order backlog issues and move selected ids into a sprint with a start/end date; snapshot committed estimates when starting. - Render a sprint board and record scope added or removed after start without rewriting the original commitment. - Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Adding a five-point issue mid-sprint appears as scope added, not original commitment. Then check: An issue cannot belong to two active sprints. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Current estimates cannot reconstruct historical sprint scope. Done when: Adding a five-point issue mid-sprint appears as scope added, not original commitment. An issue cannot belong to two active sprints. Do not build yet: Do not start close and report until these checks pass. ### Phase 4 · Close and report Build: Close and report for Jira: Close a sprint with an explicit choice to return unfinished issues to backlog or move them to a named future sprint. - Close a sprint with an explicit choice to return unfinished issues to backlog or move them to a named future sprint. - Compute completion and daily remaining points from dated events; label this a simple project report. - Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Closing moves unfinished work exactly once and preserves completed issue history. Then check: A reopened issue increases remaining work on its reopen day. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Velocity is a team planning measure; do not turn it into an individual performance score. Done when: Closing moves unfinished work exactly once and preserves completed issue history. A reopened issue increases remaining work on its reopen day. Do not build yet: Do not start portable delivery and clean-start proof until these checks pass. ### Phase 5 · Portable delivery and clean-start proof Build: Finish the Jira replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Issue keys and workflow; Backlog and sprint commitment; Close and report. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. - Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for jira. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. - Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Commands, after creating the named files: `python -m pip install -r requirements.txt`; `python -m unittest discover -s test`. - Trap: Export without an import or restore rehearsal is not verified portability. Done when: A new folder reaches the documented fixture outcome using only README instructions. A backup restored in isolation preserves the proof data and can be opened. Do not build yet: Do not start operate and share with access controls until these checks pass. ### Phase 6 · Operate and share with access controls (product-builder only) Build: Product-builder only: make a focused issue backlog with explicit workflow transitions and sprint history operable for its stated audience before allowing remote access. - Add owner/member/viewer authorization as appropriate, password hashes through Werkzeug, expiring server-side sessions, CSRF and login rate limits. Add users, sessions and audit schema migrations plus an owner-init command prompting securely for its password. Enforce ownership on every private read/write/download and fail closed when product setup is incomplete. Existing learner or admin identities must use this same boundary. - Serve app:app with Waitress on loopback behind Caddy HTTPS. Configure trusted proxy headers narrowly, Secure/HttpOnly/SameSite cookies, upload limits, request ids and structured logs without private content. Run background jobs as a separate supervised process when the domain workflow requires them. Commands, after creating the named files: `waitress-serve --listen=127.0.0.1:5000 app:app`. - Add a scheduled encrypted off-host backup using this procedure: Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for jira. Monitor health, disk space, failed jobs and backup age. Stop the service to test an alert; rehearse recovery with outbound effects disabled and record recovery time. Rotate any exposed credentials and require reconciliation before resuming queues. - Trap: Product mode is additional engineering, not a switch that makes a local prototype production-ready. Done when: An unauthenticated visitor cannot read private records, download private files or mutate the admin surface. A viewer cannot mutate data by making a direct request, and guessed ids cannot cross ownership boundaries. Stopping the service triggers the configured alert and the latest off-host backup restores the fixture in isolation. Do not build yet: Do not add new providers or vendor-scale features until the release gates are recorded. ### Out of scope (and why) - This is a focused issue backlog with explicit workflow transitions and sprint history; full Jira feature parity, vendor hosting and support are not included. - the Atlassian Marketplace and its long tail of organization-specific apps: retain the paid product if this capability is essential; it is outside this bounded build. - deep two-way integrations with source control, chat, support, and CI systems: retain the paid product if this capability is essential; it is outside this bounded build. - advanced roadmaps, reporting, automation, and cross-project dependency planning: retain the paid product if this capability is essential; it is outside this bounded build. - enterprise identity, permissions, audit, data residency, and support guarantees: retain the paid product if this capability is essential; it is outside this bounded build. - migration fidelity for years of custom fields, workflows, links, and issue history: retain the paid product if this capability is essential; it is outside this bounded build. ### README must contain - Exact install, configure, initialize, start, test and recovery commands for a clean folder. - The schema, fixture, acceptance results, private data locations and export format. - Every prerequisite and secret source, actual running costs and deliberately excluded capabilities. - An honest distinction between tests actually run and checks still awaiting real credentials or deployment. - Dependency documentation reviewed 2026-09-05: https://flask.palletsprojects.com/en/stable/installation/ ; https://docs.python.org/3/library/sqlite3.html ; https://flask-wtf.readthedocs.io/en/1.2.x/csrf/ ; https://docs.pylonsproject.org/projects/waitress/en/stable/usage.html. Recheck before upgrading; freeze the versions actually tested. ===== AGENTS.md ===== # Agent instructions · Jira indie build - Read `README.md` and `BUILD_PLAN.md` before writing code. The stack is fixed: Python 3.12+ and Flask, SQLite through Python sqlite3, Jinja HTML templates, CSS and vanilla JavaScript, Python unittest and browser acceptance fixtures. Do not substitute. - Work one phase at a time, in order. Do not start a phase until every "Done when" item of the previous one passes. - Prefer the fewest moving parts that satisfy the step. No frameworks, services or dependencies the plan does not name. - Secrets live in `.env`, never in source or logs. Keep `.env.example` current when a variable is introduced. - Do not invent cryptography, security guarantees, APIs or compliance claims. - Add a focused test for every destructive, security-sensitive or data-loss path the plan names. - Run the project checks before declaring a phase complete, and record any deliberate shortcut in the README under "Tradeoffs". ## Known traps - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. - Never derive issue numbers from the current row count. - Current estimates cannot reconstruct historical sprint scope. - Velocity is a team planning measure; do not turn it into an individual performance score. - Export without an import or restore rehearsal is not verified portability. ===== BUILD_PLAN.md ===== # Build plan · Jira Build a focused issue backlog with explicit workflow transitions and sprint history. Phases are in dependency order. Each ends in a "Done when" list; treat an unticked item as a blocker, not a note. ## Phase 1 · Local foundation and data contract Create the runnable local foundation for a focused issue backlog with explicit workflow transitions and sprint history, including the real schema and acceptance fixture. ### Steps 1. Create and start the local application Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Files: `app.py`, `requirements.txt`, `.env.example`, `.gitignore` ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` 2. Implement storage and seed the named fixture For database-backed state create schema.sql and db.py using this model: projects(id,key); issues(id,project_id,number,title,type,status,estimate,sprint_id,revision); transitions(from_status,to_status); sprints(id,project_id,start,end,state); events(id,issue_id,at,kind,payload). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Re-running init must not erase data. Files: `schema.sql`, `db.py`, `manage.py`, `fixtures/README.md` ```sh python manage.py init python manage.py seed ``` 3. Protect the local request boundary Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. Files: `app.py`, `templates/base.html`, `test/test_foundation.py` ### Done when - [ ] The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. - [ ] Restarting preserves the seeded records or canonical files; running init again deletes nothing. - [ ] A cross-origin state-changing request to an admin route is refused. ### Watch out - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. ## Phase 2 · Issue keys and workflow Issue keys and workflow for Jira: Allocate monotonically increasing issue numbers per project in a transaction; support bug, story and task types. ### Steps 1. Allocate monotonically increasing issue numbers per project in a transaction; support bug, story and task types. Allocate monotonically increasing issue numbers per project in a transaction; support bug, story and task types. Files: `features/issue_keys_and_workflow.py`, `templates/issue_keys_and_workflow.html` 2. Define allowed transitions as data and validate them server-side; record status events with the old and new value. Define allowed transitions as data and validate them server-side; record status events with the old and new value. Files: `features/issue_keys_and_workflow.py` 3. Exercise the acceptance fixture Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Two concurrent creates receive distinct APP keys. Then check: A forbidden transition returns a reason and leaves status unchanged. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_issue_keys_and_workflow.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Two concurrent creates receive distinct APP keys. - [ ] A forbidden transition returns a reason and leaves status unchanged. ### Watch out - Never derive issue numbers from the current row count. ## Phase 3 · Backlog and sprint commitment Backlog and sprint commitment for Jira: Order backlog issues and move selected ids into a sprint with a start/end date; snapshot committed estimates when starting. ### Steps 1. Order backlog issues and move selected ids into a sprint with a start/end date; snapshot committed estimates when starting. Order backlog issues and move selected ids into a sprint with a start/end date; snapshot committed estimates when starting. Files: `features/backlog_and_sprint_commitment.py`, `templates/backlog_and_sprint_commitment.html` 2. Render a sprint board and record scope added or removed after start without rewriting the original commitment. Render a sprint board and record scope added or removed after start without rewriting the original commitment. Files: `features/backlog_and_sprint_commitment.py` 3. Exercise the acceptance fixture Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Adding a five-point issue mid-sprint appears as scope added, not original commitment. Then check: An issue cannot belong to two active sprints. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_backlog_and_sprint_commitment.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Adding a five-point issue mid-sprint appears as scope added, not original commitment. - [ ] An issue cannot belong to two active sprints. ### Watch out - Current estimates cannot reconstruct historical sprint scope. ## Phase 4 · Close and report Close and report for Jira: Close a sprint with an explicit choice to return unfinished issues to backlog or move them to a named future sprint. ### Steps 1. Close a sprint with an explicit choice to return unfinished issues to backlog or move them to a named future sprint. Close a sprint with an explicit choice to return unfinished issues to backlog or move them to a named future sprint. Files: `features/close_and_report.py`, `templates/close_and_report.html` 2. Compute completion and daily remaining points from dated events; label this a simple project report. Compute completion and daily remaining points from dated events; label this a simple project report. Files: `features/close_and_report.py` 3. Exercise the acceptance fixture Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Closing moves unfinished work exactly once and preserves completed issue history. Then check: A reopened issue increases remaining work on its reopen day. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_close_and_report.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Closing moves unfinished work exactly once and preserves completed issue history. - [ ] A reopened issue increases remaining work on its reopen day. ### Watch out - Velocity is a team planning measure; do not turn it into an individual performance score. ## Phase 5 · Portable delivery and clean-start proof Finish the Jira replacement with a documented first-run path and a recoverable export. ### Steps 1. Write the user-facing runbook Document prerequisites, every configuration variable, data locations and the three domain workflows: Issue keys and workflow; Backlog and sprint commitment; Close and report. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. Files: `README.md`, `.env.example` 2. Create and rehearse a recoverable backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for jira. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. Files: `OPERATIONS.md`, `scripts/backup.py` 3. Reproduce the first-run experience Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Files: `README.md`, `verification.md` ```sh python -m pip install -r requirements.txt python -m unittest discover -s test ``` ### Done when - [ ] A new folder reaches the documented fixture outcome using only README instructions. - [ ] A backup restored in isolation preserves the proof data and can be opened. ### Watch out - Export without an import or restore rehearsal is not verified portability. ## Not in this build - This is a focused issue backlog with explicit workflow transitions and sprint history; full Jira feature parity, vendor hosting and support are not included. - the Atlassian Marketplace and its long tail of organization-specific apps - deep two-way integrations with source control, chat, support, and CI systems - advanced roadmaps, reporting, automation, and cross-project dependency planning - enterprise identity, permissions, audit, data residency, and support guarantees - migration fidelity for years of custom fields, workflows, links, and issue history ## After v1, if you want it - Extend close and report only after the fixture and recovery checks pass. - Before adding another integration, document its credentials, limits, cost and failure behavior with primary-source links. ===== .env.example ===== # Copy to .env and fill in. Never commit .env; this file documents it. # Required. A new private folder this application creates on first run; never serve it as static files. DATA_DIR=./data/jira # Required · secret. Generate with python -c "import secrets; print(secrets.token_hex(32))" and save only in .env. SECRET_KEY=replace-with-a-random-secret # Required. Use indie for loopback-only personal work. Product mode must refuse to start until owner login and the deployment gates are configured. APP_MODE=indie # Required. The origin used for local forms and links; replace with the chosen HTTPS origin in product mode. SITE_URL=http://127.0.0.1:5000
You are building a production product version of Jira. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # Jira · product brief ## Problem Issues, workflows, a backlog, sprints, and a board are a credible multi-day build for one small team. The replacement stops being small when Jira is the company's system of record: custom schemes, permissions, automation, reporting, marketplace apps, two-way integrations, and years of workflow history are the product people are actually paying not to migrate. ## Product outcome An operated version of a focused issue backlog with explicit workflow transitions and sprint history, with authorized access, restore evidence and honest scope limits. ## Target user A builder who needs a maintainable product foundation, not a one-off demo. ## Required capabilities - Docker - PostgreSQL - self-hosted server - email credentials for invitations and notifications - GitHub token for optional repository sync ## Explicit non-goals for v1 - This is a focused issue backlog with explicit workflow transitions and sprint history; full Jira feature parity, vendor hosting and support are not included. - the Atlassian Marketplace and its long tail of organization-specific apps - deep two-way integrations with source control, chat, support, and CI systems - advanced roadmaps, reporting, automation, and cross-project dependency planning - enterprise identity, permissions, audit, data residency, and support guarantees - migration fidelity for years of custom fields, workflows, links, and issue history ## Success criteria - Two concurrent creates receive distinct APP keys. - Adding a five-point issue mid-sprint appears as scope added, not original commitment. - Closing moves unfinished work exactly once and preserves completed issue history. - A private-data authorization check passes using a second identity. - An off-host restore drill has a date, observed result and recovery time in OPERATIONS.md. - README names the excluded vendor capabilities and actual provider/hosting costs. ===== BRIEF.md ===== # Build brief · Jira The one-shot brief this plan expands. `BUILD_PLAN.md` (or `MILESTONES.md`) is the same sequence broken into steps and checks; where the two disagree, the plan wins. Build me a focused issue backlog with explicit workflow transitions and sprint history as a bounded replacement for Jira. Build it in phases in the order below. Do not write the whole product in one pass. Finish the current phase, run its Done when checks, fix failures, then continue. Indie mode completes Phases 1-5. Phase 6 is required before shared or public deployment. ### Stack (fixed, do not substitute) - Runtime: Python 3.12+ and Flask. A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. - Storage: SQLite through Python sqlite3. Local ownership with explicit transactions and a portable backup path. - Interface: Jinja HTML templates, CSS and vanilla JavaScript. Implement the specified screens directly with labelled controls and progressive enhancement. - Verification: Python unittest and browser acceptance fixtures. Check invariants and the actual user workflow before the next phase. ### Data model (create this before Phase 1) - projects(id,key) - issues(id,project_id,number,title,type,status,estimate,sprint_id,revision) - transitions(from_status,to_status) - sprints(id,project_id,start,end,state) - events(id,issue_id,at,kind,payload) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. ### Prerequisites and configuration - Python 3.12 or newer and a terminal: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. Cost: Python is free; this local prototype requires no hosting subscription. - A current desktop browser and text editor: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. Verify: You can create a text file in the project folder and open browser developer tools. Cost: No paid service required for this local step. - Jira acceptance sample: Create synthetic sample data before implementation: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. Cost: No paid service required for this local step. - Confirm the bounded replacement: The deliverable is a focused issue backlog with explicit workflow transitions and sprint history. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. Cost: No paid service required for this local step. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL. Ship .env.example, replace placeholders and exclude secrets from git. ### Phase 1 · Local foundation and data contract Build: Create the runnable local foundation for a focused issue backlog with explicit workflow transitions and sprint history, including the real schema and acceptance fixture. - Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Commands, after creating the named files: `python -m venv .venv`; `python -m pip install Flask Flask-WTF python-dotenv waitress tzdata`; `python -m pip freeze > requirements.txt`; `python -m flask --app app run --host 127.0.0.1`. - For database-backed state create schema.sql and db.py using this model: projects(id,key); issues(id,project_id,number,title,type,status,estimate,sprint_id,revision); transitions(from_status,to_status); sprints(id,project_id,start,end,state); events(id,issue_id,at,kind,payload). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Re-running init must not erase data. Commands, after creating the named files: `python manage.py init`; `python manage.py seed`. - Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. - Trap: The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. Done when: The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. Restarting preserves the seeded records or canonical files; running init again deletes nothing. A cross-origin state-changing request to an admin route is refused. Do not build yet: Do not start issue keys and workflow until these checks pass. ### Phase 2 · Issue keys and workflow Build: Issue keys and workflow for Jira: Allocate monotonically increasing issue numbers per project in a transaction; support bug, story and task types. - Allocate monotonically increasing issue numbers per project in a transaction; support bug, story and task types. - Define allowed transitions as data and validate them server-side; record status events with the old and new value. - Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Two concurrent creates receive distinct APP keys. Then check: A forbidden transition returns a reason and leaves status unchanged. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Never derive issue numbers from the current row count. Done when: Two concurrent creates receive distinct APP keys. A forbidden transition returns a reason and leaves status unchanged. Do not build yet: Do not start backlog and sprint commitment until these checks pass. ### Phase 3 · Backlog and sprint commitment Build: Backlog and sprint commitment for Jira: Order backlog issues and move selected ids into a sprint with a start/end date; snapshot committed estimates when starting. - Order backlog issues and move selected ids into a sprint with a start/end date; snapshot committed estimates when starting. - Render a sprint board and record scope added or removed after start without rewriting the original commitment. - Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Adding a five-point issue mid-sprint appears as scope added, not original commitment. Then check: An issue cannot belong to two active sprints. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Current estimates cannot reconstruct historical sprint scope. Done when: Adding a five-point issue mid-sprint appears as scope added, not original commitment. An issue cannot belong to two active sprints. Do not build yet: Do not start close and report until these checks pass. ### Phase 4 · Close and report Build: Close and report for Jira: Close a sprint with an explicit choice to return unfinished issues to backlog or move them to a named future sprint. - Close a sprint with an explicit choice to return unfinished issues to backlog or move them to a named future sprint. - Compute completion and daily remaining points from dated events; label this a simple project report. - Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Closing moves unfinished work exactly once and preserves completed issue history. Then check: A reopened issue increases remaining work on its reopen day. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Velocity is a team planning measure; do not turn it into an individual performance score. Done when: Closing moves unfinished work exactly once and preserves completed issue history. A reopened issue increases remaining work on its reopen day. Do not build yet: Do not start portable delivery and clean-start proof until these checks pass. ### Phase 5 · Portable delivery and clean-start proof Build: Finish the Jira replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Issue keys and workflow; Backlog and sprint commitment; Close and report. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. - Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for jira. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. - Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Commands, after creating the named files: `python -m pip install -r requirements.txt`; `python -m unittest discover -s test`. - Trap: Export without an import or restore rehearsal is not verified portability. Done when: A new folder reaches the documented fixture outcome using only README instructions. A backup restored in isolation preserves the proof data and can be opened. Do not build yet: Do not start operate and share with access controls until these checks pass. ### Phase 6 · Operate and share with access controls (product-builder only) Build: Product-builder only: make a focused issue backlog with explicit workflow transitions and sprint history operable for its stated audience before allowing remote access. - Add owner/member/viewer authorization as appropriate, password hashes through Werkzeug, expiring server-side sessions, CSRF and login rate limits. Add users, sessions and audit schema migrations plus an owner-init command prompting securely for its password. Enforce ownership on every private read/write/download and fail closed when product setup is incomplete. Existing learner or admin identities must use this same boundary. - Serve app:app with Waitress on loopback behind Caddy HTTPS. Configure trusted proxy headers narrowly, Secure/HttpOnly/SameSite cookies, upload limits, request ids and structured logs without private content. Run background jobs as a separate supervised process when the domain workflow requires them. Commands, after creating the named files: `waitress-serve --listen=127.0.0.1:5000 app:app`. - Add a scheduled encrypted off-host backup using this procedure: Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for jira. Monitor health, disk space, failed jobs and backup age. Stop the service to test an alert; rehearse recovery with outbound effects disabled and record recovery time. Rotate any exposed credentials and require reconciliation before resuming queues. - Trap: Product mode is additional engineering, not a switch that makes a local prototype production-ready. Done when: An unauthenticated visitor cannot read private records, download private files or mutate the admin surface. A viewer cannot mutate data by making a direct request, and guessed ids cannot cross ownership boundaries. Stopping the service triggers the configured alert and the latest off-host backup restores the fixture in isolation. Do not build yet: Do not add new providers or vendor-scale features until the release gates are recorded. ### Out of scope (and why) - This is a focused issue backlog with explicit workflow transitions and sprint history; full Jira feature parity, vendor hosting and support are not included. - the Atlassian Marketplace and its long tail of organization-specific apps: retain the paid product if this capability is essential; it is outside this bounded build. - deep two-way integrations with source control, chat, support, and CI systems: retain the paid product if this capability is essential; it is outside this bounded build. - advanced roadmaps, reporting, automation, and cross-project dependency planning: retain the paid product if this capability is essential; it is outside this bounded build. - enterprise identity, permissions, audit, data residency, and support guarantees: retain the paid product if this capability is essential; it is outside this bounded build. - migration fidelity for years of custom fields, workflows, links, and issue history: retain the paid product if this capability is essential; it is outside this bounded build. ### README must contain - Exact install, configure, initialize, start, test and recovery commands for a clean folder. - The schema, fixture, acceptance results, private data locations and export format. - Every prerequisite and secret source, actual running costs and deliberately excluded capabilities. - An honest distinction between tests actually run and checks still awaiting real credentials or deployment. - Dependency documentation reviewed 2026-09-05: https://flask.palletsprojects.com/en/stable/installation/ ; https://docs.python.org/3/library/sqlite3.html ; https://flask-wtf.readthedocs.io/en/1.2.x/csrf/ ; https://docs.pylonsproject.org/projects/waitress/en/stable/usage.html. Recheck before upgrading; freeze the versions actually tested. ===== ARCHITECTURE.md ===== # Architecture · Jira ## Stack | Part | Choice | Why | | --- | --- | --- | | Runtime | Python 3.12+ and Flask | A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. | | Storage | SQLite through Python sqlite3 | Local ownership with explicit transactions and a portable backup path. | | Interface | Jinja HTML templates, CSS and vanilla JavaScript | Implement the specified screens directly with labelled controls and progressive enhancement. | | Verification | Python unittest and browser acceptance fixtures | Check invariants and the actual user workflow before the next phase. | ## Modules Each module has one owner concern and a documented way to replace it. | Module | Owns | How to replace it | | --- | --- | --- | | Data and identity | projects(id,key); issues(id,project_id,number,title,type,status,estimate,sprint_id,revision); transitions(from_status,to_status); sprints(id,project_id,start,end,state); events(id,issue_id,at,kind,payload) | Keep stable ids and a versioned repository interface; migrate storage behind it with a fixture round-trip. | | Issue keys and workflow | Allocate monotonically increasing issue numbers per project in a transaction; support bug, story and task types. | Keep the acceptance contract: Two concurrent creates receive distinct APP keys. Replace only this module after replaying its fixture; preserve ids and existing records. | | Backlog and sprint commitment | Order backlog issues and move selected ids into a sprint with a start/end date; snapshot committed estimates when starting. | Keep the acceptance contract: Adding a five-point issue mid-sprint appears as scope added, not original commitment. Replace only this module after replaying its fixture; preserve ids and existing records. | | Close and report | Close a sprint with an explicit choice to return unfinished issues to backlog or move them to a named future sprint. | Keep the acceptance contract: Closing moves unfinished work exactly once and preserves completed issue history. Replace only this module after replaying its fixture; preserve ids and existing records. | | Operations | Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for jira. | Change host or backup destination only after an isolated restore and authorization check. | ## Configuration Every runtime setting is an environment variable documented in `.env.example`, validated at startup, with a safe local default wherever one exists. - `DATA_DIR` · required · A new private folder this application creates on first run; never serve it as static files. - `SECRET_KEY` · required, secret · Generate with python -c "import secrets; print(secrets.token_hex(32))" and save only in .env. - `APP_MODE` · required · Use indie for loopback-only personal work. Product mode must refuse to start until owner login and the deployment gates are configured. - `SITE_URL` · required · The origin used for local forms and links; replace with the chosen HTTPS origin in product mode. ## Production baseline - Security: least privilege, input validation at every boundary, secret redaction in logs, rate limits on abuse-prone paths, no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore procedures that have been exercised. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, timeouts. - Observability: structured logs with request or operation ids, an error-tracking hook, and health and readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, one end-to-end test of the critical path. ## Decision records For each dependency in the stack table, keep a short note: why it was chosen, its failure mode, and how it is replaced. Do not add infrastructure until a requirement in `PRODUCT.md` justifies it. ===== AGENTS.md ===== # Agent instructions · Jira product build - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. The stack is fixed: Python 3.12+ and Flask, SQLite through Python sqlite3, Jinja HTML templates, CSS and vanilla JavaScript, Python unittest and browser acceptance fixtures. - Implement milestone by milestone from `MILESTONES.md`; keep each change reviewable and leave the application runnable at every commit. - Treat authentication, payments, encryption, imports, webhooks and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a check pass. - Put every external service behind an interface with a deterministic fake for tests. - Add migrations and rollback or recovery notes for every persistent data change. - Log useful operational context without credentials, tokens, passwords or personal data. - Update documentation and run every check before completing a milestone. ## Known traps - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. - Never derive issue numbers from the current row count. - Current estimates cannot reconstruct historical sprint scope. - Velocity is a team planning measure; do not turn it into an individual performance score. - Export without an import or restore rehearsal is not verified portability. - Product mode is additional engineering, not a switch that makes a local prototype production-ready. ===== MILESTONES.md ===== # Delivery milestones · Jira Estimated effort: **multi-day** for the indie phases; the production-only milestones add the trust and operability layer. ## M1 · Local foundation and data contract Create the runnable local foundation for a focused issue backlog with explicit workflow transitions and sprint history, including the real schema and acceptance fixture. ### Steps 1. Create and start the local application Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Files: `app.py`, `requirements.txt`, `.env.example`, `.gitignore` ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` 2. Implement storage and seed the named fixture For database-backed state create schema.sql and db.py using this model: projects(id,key); issues(id,project_id,number,title,type,status,estimate,sprint_id,revision); transitions(from_status,to_status); sprints(id,project_id,start,end,state); events(id,issue_id,at,kind,payload). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Re-running init must not erase data. Files: `schema.sql`, `db.py`, `manage.py`, `fixtures/README.md` ```sh python manage.py init python manage.py seed ``` 3. Protect the local request boundary Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. Files: `app.py`, `templates/base.html`, `test/test_foundation.py` ### Done when - [ ] The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. - [ ] Restarting preserves the seeded records or canonical files; running init again deletes nothing. - [ ] A cross-origin state-changing request to an admin route is refused. ### Watch out - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. ## M2 · Issue keys and workflow Issue keys and workflow for Jira: Allocate monotonically increasing issue numbers per project in a transaction; support bug, story and task types. ### Steps 1. Allocate monotonically increasing issue numbers per project in a transaction; support bug, story and task types. Allocate monotonically increasing issue numbers per project in a transaction; support bug, story and task types. Files: `features/issue_keys_and_workflow.py`, `templates/issue_keys_and_workflow.html` 2. Define allowed transitions as data and validate them server-side; record status events with the old and new value. Define allowed transitions as data and validate them server-side; record status events with the old and new value. Files: `features/issue_keys_and_workflow.py` 3. Exercise the acceptance fixture Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Two concurrent creates receive distinct APP keys. Then check: A forbidden transition returns a reason and leaves status unchanged. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_issue_keys_and_workflow.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Two concurrent creates receive distinct APP keys. - [ ] A forbidden transition returns a reason and leaves status unchanged. ### Watch out - Never derive issue numbers from the current row count. ## M3 · Backlog and sprint commitment Backlog and sprint commitment for Jira: Order backlog issues and move selected ids into a sprint with a start/end date; snapshot committed estimates when starting. ### Steps 1. Order backlog issues and move selected ids into a sprint with a start/end date; snapshot committed estimates when starting. Order backlog issues and move selected ids into a sprint with a start/end date; snapshot committed estimates when starting. Files: `features/backlog_and_sprint_commitment.py`, `templates/backlog_and_sprint_commitment.html` 2. Render a sprint board and record scope added or removed after start without rewriting the original commitment. Render a sprint board and record scope added or removed after start without rewriting the original commitment. Files: `features/backlog_and_sprint_commitment.py` 3. Exercise the acceptance fixture Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Adding a five-point issue mid-sprint appears as scope added, not original commitment. Then check: An issue cannot belong to two active sprints. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_backlog_and_sprint_commitment.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Adding a five-point issue mid-sprint appears as scope added, not original commitment. - [ ] An issue cannot belong to two active sprints. ### Watch out - Current estimates cannot reconstruct historical sprint scope. ## M4 · Close and report Close and report for Jira: Close a sprint with an explicit choice to return unfinished issues to backlog or move them to a named future sprint. ### Steps 1. Close a sprint with an explicit choice to return unfinished issues to backlog or move them to a named future sprint. Close a sprint with an explicit choice to return unfinished issues to backlog or move them to a named future sprint. Files: `features/close_and_report.py`, `templates/close_and_report.html` 2. Compute completion and daily remaining points from dated events; label this a simple project report. Compute completion and daily remaining points from dated events; label this a simple project report. Files: `features/close_and_report.py` 3. Exercise the acceptance fixture Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Closing moves unfinished work exactly once and preserves completed issue history. Then check: A reopened issue increases remaining work on its reopen day. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_close_and_report.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Closing moves unfinished work exactly once and preserves completed issue history. - [ ] A reopened issue increases remaining work on its reopen day. ### Watch out - Velocity is a team planning measure; do not turn it into an individual performance score. ## M5 · Portable delivery and clean-start proof Finish the Jira replacement with a documented first-run path and a recoverable export. ### Steps 1. Write the user-facing runbook Document prerequisites, every configuration variable, data locations and the three domain workflows: Issue keys and workflow; Backlog and sprint commitment; Close and report. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. Files: `README.md`, `.env.example` 2. Create and rehearse a recoverable backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for jira. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. Files: `OPERATIONS.md`, `scripts/backup.py` 3. Reproduce the first-run experience Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Files: `README.md`, `verification.md` ```sh python -m pip install -r requirements.txt python -m unittest discover -s test ``` ### Done when - [ ] A new folder reaches the documented fixture outcome using only README instructions. - [ ] A backup restored in isolation preserves the proof data and can be opened. ### Watch out - Export without an import or restore rehearsal is not verified portability. ## M6 · Operate and share with access controls (production only) Product-builder only: make a focused issue backlog with explicit workflow transitions and sprint history operable for its stated audience before allowing remote access. ### Steps 1. Establish owner access before exposure Add owner/member/viewer authorization as appropriate, password hashes through Werkzeug, expiring server-side sessions, CSRF and login rate limits. Add users, sessions and audit schema migrations plus an owner-init command prompting securely for its password. Enforce ownership on every private read/write/download and fail closed when product setup is incomplete. Existing learner or admin identities must use this same boundary. Files: `ARCHITECTURE.md`, `OPERATIONS.md` 2. Deploy a monitored service Serve app:app with Waitress on loopback behind Caddy HTTPS. Configure trusted proxy headers narrowly, Secure/HttpOnly/SameSite cookies, upload limits, request ids and structured logs without private content. Run background jobs as a separate supervised process when the domain workflow requires them. Files: `Caddyfile`, `OPERATIONS.md` ```sh waitress-serve --listen=127.0.0.1:5000 app:app ``` 3. Rehearse loss and recovery Add a scheduled encrypted off-host backup using this procedure: Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for jira. Monitor health, disk space, failed jobs and backup age. Stop the service to test an alert; rehearse recovery with outbound effects disabled and record recovery time. Rotate any exposed credentials and require reconciliation before resuming queues. Files: `OPERATIONS.md`, `release-checklist.md` ### Done when - [ ] An unauthenticated visitor cannot read private records, download private files or mutate the admin surface. - [ ] A viewer cannot mutate data by making a direct request, and guessed ids cannot cross ownership boundaries. - [ ] Stopping the service triggers the configured alert and the latest off-host backup restores the fixture in isolation. ### Watch out - Product mode is additional engineering, not a switch that makes a local prototype production-ready. ===== OPERATIONS.md ===== # Operations · Jira ## Backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for jira. ## Restore Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. Do a restore drill before the first real user, and write the date here when it passes. ## Monitoring Check HTTP availability, free disk, backup age and domain failures for Issue keys and workflow, Backlog and sprint commitment, Close and report. Alert without logging private payloads. ## Incident checklist Pause outbound jobs and public intake as appropriate, preserve redacted diagnostics, restore an isolated verified backup, rotate affected credentials and reconcile uncertain effects before reopening. 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified backup when needed. 5. Document the root cause, the remediation and the regression test. ## Release gate - [ ] Two concurrent creates receive distinct APP keys. - [ ] Adding a five-point issue mid-sprint appears as scope added, not original commitment. - [ ] Closing moves unfinished work exactly once and preserves completed issue history. - [ ] A private-data authorization check passes using a second identity. - [ ] An off-host restore drill has a date, observed result and recovery time in OPERATIONS.md. - [ ] README names the excluded vendor capabilities and actual provider/hosting costs. ## Launch constraint Do not market omitted Jira capabilities as implemented. The non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered. ===== .env.example ===== # Copy to .env and fill in. Never commit .env; this file documents it. # Required. A new private folder this application creates on first run; never serve it as static files. DATA_DIR=./data/jira # Required · secret. Generate with python -c "import secrets; print(secrets.token_hex(32))" and save only in .env. SECRET_KEY=replace-with-a-random-secret # Required. Use indie for loopback-only personal work. Product mode must refuse to start until owner login and the deployment gates are configured. APP_MODE=indie # Required. The origin used for local forms and links; replace with the chosen HTTPS origin in product mode. SITE_URL=http://127.0.0.1:5000
README.md
# Jira · indie build Build a focused issue backlog with explicit workflow transitions and sprint history. Estimated effort: **multi-day**. Work `BUILD_PLAN.md` top to bottom · every phase ends in a check that has to pass before the next one starts. ## Stack | Part | Choice | Why | | --- | --- | --- | | Runtime | Python 3.12+ and Flask | A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. | | Storage | SQLite through Python sqlite3 | Local ownership with explicit transactions and a portable backup path. | | Interface | Jinja HTML templates, CSS and vanilla JavaScript | Implement the specified screens directly with labelled controls and progressive enhancement. | | Verification | Python unittest and browser acceptance fixtures | Check invariants and the actual user workflow before the next phase. | ## Before you start Have every one of these ready. The plan assumes them from step one. - [ ] **Python 3.12 or newer and a terminal** · Python is free; this local prototype requires no hosting subscription. - Why: The local backend, tests and storage use Python. - Get it: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. - Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. - [ ] **A current desktop browser and text editor** · No paid service required for this local step. - Why: You need to view the local interface and edit generated project files. - Get it: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. - Verify: You can create a text file in the project folder and open browser developer tools. - [ ] **Jira acceptance sample** · No paid service required for this local step. - Why: This fixture makes the first end-to-end check reproducible. - Get it: Create synthetic sample data before implementation: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. - Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. - [ ] **Confirm the bounded replacement** · No paid service required for this local step. - Why: The full commercial product is larger than this guide. - Get it: The deliverable is a focused issue backlog with explicit workflow transitions and sprint history. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. - Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. ## Quick start ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` Then copy `.env.example` to `.env` and fill in the values it documents. ## Honest limits This build deliberately does not replace: - This is a focused issue backlog with explicit workflow transitions and sprint history; full Jira feature parity, vendor hosting and support are not included. - the Atlassian Marketplace and its long tail of organization-specific apps - deep two-way integrations with source control, chat, support, and CI systems - advanced roadmaps, reporting, automation, and cross-project dependency planning - enterprise identity, permissions, audit, data residency, and support guarantees - migration fidelity for years of custom fields, workflows, links, and issue history If one of those is essential to you, that is the reason to keep paying for Jira, and the README should say so rather than pretend.
BRIEF.md
# Build brief · Jira The one-shot brief this plan expands. `BUILD_PLAN.md` (or `MILESTONES.md`) is the same sequence broken into steps and checks; where the two disagree, the plan wins. Build me a focused issue backlog with explicit workflow transitions and sprint history as a bounded replacement for Jira. Build it in phases in the order below. Do not write the whole product in one pass. Finish the current phase, run its Done when checks, fix failures, then continue. Indie mode completes Phases 1-5. Phase 6 is required before shared or public deployment. ### Stack (fixed, do not substitute) - Runtime: Python 3.12+ and Flask. A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. - Storage: SQLite through Python sqlite3. Local ownership with explicit transactions and a portable backup path. - Interface: Jinja HTML templates, CSS and vanilla JavaScript. Implement the specified screens directly with labelled controls and progressive enhancement. - Verification: Python unittest and browser acceptance fixtures. Check invariants and the actual user workflow before the next phase. ### Data model (create this before Phase 1) - projects(id,key) - issues(id,project_id,number,title,type,status,estimate,sprint_id,revision) - transitions(from_status,to_status) - sprints(id,project_id,start,end,state) - events(id,issue_id,at,kind,payload) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. ### Prerequisites and configuration - Python 3.12 or newer and a terminal: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. Cost: Python is free; this local prototype requires no hosting subscription. - A current desktop browser and text editor: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. Verify: You can create a text file in the project folder and open browser developer tools. Cost: No paid service required for this local step. - Jira acceptance sample: Create synthetic sample data before implementation: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. Cost: No paid service required for this local step. - Confirm the bounded replacement: The deliverable is a focused issue backlog with explicit workflow transitions and sprint history. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. Cost: No paid service required for this local step. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL. Ship .env.example, replace placeholders and exclude secrets from git. ### Phase 1 · Local foundation and data contract Build: Create the runnable local foundation for a focused issue backlog with explicit workflow transitions and sprint history, including the real schema and acceptance fixture. - Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Commands, after creating the named files: `python -m venv .venv`; `python -m pip install Flask Flask-WTF python-dotenv waitress tzdata`; `python -m pip freeze > requirements.txt`; `python -m flask --app app run --host 127.0.0.1`. - For database-backed state create schema.sql and db.py using this model: projects(id,key); issues(id,project_id,number,title,type,status,estimate,sprint_id,revision); transitions(from_status,to_status); sprints(id,project_id,start,end,state); events(id,issue_id,at,kind,payload). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Re-running init must not erase data. Commands, after creating the named files: `python manage.py init`; `python manage.py seed`. - Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. - Trap: The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. Done when: The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. Restarting preserves the seeded records or canonical files; running init again deletes nothing. A cross-origin state-changing request to an admin route is refused. Do not build yet: Do not start issue keys and workflow until these checks pass. ### Phase 2 · Issue keys and workflow Build: Issue keys and workflow for Jira: Allocate monotonically increasing issue numbers per project in a transaction; support bug, story and task types. - Allocate monotonically increasing issue numbers per project in a transaction; support bug, story and task types. - Define allowed transitions as data and validate them server-side; record status events with the old and new value. - Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Two concurrent creates receive distinct APP keys. Then check: A forbidden transition returns a reason and leaves status unchanged. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Never derive issue numbers from the current row count. Done when: Two concurrent creates receive distinct APP keys. A forbidden transition returns a reason and leaves status unchanged. Do not build yet: Do not start backlog and sprint commitment until these checks pass. ### Phase 3 · Backlog and sprint commitment Build: Backlog and sprint commitment for Jira: Order backlog issues and move selected ids into a sprint with a start/end date; snapshot committed estimates when starting. - Order backlog issues and move selected ids into a sprint with a start/end date; snapshot committed estimates when starting. - Render a sprint board and record scope added or removed after start without rewriting the original commitment. - Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Adding a five-point issue mid-sprint appears as scope added, not original commitment. Then check: An issue cannot belong to two active sprints. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Current estimates cannot reconstruct historical sprint scope. Done when: Adding a five-point issue mid-sprint appears as scope added, not original commitment. An issue cannot belong to two active sprints. Do not build yet: Do not start close and report until these checks pass. ### Phase 4 · Close and report Build: Close and report for Jira: Close a sprint with an explicit choice to return unfinished issues to backlog or move them to a named future sprint. - Close a sprint with an explicit choice to return unfinished issues to backlog or move them to a named future sprint. - Compute completion and daily remaining points from dated events; label this a simple project report. - Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Closing moves unfinished work exactly once and preserves completed issue history. Then check: A reopened issue increases remaining work on its reopen day. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Velocity is a team planning measure; do not turn it into an individual performance score. Done when: Closing moves unfinished work exactly once and preserves completed issue history. A reopened issue increases remaining work on its reopen day. Do not build yet: Do not start portable delivery and clean-start proof until these checks pass. ### Phase 5 · Portable delivery and clean-start proof Build: Finish the Jira replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Issue keys and workflow; Backlog and sprint commitment; Close and report. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. - Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for jira. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. - Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Commands, after creating the named files: `python -m pip install -r requirements.txt`; `python -m unittest discover -s test`. - Trap: Export without an import or restore rehearsal is not verified portability. Done when: A new folder reaches the documented fixture outcome using only README instructions. A backup restored in isolation preserves the proof data and can be opened. Do not build yet: Do not start operate and share with access controls until these checks pass. ### Phase 6 · Operate and share with access controls (product-builder only) Build: Product-builder only: make a focused issue backlog with explicit workflow transitions and sprint history operable for its stated audience before allowing remote access. - Add owner/member/viewer authorization as appropriate, password hashes through Werkzeug, expiring server-side sessions, CSRF and login rate limits. Add users, sessions and audit schema migrations plus an owner-init command prompting securely for its password. Enforce ownership on every private read/write/download and fail closed when product setup is incomplete. Existing learner or admin identities must use this same boundary. - Serve app:app with Waitress on loopback behind Caddy HTTPS. Configure trusted proxy headers narrowly, Secure/HttpOnly/SameSite cookies, upload limits, request ids and structured logs without private content. Run background jobs as a separate supervised process when the domain workflow requires them. Commands, after creating the named files: `waitress-serve --listen=127.0.0.1:5000 app:app`. - Add a scheduled encrypted off-host backup using this procedure: Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for jira. Monitor health, disk space, failed jobs and backup age. Stop the service to test an alert; rehearse recovery with outbound effects disabled and record recovery time. Rotate any exposed credentials and require reconciliation before resuming queues. - Trap: Product mode is additional engineering, not a switch that makes a local prototype production-ready. Done when: An unauthenticated visitor cannot read private records, download private files or mutate the admin surface. A viewer cannot mutate data by making a direct request, and guessed ids cannot cross ownership boundaries. Stopping the service triggers the configured alert and the latest off-host backup restores the fixture in isolation. Do not build yet: Do not add new providers or vendor-scale features until the release gates are recorded. ### Out of scope (and why) - This is a focused issue backlog with explicit workflow transitions and sprint history; full Jira feature parity, vendor hosting and support are not included. - the Atlassian Marketplace and its long tail of organization-specific apps: retain the paid product if this capability is essential; it is outside this bounded build. - deep two-way integrations with source control, chat, support, and CI systems: retain the paid product if this capability is essential; it is outside this bounded build. - advanced roadmaps, reporting, automation, and cross-project dependency planning: retain the paid product if this capability is essential; it is outside this bounded build. - enterprise identity, permissions, audit, data residency, and support guarantees: retain the paid product if this capability is essential; it is outside this bounded build. - migration fidelity for years of custom fields, workflows, links, and issue history: retain the paid product if this capability is essential; it is outside this bounded build. ### README must contain - Exact install, configure, initialize, start, test and recovery commands for a clean folder. - The schema, fixture, acceptance results, private data locations and export format. - Every prerequisite and secret source, actual running costs and deliberately excluded capabilities. - An honest distinction between tests actually run and checks still awaiting real credentials or deployment. - Dependency documentation reviewed 2026-09-05: https://flask.palletsprojects.com/en/stable/installation/ ; https://docs.python.org/3/library/sqlite3.html ; https://flask-wtf.readthedocs.io/en/1.2.x/csrf/ ; https://docs.pylonsproject.org/projects/waitress/en/stable/usage.html. Recheck before upgrading; freeze the versions actually tested.
AGENTS.md
# Agent instructions · Jira indie build - Read `README.md` and `BUILD_PLAN.md` before writing code. The stack is fixed: Python 3.12+ and Flask, SQLite through Python sqlite3, Jinja HTML templates, CSS and vanilla JavaScript, Python unittest and browser acceptance fixtures. Do not substitute. - Work one phase at a time, in order. Do not start a phase until every "Done when" item of the previous one passes. - Prefer the fewest moving parts that satisfy the step. No frameworks, services or dependencies the plan does not name. - Secrets live in `.env`, never in source or logs. Keep `.env.example` current when a variable is introduced. - Do not invent cryptography, security guarantees, APIs or compliance claims. - Add a focused test for every destructive, security-sensitive or data-loss path the plan names. - Run the project checks before declaring a phase complete, and record any deliberate shortcut in the README under "Tradeoffs". ## Known traps - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. - Never derive issue numbers from the current row count. - Current estimates cannot reconstruct historical sprint scope. - Velocity is a team planning measure; do not turn it into an individual performance score. - Export without an import or restore rehearsal is not verified portability.
BUILD_PLAN.md
# Build plan · Jira Build a focused issue backlog with explicit workflow transitions and sprint history. Phases are in dependency order. Each ends in a "Done when" list; treat an unticked item as a blocker, not a note. ## Phase 1 · Local foundation and data contract Create the runnable local foundation for a focused issue backlog with explicit workflow transitions and sprint history, including the real schema and acceptance fixture. ### Steps 1. Create and start the local application Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Files: `app.py`, `requirements.txt`, `.env.example`, `.gitignore` ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` 2. Implement storage and seed the named fixture For database-backed state create schema.sql and db.py using this model: projects(id,key); issues(id,project_id,number,title,type,status,estimate,sprint_id,revision); transitions(from_status,to_status); sprints(id,project_id,start,end,state); events(id,issue_id,at,kind,payload). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Re-running init must not erase data. Files: `schema.sql`, `db.py`, `manage.py`, `fixtures/README.md` ```sh python manage.py init python manage.py seed ``` 3. Protect the local request boundary Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. Files: `app.py`, `templates/base.html`, `test/test_foundation.py` ### Done when - [ ] The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. - [ ] Restarting preserves the seeded records or canonical files; running init again deletes nothing. - [ ] A cross-origin state-changing request to an admin route is refused. ### Watch out - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. ## Phase 2 · Issue keys and workflow Issue keys and workflow for Jira: Allocate monotonically increasing issue numbers per project in a transaction; support bug, story and task types. ### Steps 1. Allocate monotonically increasing issue numbers per project in a transaction; support bug, story and task types. Allocate monotonically increasing issue numbers per project in a transaction; support bug, story and task types. Files: `features/issue_keys_and_workflow.py`, `templates/issue_keys_and_workflow.html` 2. Define allowed transitions as data and validate them server-side; record status events with the old and new value. Define allowed transitions as data and validate them server-side; record status events with the old and new value. Files: `features/issue_keys_and_workflow.py` 3. Exercise the acceptance fixture Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Two concurrent creates receive distinct APP keys. Then check: A forbidden transition returns a reason and leaves status unchanged. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_issue_keys_and_workflow.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Two concurrent creates receive distinct APP keys. - [ ] A forbidden transition returns a reason and leaves status unchanged. ### Watch out - Never derive issue numbers from the current row count. ## Phase 3 · Backlog and sprint commitment Backlog and sprint commitment for Jira: Order backlog issues and move selected ids into a sprint with a start/end date; snapshot committed estimates when starting. ### Steps 1. Order backlog issues and move selected ids into a sprint with a start/end date; snapshot committed estimates when starting. Order backlog issues and move selected ids into a sprint with a start/end date; snapshot committed estimates when starting. Files: `features/backlog_and_sprint_commitment.py`, `templates/backlog_and_sprint_commitment.html` 2. Render a sprint board and record scope added or removed after start without rewriting the original commitment. Render a sprint board and record scope added or removed after start without rewriting the original commitment. Files: `features/backlog_and_sprint_commitment.py` 3. Exercise the acceptance fixture Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Adding a five-point issue mid-sprint appears as scope added, not original commitment. Then check: An issue cannot belong to two active sprints. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_backlog_and_sprint_commitment.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Adding a five-point issue mid-sprint appears as scope added, not original commitment. - [ ] An issue cannot belong to two active sprints. ### Watch out - Current estimates cannot reconstruct historical sprint scope. ## Phase 4 · Close and report Close and report for Jira: Close a sprint with an explicit choice to return unfinished issues to backlog or move them to a named future sprint. ### Steps 1. Close a sprint with an explicit choice to return unfinished issues to backlog or move them to a named future sprint. Close a sprint with an explicit choice to return unfinished issues to backlog or move them to a named future sprint. Files: `features/close_and_report.py`, `templates/close_and_report.html` 2. Compute completion and daily remaining points from dated events; label this a simple project report. Compute completion and daily remaining points from dated events; label this a simple project report. Files: `features/close_and_report.py` 3. Exercise the acceptance fixture Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Closing moves unfinished work exactly once and preserves completed issue history. Then check: A reopened issue increases remaining work on its reopen day. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_close_and_report.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Closing moves unfinished work exactly once and preserves completed issue history. - [ ] A reopened issue increases remaining work on its reopen day. ### Watch out - Velocity is a team planning measure; do not turn it into an individual performance score. ## Phase 5 · Portable delivery and clean-start proof Finish the Jira replacement with a documented first-run path and a recoverable export. ### Steps 1. Write the user-facing runbook Document prerequisites, every configuration variable, data locations and the three domain workflows: Issue keys and workflow; Backlog and sprint commitment; Close and report. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. Files: `README.md`, `.env.example` 2. Create and rehearse a recoverable backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for jira. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. Files: `OPERATIONS.md`, `scripts/backup.py` 3. Reproduce the first-run experience Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Files: `README.md`, `verification.md` ```sh python -m pip install -r requirements.txt python -m unittest discover -s test ``` ### Done when - [ ] A new folder reaches the documented fixture outcome using only README instructions. - [ ] A backup restored in isolation preserves the proof data and can be opened. ### Watch out - Export without an import or restore rehearsal is not verified portability. ## Not in this build - This is a focused issue backlog with explicit workflow transitions and sprint history; full Jira feature parity, vendor hosting and support are not included. - the Atlassian Marketplace and its long tail of organization-specific apps - deep two-way integrations with source control, chat, support, and CI systems - advanced roadmaps, reporting, automation, and cross-project dependency planning - enterprise identity, permissions, audit, data residency, and support guarantees - migration fidelity for years of custom fields, workflows, links, and issue history ## After v1, if you want it - Extend close and report only after the fixture and recovery checks pass. - Before adding another integration, document its credentials, limits, cost and failure behavior with primary-source links.
.env.example
# Copy to .env and fill in. Never commit .env; this file documents it. # Required. A new private folder this application creates on first run; never serve it as static files. DATA_DIR=./data/jira # Required · secret. Generate with python -c "import secrets; print(secrets.token_hex(32))" and save only in .env. SECRET_KEY=replace-with-a-random-secret # Required. Use indie for loopback-only personal work. Product mode must refuse to start until owner login and the deployment gates are configured. APP_MODE=indie # Required. The origin used for local forms and links; replace with the chosen HTTPS origin in product mode. SITE_URL=http://127.0.0.1:5000
PRODUCT.md
# Jira · product brief ## Problem Issues, workflows, a backlog, sprints, and a board are a credible multi-day build for one small team. The replacement stops being small when Jira is the company's system of record: custom schemes, permissions, automation, reporting, marketplace apps, two-way integrations, and years of workflow history are the product people are actually paying not to migrate. ## Product outcome An operated version of a focused issue backlog with explicit workflow transitions and sprint history, with authorized access, restore evidence and honest scope limits. ## Target user A builder who needs a maintainable product foundation, not a one-off demo. ## Required capabilities - Docker - PostgreSQL - self-hosted server - email credentials for invitations and notifications - GitHub token for optional repository sync ## Explicit non-goals for v1 - This is a focused issue backlog with explicit workflow transitions and sprint history; full Jira feature parity, vendor hosting and support are not included. - the Atlassian Marketplace and its long tail of organization-specific apps - deep two-way integrations with source control, chat, support, and CI systems - advanced roadmaps, reporting, automation, and cross-project dependency planning - enterprise identity, permissions, audit, data residency, and support guarantees - migration fidelity for years of custom fields, workflows, links, and issue history ## Success criteria - Two concurrent creates receive distinct APP keys. - Adding a five-point issue mid-sprint appears as scope added, not original commitment. - Closing moves unfinished work exactly once and preserves completed issue history. - A private-data authorization check passes using a second identity. - An off-host restore drill has a date, observed result and recovery time in OPERATIONS.md. - README names the excluded vendor capabilities and actual provider/hosting costs.
BRIEF.md
# Build brief · Jira The one-shot brief this plan expands. `BUILD_PLAN.md` (or `MILESTONES.md`) is the same sequence broken into steps and checks; where the two disagree, the plan wins. Build me a focused issue backlog with explicit workflow transitions and sprint history as a bounded replacement for Jira. Build it in phases in the order below. Do not write the whole product in one pass. Finish the current phase, run its Done when checks, fix failures, then continue. Indie mode completes Phases 1-5. Phase 6 is required before shared or public deployment. ### Stack (fixed, do not substitute) - Runtime: Python 3.12+ and Flask. A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. - Storage: SQLite through Python sqlite3. Local ownership with explicit transactions and a portable backup path. - Interface: Jinja HTML templates, CSS and vanilla JavaScript. Implement the specified screens directly with labelled controls and progressive enhancement. - Verification: Python unittest and browser acceptance fixtures. Check invariants and the actual user workflow before the next phase. ### Data model (create this before Phase 1) - projects(id,key) - issues(id,project_id,number,title,type,status,estimate,sprint_id,revision) - transitions(from_status,to_status) - sprints(id,project_id,start,end,state) - events(id,issue_id,at,kind,payload) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. ### Prerequisites and configuration - Python 3.12 or newer and a terminal: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. Cost: Python is free; this local prototype requires no hosting subscription. - A current desktop browser and text editor: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. Verify: You can create a text file in the project folder and open browser developer tools. Cost: No paid service required for this local step. - Jira acceptance sample: Create synthetic sample data before implementation: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. Cost: No paid service required for this local step. - Confirm the bounded replacement: The deliverable is a focused issue backlog with explicit workflow transitions and sprint history. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. Cost: No paid service required for this local step. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL. Ship .env.example, replace placeholders and exclude secrets from git. ### Phase 1 · Local foundation and data contract Build: Create the runnable local foundation for a focused issue backlog with explicit workflow transitions and sprint history, including the real schema and acceptance fixture. - Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Commands, after creating the named files: `python -m venv .venv`; `python -m pip install Flask Flask-WTF python-dotenv waitress tzdata`; `python -m pip freeze > requirements.txt`; `python -m flask --app app run --host 127.0.0.1`. - For database-backed state create schema.sql and db.py using this model: projects(id,key); issues(id,project_id,number,title,type,status,estimate,sprint_id,revision); transitions(from_status,to_status); sprints(id,project_id,start,end,state); events(id,issue_id,at,kind,payload). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Re-running init must not erase data. Commands, after creating the named files: `python manage.py init`; `python manage.py seed`. - Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. - Trap: The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. Done when: The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. Restarting preserves the seeded records or canonical files; running init again deletes nothing. A cross-origin state-changing request to an admin route is refused. Do not build yet: Do not start issue keys and workflow until these checks pass. ### Phase 2 · Issue keys and workflow Build: Issue keys and workflow for Jira: Allocate monotonically increasing issue numbers per project in a transaction; support bug, story and task types. - Allocate monotonically increasing issue numbers per project in a transaction; support bug, story and task types. - Define allowed transitions as data and validate them server-side; record status events with the old and new value. - Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Two concurrent creates receive distinct APP keys. Then check: A forbidden transition returns a reason and leaves status unchanged. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Never derive issue numbers from the current row count. Done when: Two concurrent creates receive distinct APP keys. A forbidden transition returns a reason and leaves status unchanged. Do not build yet: Do not start backlog and sprint commitment until these checks pass. ### Phase 3 · Backlog and sprint commitment Build: Backlog and sprint commitment for Jira: Order backlog issues and move selected ids into a sprint with a start/end date; snapshot committed estimates when starting. - Order backlog issues and move selected ids into a sprint with a start/end date; snapshot committed estimates when starting. - Render a sprint board and record scope added or removed after start without rewriting the original commitment. - Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Adding a five-point issue mid-sprint appears as scope added, not original commitment. Then check: An issue cannot belong to two active sprints. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Current estimates cannot reconstruct historical sprint scope. Done when: Adding a five-point issue mid-sprint appears as scope added, not original commitment. An issue cannot belong to two active sprints. Do not build yet: Do not start close and report until these checks pass. ### Phase 4 · Close and report Build: Close and report for Jira: Close a sprint with an explicit choice to return unfinished issues to backlog or move them to a named future sprint. - Close a sprint with an explicit choice to return unfinished issues to backlog or move them to a named future sprint. - Compute completion and daily remaining points from dated events; label this a simple project report. - Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Closing moves unfinished work exactly once and preserves completed issue history. Then check: A reopened issue increases remaining work on its reopen day. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Velocity is a team planning measure; do not turn it into an individual performance score. Done when: Closing moves unfinished work exactly once and preserves completed issue history. A reopened issue increases remaining work on its reopen day. Do not build yet: Do not start portable delivery and clean-start proof until these checks pass. ### Phase 5 · Portable delivery and clean-start proof Build: Finish the Jira replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Issue keys and workflow; Backlog and sprint commitment; Close and report. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. - Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for jira. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. - Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Commands, after creating the named files: `python -m pip install -r requirements.txt`; `python -m unittest discover -s test`. - Trap: Export without an import or restore rehearsal is not verified portability. Done when: A new folder reaches the documented fixture outcome using only README instructions. A backup restored in isolation preserves the proof data and can be opened. Do not build yet: Do not start operate and share with access controls until these checks pass. ### Phase 6 · Operate and share with access controls (product-builder only) Build: Product-builder only: make a focused issue backlog with explicit workflow transitions and sprint history operable for its stated audience before allowing remote access. - Add owner/member/viewer authorization as appropriate, password hashes through Werkzeug, expiring server-side sessions, CSRF and login rate limits. Add users, sessions and audit schema migrations plus an owner-init command prompting securely for its password. Enforce ownership on every private read/write/download and fail closed when product setup is incomplete. Existing learner or admin identities must use this same boundary. - Serve app:app with Waitress on loopback behind Caddy HTTPS. Configure trusted proxy headers narrowly, Secure/HttpOnly/SameSite cookies, upload limits, request ids and structured logs without private content. Run background jobs as a separate supervised process when the domain workflow requires them. Commands, after creating the named files: `waitress-serve --listen=127.0.0.1:5000 app:app`. - Add a scheduled encrypted off-host backup using this procedure: Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for jira. Monitor health, disk space, failed jobs and backup age. Stop the service to test an alert; rehearse recovery with outbound effects disabled and record recovery time. Rotate any exposed credentials and require reconciliation before resuming queues. - Trap: Product mode is additional engineering, not a switch that makes a local prototype production-ready. Done when: An unauthenticated visitor cannot read private records, download private files or mutate the admin surface. A viewer cannot mutate data by making a direct request, and guessed ids cannot cross ownership boundaries. Stopping the service triggers the configured alert and the latest off-host backup restores the fixture in isolation. Do not build yet: Do not add new providers or vendor-scale features until the release gates are recorded. ### Out of scope (and why) - This is a focused issue backlog with explicit workflow transitions and sprint history; full Jira feature parity, vendor hosting and support are not included. - the Atlassian Marketplace and its long tail of organization-specific apps: retain the paid product if this capability is essential; it is outside this bounded build. - deep two-way integrations with source control, chat, support, and CI systems: retain the paid product if this capability is essential; it is outside this bounded build. - advanced roadmaps, reporting, automation, and cross-project dependency planning: retain the paid product if this capability is essential; it is outside this bounded build. - enterprise identity, permissions, audit, data residency, and support guarantees: retain the paid product if this capability is essential; it is outside this bounded build. - migration fidelity for years of custom fields, workflows, links, and issue history: retain the paid product if this capability is essential; it is outside this bounded build. ### README must contain - Exact install, configure, initialize, start, test and recovery commands for a clean folder. - The schema, fixture, acceptance results, private data locations and export format. - Every prerequisite and secret source, actual running costs and deliberately excluded capabilities. - An honest distinction between tests actually run and checks still awaiting real credentials or deployment. - Dependency documentation reviewed 2026-09-05: https://flask.palletsprojects.com/en/stable/installation/ ; https://docs.python.org/3/library/sqlite3.html ; https://flask-wtf.readthedocs.io/en/1.2.x/csrf/ ; https://docs.pylonsproject.org/projects/waitress/en/stable/usage.html. Recheck before upgrading; freeze the versions actually tested.
ARCHITECTURE.md
# Architecture · Jira ## Stack | Part | Choice | Why | | --- | --- | --- | | Runtime | Python 3.12+ and Flask | A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. | | Storage | SQLite through Python sqlite3 | Local ownership with explicit transactions and a portable backup path. | | Interface | Jinja HTML templates, CSS and vanilla JavaScript | Implement the specified screens directly with labelled controls and progressive enhancement. | | Verification | Python unittest and browser acceptance fixtures | Check invariants and the actual user workflow before the next phase. | ## Modules Each module has one owner concern and a documented way to replace it. | Module | Owns | How to replace it | | --- | --- | --- | | Data and identity | projects(id,key); issues(id,project_id,number,title,type,status,estimate,sprint_id,revision); transitions(from_status,to_status); sprints(id,project_id,start,end,state); events(id,issue_id,at,kind,payload) | Keep stable ids and a versioned repository interface; migrate storage behind it with a fixture round-trip. | | Issue keys and workflow | Allocate monotonically increasing issue numbers per project in a transaction; support bug, story and task types. | Keep the acceptance contract: Two concurrent creates receive distinct APP keys. Replace only this module after replaying its fixture; preserve ids and existing records. | | Backlog and sprint commitment | Order backlog issues and move selected ids into a sprint with a start/end date; snapshot committed estimates when starting. | Keep the acceptance contract: Adding a five-point issue mid-sprint appears as scope added, not original commitment. Replace only this module after replaying its fixture; preserve ids and existing records. | | Close and report | Close a sprint with an explicit choice to return unfinished issues to backlog or move them to a named future sprint. | Keep the acceptance contract: Closing moves unfinished work exactly once and preserves completed issue history. Replace only this module after replaying its fixture; preserve ids and existing records. | | Operations | Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for jira. | Change host or backup destination only after an isolated restore and authorization check. | ## Configuration Every runtime setting is an environment variable documented in `.env.example`, validated at startup, with a safe local default wherever one exists. - `DATA_DIR` · required · A new private folder this application creates on first run; never serve it as static files. - `SECRET_KEY` · required, secret · Generate with python -c "import secrets; print(secrets.token_hex(32))" and save only in .env. - `APP_MODE` · required · Use indie for loopback-only personal work. Product mode must refuse to start until owner login and the deployment gates are configured. - `SITE_URL` · required · The origin used for local forms and links; replace with the chosen HTTPS origin in product mode. ## Production baseline - Security: least privilege, input validation at every boundary, secret redaction in logs, rate limits on abuse-prone paths, no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore procedures that have been exercised. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, timeouts. - Observability: structured logs with request or operation ids, an error-tracking hook, and health and readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, one end-to-end test of the critical path. ## Decision records For each dependency in the stack table, keep a short note: why it was chosen, its failure mode, and how it is replaced. Do not add infrastructure until a requirement in `PRODUCT.md` justifies it.
AGENTS.md
# Agent instructions · Jira product build - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. The stack is fixed: Python 3.12+ and Flask, SQLite through Python sqlite3, Jinja HTML templates, CSS and vanilla JavaScript, Python unittest and browser acceptance fixtures. - Implement milestone by milestone from `MILESTONES.md`; keep each change reviewable and leave the application runnable at every commit. - Treat authentication, payments, encryption, imports, webhooks and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a check pass. - Put every external service behind an interface with a deterministic fake for tests. - Add migrations and rollback or recovery notes for every persistent data change. - Log useful operational context without credentials, tokens, passwords or personal data. - Update documentation and run every check before completing a milestone. ## Known traps - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. - Never derive issue numbers from the current row count. - Current estimates cannot reconstruct historical sprint scope. - Velocity is a team planning measure; do not turn it into an individual performance score. - Export without an import or restore rehearsal is not verified portability. - Product mode is additional engineering, not a switch that makes a local prototype production-ready.
MILESTONES.md
# Delivery milestones · Jira Estimated effort: **multi-day** for the indie phases; the production-only milestones add the trust and operability layer. ## M1 · Local foundation and data contract Create the runnable local foundation for a focused issue backlog with explicit workflow transitions and sprint history, including the real schema and acceptance fixture. ### Steps 1. Create and start the local application Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Files: `app.py`, `requirements.txt`, `.env.example`, `.gitignore` ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` 2. Implement storage and seed the named fixture For database-backed state create schema.sql and db.py using this model: projects(id,key); issues(id,project_id,number,title,type,status,estimate,sprint_id,revision); transitions(from_status,to_status); sprints(id,project_id,start,end,state); events(id,issue_id,at,kind,payload). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Re-running init must not erase data. Files: `schema.sql`, `db.py`, `manage.py`, `fixtures/README.md` ```sh python manage.py init python manage.py seed ``` 3. Protect the local request boundary Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. Files: `app.py`, `templates/base.html`, `test/test_foundation.py` ### Done when - [ ] The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. - [ ] Restarting preserves the seeded records or canonical files; running init again deletes nothing. - [ ] A cross-origin state-changing request to an admin route is refused. ### Watch out - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. ## M2 · Issue keys and workflow Issue keys and workflow for Jira: Allocate monotonically increasing issue numbers per project in a transaction; support bug, story and task types. ### Steps 1. Allocate monotonically increasing issue numbers per project in a transaction; support bug, story and task types. Allocate monotonically increasing issue numbers per project in a transaction; support bug, story and task types. Files: `features/issue_keys_and_workflow.py`, `templates/issue_keys_and_workflow.html` 2. Define allowed transitions as data and validate them server-side; record status events with the old and new value. Define allowed transitions as data and validate them server-side; record status events with the old and new value. Files: `features/issue_keys_and_workflow.py` 3. Exercise the acceptance fixture Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Two concurrent creates receive distinct APP keys. Then check: A forbidden transition returns a reason and leaves status unchanged. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_issue_keys_and_workflow.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Two concurrent creates receive distinct APP keys. - [ ] A forbidden transition returns a reason and leaves status unchanged. ### Watch out - Never derive issue numbers from the current row count. ## M3 · Backlog and sprint commitment Backlog and sprint commitment for Jira: Order backlog issues and move selected ids into a sprint with a start/end date; snapshot committed estimates when starting. ### Steps 1. Order backlog issues and move selected ids into a sprint with a start/end date; snapshot committed estimates when starting. Order backlog issues and move selected ids into a sprint with a start/end date; snapshot committed estimates when starting. Files: `features/backlog_and_sprint_commitment.py`, `templates/backlog_and_sprint_commitment.html` 2. Render a sprint board and record scope added or removed after start without rewriting the original commitment. Render a sprint board and record scope added or removed after start without rewriting the original commitment. Files: `features/backlog_and_sprint_commitment.py` 3. Exercise the acceptance fixture Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Adding a five-point issue mid-sprint appears as scope added, not original commitment. Then check: An issue cannot belong to two active sprints. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_backlog_and_sprint_commitment.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Adding a five-point issue mid-sprint appears as scope added, not original commitment. - [ ] An issue cannot belong to two active sprints. ### Watch out - Current estimates cannot reconstruct historical sprint scope. ## M4 · Close and report Close and report for Jira: Close a sprint with an explicit choice to return unfinished issues to backlog or move them to a named future sprint. ### Steps 1. Close a sprint with an explicit choice to return unfinished issues to backlog or move them to a named future sprint. Close a sprint with an explicit choice to return unfinished issues to backlog or move them to a named future sprint. Files: `features/close_and_report.py`, `templates/close_and_report.html` 2. Compute completion and daily remaining points from dated events; label this a simple project report. Compute completion and daily remaining points from dated events; label this a simple project report. Files: `features/close_and_report.py` 3. Exercise the acceptance fixture Use APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Check: Closing moves unfinished work exactly once and preserves completed issue history. Then check: A reopened issue increases remaining work on its reopen day. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_close_and_report.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Closing moves unfinished work exactly once and preserves completed issue history. - [ ] A reopened issue increases remaining work on its reopen day. ### Watch out - Velocity is a team planning measure; do not turn it into an individual performance score. ## M5 · Portable delivery and clean-start proof Finish the Jira replacement with a documented first-run path and a recoverable export. ### Steps 1. Write the user-facing runbook Document prerequisites, every configuration variable, data locations and the three domain workflows: Issue keys and workflow; Backlog and sprint commitment; Close and report. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. Files: `README.md`, `.env.example` 2. Create and rehearse a recoverable backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for jira. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. Files: `OPERATIONS.md`, `scripts/backup.py` 3. Reproduce the first-run experience Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Files: `README.md`, `verification.md` ```sh python -m pip install -r requirements.txt python -m unittest discover -s test ``` ### Done when - [ ] A new folder reaches the documented fixture outcome using only README instructions. - [ ] A backup restored in isolation preserves the proof data and can be opened. ### Watch out - Export without an import or restore rehearsal is not verified portability. ## M6 · Operate and share with access controls (production only) Product-builder only: make a focused issue backlog with explicit workflow transitions and sprint history operable for its stated audience before allowing remote access. ### Steps 1. Establish owner access before exposure Add owner/member/viewer authorization as appropriate, password hashes through Werkzeug, expiring server-side sessions, CSRF and login rate limits. Add users, sessions and audit schema migrations plus an owner-init command prompting securely for its password. Enforce ownership on every private read/write/download and fail closed when product setup is incomplete. Existing learner or admin identities must use this same boundary. Files: `ARCHITECTURE.md`, `OPERATIONS.md` 2. Deploy a monitored service Serve app:app with Waitress on loopback behind Caddy HTTPS. Configure trusted proxy headers narrowly, Secure/HttpOnly/SameSite cookies, upload limits, request ids and structured logs without private content. Run background jobs as a separate supervised process when the domain workflow requires them. Files: `Caddyfile`, `OPERATIONS.md` ```sh waitress-serve --listen=127.0.0.1:5000 app:app ``` 3. Rehearse loss and recovery Add a scheduled encrypted off-host backup using this procedure: Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for jira. Monitor health, disk space, failed jobs and backup age. Stop the service to test an alert; rehearse recovery with outbound effects disabled and record recovery time. Rotate any exposed credentials and require reconciliation before resuming queues. Files: `OPERATIONS.md`, `release-checklist.md` ### Done when - [ ] An unauthenticated visitor cannot read private records, download private files or mutate the admin surface. - [ ] A viewer cannot mutate data by making a direct request, and guessed ids cannot cross ownership boundaries. - [ ] Stopping the service triggers the configured alert and the latest off-host backup restores the fixture in isolation. ### Watch out - Product mode is additional engineering, not a switch that makes a local prototype production-ready.
OPERATIONS.md
# Operations · Jira ## Backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for jira. ## Restore Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: APP-1 bug and APP-2 story, a seven-day sprint and a forbidden done-to-in-progress transition. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. Do a restore drill before the first real user, and write the date here when it passes. ## Monitoring Check HTTP availability, free disk, backup age and domain failures for Issue keys and workflow, Backlog and sprint commitment, Close and report. Alert without logging private payloads. ## Incident checklist Pause outbound jobs and public intake as appropriate, preserve redacted diagnostics, restore an isolated verified backup, rotate affected credentials and reconcile uncertain effects before reopening. 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified backup when needed. 5. Document the root cause, the remediation and the regression test. ## Release gate - [ ] Two concurrent creates receive distinct APP keys. - [ ] Adding a five-point issue mid-sprint appears as scope added, not original commitment. - [ ] Closing moves unfinished work exactly once and preserves completed issue history. - [ ] A private-data authorization check passes using a second identity. - [ ] An off-host restore drill has a date, observed result and recovery time in OPERATIONS.md. - [ ] README names the excluded vendor capabilities and actual provider/hosting costs. ## Launch constraint Do not market omitted Jira capabilities as implemented. The non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
.env.example
# Copy to .env and fill in. Never commit .env; this file documents it. # Required. A new private folder this application creates on first run; never serve it as static files. DATA_DIR=./data/jira # Required · secret. Generate with python -c "import secrets; print(secrets.token_hex(32))" and save only in .env. SECRET_KEY=replace-with-a-random-secret # Required. Use indie for loopback-only personal work. Product mode must refuse to start until owner login and the deployment gates are configured. APP_MODE=indie # Required. The origin used for local forms and links; replace with the chosen HTTPS origin in product mode. SITE_URL=http://127.0.0.1:5000
$ choose a build depth, inspect the files, then open the complete pack in your agent
A Jira ticket is often connected to a pull request, deployment, support case, audit trail, roadmap, and three teams' reporting rules. Rebuilding the visible board is straightforward; replacing the shared organizational contract around issue IDs, permissions, automations, and history is not. The subscription buys continuity and integration upkeep more than draggable cards.
xthe Atlassian Marketplace and its long tail of organization-specific apps
xdeep two-way integrations with source control, chat, support, and CI systems
xadvanced roadmaps, reporting, automation, and cross-project dependency planning
xenterprise identity, permissions, audit, data residency, and support guarantees
xmigration fidelity for years of custom fields, workflows, links, and issue history
share on X ↗"I just replaced Jira ($7.91/mo) with one prompt"
Don't feel like building it? These folks already made it free.
PlaneThe closest modern Jira-shaped escape hatch; the self-hosted stack is not a weekend hobbyopen source↗
OpenProjectThe enterprise project suite; free in money, expensive in menusopen source↗
RedmineIssue tracking, time sheets, Gantt, and wikis from the era when software admitted it needed configurationopen source↗all 5 free alternatives to Jira →· no votes, no pay-to-list · just what's real
Jira pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| free | $0/user | $0/user | Up to 10 users, 2 GB storage, 100 automation rule runs/month; unlimited goals, projects, tasks and forms |
| standard | — | $7.91/user | Up to 100,000 users, 250 GB storage, 1,700 automation runs/month and 25 Rovo credits/user/month |
| premium | — | $14.54/user | Up to 100,000 users, unlimited storage, 1,000 automation runs per paid user/month and 70 Rovo credits/user/month |
| enterprise | custom | — | Annual custom plan with unlimited automation, up to 150 sites, 150 Rovo credits/user/month and Atlassian Guard Standard |
free tierUp to 10 users, 2 GB storage and 100 automation rule runs/month
billingmonthly + annual (annual saves up to 17%); Enterprise annual only; monthly pricing is progressive by user count
hidden costsThe per-user rate changes with team size, so the bill is not a simple headline-price multiplication. Marketplace apps, Guard beyond included entitlements and other Atlassian products add cost. Rovo credits currently do not incur automatic overage charges; Atlassian says it will provide notice before changing that.
verified 2026-08-14 · source ↗
Is Jira free?
The Free plan covers up to 10 users with 2 GB of storage and 100 automation rule runs per month. Paid is Standard at $7.91/mo (checked 2026-08-14).
Vibecode Jira
Kinda. The core of Jira is buildable in a weekend with the prompt on this page, but there are real gaps: the Atlassian Marketplace and its long tail of organization-specific apps, deep two-way integrations with source control, chat, support, and CI systems. Read the honest list above before committing.
How much does Jira cost?
Jira costs about $7.91/month (Standard, checked 2026-08-14), which is $94.92 per year.
What do I lose by replacing Jira?
Honestly: the Atlassian Marketplace and its long tail of organization-specific apps; deep two-way integrations with source control, chat, support, and CI systems; advanced roadmaps, reporting, automation, and cross-project dependency planning; enterprise identity, permissions, audit, data residency, and support guarantees; migration fidelity for years of custom fields, workflows, links, and issue history. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Jira?
Yes: Plane (The closest modern Jira-shaped escape hatch; the self-hosted stack is not a weekend hobby) OpenProject (The enterprise project suite; free in money, expensive in menus) Redmine (Issue tracking, time sheets, Gantt, and wikis from the era when software admitted it needed configuration) All 5 curated free alternatives are at vibecodeit.com/jira/alternatives. The prompt is for when you want it exactly your way.