Project Management is OpenTechnologyApp's built-in template for the shape most teams actually run: outside requests come in somewhere, someone decides what's worth doing, and only then does it become tracked delivery work. The template keeps those two things in genuinely separate queues, not just separate views of the same list.
What it tracks
| Queue | What lives there |
|---|---|
| Request Intake | The public portal lands here — no login required for the requester. Every request is triaged and approved before it becomes real work. |
| Initiatives & Epics | The canonical parent layer — every Epic lives here once |
| Product Backlog | Approved work, not yet committed to a sprint |
| Active Sprint | Committed work in flight |
| Risks & Milestones | Tracked separately from delivery work, so a risk doesn't get lost inside a sprint board |
| Weekly Reports | One rollup item per cycle |
The portal is the actual differentiator
Turn on the portal for Request Intake and external stakeholders — clients, other teams, anyone without an account — get a clean submission form. What they submit lands in Intake, goes through Triage Status (New → In Triage → Approved/Rejected/Duplicate) and a Decision field, and only an approved request becomes real backlog work. A rejected or duplicate request stays visible as a closed record, not deleted — the intake trail is kept, not erased.
That structural separation is the point: nothing submitted externally can jump straight into an active sprint. It has to clear triage first, same as anything else.
Ten automations, all state-changing
No comment-only automations here — every one of the ten actually moves something:
- A compliance-flagged request jumps to urgent automatically
- An approved triage decision flips the item to in-progress
- A rejected or duplicate request closes itself
- Committed work moves to in-progress
- A blocked item jumps to high priority
- Critical severity forces urgent priority
- A Health field set to Red forces urgent priority
- Overdue work escalates
- An item with no update in 7 days gets flagged for review
Two dashboards, and one deliberate thing they don't claim
Portfolio & Sprint covers the delivery side: an Epic → Work Item hierarchy tree, health-by-strategic-alignment breakdowns, a due-date calendar, and a chart of items created over time. Intake & Backlog covers the triage side: requests by triage status, by category, by type.
Worth being precise about one widget: the "Items Created Over Time" chart is exactly that — a creation-rate line, not sprint velocity. Real velocity needs completed story points tracked against a completed sprint's actual dates, and this template doesn't have sprint entities with start/end dates yet — Sprint here is a category field (Current Sprint / Next Sprint / Backlog), not a full sprint record. The dashboard doesn't claim a number it can't back up.
Same honesty applies to the hierarchy: Initiative exists as an item type, but the working parent-child link today is two levels — Epic → Work Item. A true three-level Initiative → Epic → Work Item hierarchy isn't wired into the seeder yet.
No playbooks yet
Unlike IT Device Audit's five, Project Management doesn't ship playbooks today. The queue and field structure is there for a triage runbook or a sprint-planning checklist — building one is on you for now.
Get it
New Project → Project Management from the template picker at opentechnologyapp.com. Six queues, fourteen item types, ten automations, and two dashboards — turn on the portal on Request Intake when you're ready for outside requests to land somewhere real.