# Atlassian Platform Recommendations
# Cold Bore Ballistics, LLC

**Date:** 2026-06-04
**Scope:** Jira Software · Jira Service Management · Confluence
**Site:** `coldboreballisticsllc.atlassian.net`

> Recommendations based on live instance state, the Architecture Reference, and the
> CBB acquisition lens. Prioritized by impact — highest-value items first within each
> section.

---

## Table of Contents

1. [Immediate Gaps](#1-immediate-gaps)
2. [Jira — Workflow and Board Improvements](#2-jira--workflow-and-board-improvements)
3. [Confluence — Content Gaps](#3-confluence--content-gaps)
4. [ESUP — Support Pipeline Maturity](#4-esup--support-pipeline-maturity)
5. [Standard Upgrade Decision Point](#5-standard-upgrade-decision-point)
6. [Acquisition-Specific Observations](#6-acquisition-specific-observations)
7. [Prioritized Action List](#7-prioritized-action-list)

---

## 1. Immediate Gaps

**Triage ESUP-1 through ESUP-5 — Jira Service Management**
ESUP-5 ("Twist text RH/LH barely readable") is sitting at "Waiting for support" — that
is a real UI bug waiting on you as the agent, not the reporter. It should be triaged:
either promoted to a DOPE issue (likely `Bug, UI & Navigation, Highest, fix version 1.0.0`)
or explicitly closed. The same applies to ESUP-1 through -4. ESUP as an untriaged inbox
undermines its purpose as a triage gate.


---

## 2. Jira — Workflow and Board Improvements

**Add the `launch-blocking` label to all qualifying DOPE v1.0.0 issues — Jira Software**
DOPE-1 (v1.0.0 Launch Epic) has no description and no child issues linked. The
launch-blocking issues (WeatherFlow compass semantics, Niimbot B21 Pro hardware
validation, etc.) need to be epically linked and labeled. Without this,
`JQL: labels = launch-blocking` returns nothing meaningful — and that query is exactly
what a buyer's technical diligence will run to assess release readiness.

**Enable the "Waiting on Hardware" board column on DOPE — Jira Software**
The Architecture Reference specifies this column. Given that multiple issues (B21 Pro,
WeatherFlow) are blocked on physical hardware right now, this column is actively useful —
not a future-state concern.

**Fill in the DOPE-1 Epic description — Jira Software**
An empty description on the v1.0.0 Launch Epic is conspicuous in any audit. Minimum
content: what 1.0.0 means, what is in scope, rough target timeline, and a link to the
Release Checklist in CLAUDE.md/ScopeDOPE_SDLC.md.

**Add hardware target labels to DOPE issues — Jira Software**
Multiple DOPE issues are hardware-specific (Niimbot B1, B21 Pro, WeatherFlow Tactical,
BTMETER BT-100) but there is no machine-queryable way to filter by hardware target. The
Repository custom field covers repos; nothing covers devices. Structured labels
(`hw:weatherflow_tactical`, `hw:niimbot_b21_pro`, etc.) require no schema change and are
free-plan-friendly. Promote to a custom field on Standard upgrade if the list grows.

---

## 3. Confluence — Content Gaps

**Populate the CBBOPS Infrastructure Overview page — Confluence**
The page exists but should contain substantive content: the Azure architecture, IPsec
site-to-site VPN configuration, nginx setup, and where Terraform lives (`cbb-infra`). This is one
of the highest-value acquisition artifacts — it lets a buyer's engineering team understand
and operate the infrastructure without the founder present.

**Populate the CBBOPS Legal and IP Overview page — Confluence**
This page should list trademark filings, copyright registrations, and patent status with
filing numbers and current status. It should be the single place where IP ownership is
documented for due diligence — not scattered across OneDrive folders a buyer cannot
navigate without guidance.

**Create a "Hardware Protocol Reference" page in SCOPE — Confluence**
Confirmed BLE protocol details for the WeatherFlow Tactical and Niimbot B1 exist in
memory and OneDrive, but are not operationally accessible during development. A SCOPE
page covering UUIDs, characteristic IDs, and frame formats gives any future developer
(or buyer's engineer) everything needed to work the BLE stack without re-reverse-engineering
it. This is not trade-secret content — it is operational protocol documentation.

**Create a "Current Release Status" page in SCOPE — Confluence**
One page showing: current version (`0.9.6-beta4`), active branch, launch-blocking issues,
what is in flight. Updated at the start/end of each session. Low effort; high acquisition
signal — it answers "where are you in the development cycle?" without requiring a walkthrough.

---

## 4. ESUP — Support Pipeline Maturity

**Configure a basic SLA on ESUP — Jira Service Management**
Even a simple "first response within 3 days" SLA gives the support queue a clock. This
demonstrates operational process maturity to an acquirer — a support inbox with no SLA
reads as an unmanaged email folder. Configurable manually in ESUP project settings → SLAs.

**Add an auto-assign automation rule in ESUP — Jira Service Management**
Free plan allows 500 automation runs/month. A single rule — "when issue created in ESUP,
assign to admin@coldboreballisticsllc.com" — ensures nothing sits unassigned. Without it,
every new ESUP ticket lands with `Assignee: None` and the queue only works if checked
actively. One rule eliminates that risk entirely.

---

## 5. Standard Upgrade Decision Point

The Free plan is the right call through the pre-1.0.0 phase. The upgrade trigger is
specific: **the first external hire or contractor who needs Jira access.** At that point,
real permission isolation is required before their account is created.

Standard ($7.75/user/month, billed annually) unlocks the permission scheme assignment,
project role actors, and Confluence space permissions that are already staged and ready to
activate with a single `setup_atlassian.py` re-run — no migration work.

Do not upgrade before that trigger. The staged configuration means zero setup cost when
the time comes.

---

## 6. Acquisition-Specific Observations

**The Repository custom field is a strong positive.** `JQL: Repository = "scopedope-android"`
as a due-diligence query is exactly what a buyer's technical team will run. Ensure it is
populated on issues as they are created — a field that exists but is blank on most issues
signals incomplete process.

**The DOPE/CBB project separation is correct and must be maintained strictly.** In any
acquisition, the buyer will price the ScopeDOPE product line separately from CBB corporate
overhead. Clean issue separation across those two projects is a direct input to that
valuation. Product work filed in CBB or corporate work filed in DOPE muddies that line.

**The `dope-format`-stays-on-GitHub-Issues policy is acquisition-smart.** A public GitHub
issue tracker on a format spec repo signals community openness and format stability to a
technical buyer. Do not migrate it to Jira.


---

## 7. Prioritized Action List

| Priority | Action | Product | Effort |
|---|---|---|---|
| 1 | Triage ESUP-1 through ESUP-5 | Jira Service Management | 30 min |
| 2 | Fill in DOPE-1 Epic description | Jira Software | 10 min |
| 3 | Add `launch-blocking` label to qualifying DOPE issues | Jira Software | 20 min |
| 4 | Populate CBBOPS Infrastructure Overview page | Confluence | 1–2 hrs |
| 5 | Populate CBBOPS Legal and IP Overview page | Confluence | 1–2 hrs |
| 6 | Create SCOPE "Current Release Status" page | Confluence | 20 min |
| 7 | Add hardware target labels to DOPE issues | Jira Software | 20 min |
| 8 | Configure a basic ESUP SLA | Jira Service Management | 10 min |
| 9 | Create SCOPE "Hardware Protocol Reference" page | Confluence | 1 hr |

---

## Document Control

| Field | Value |
|---|---|
| **Document owner** | `jschwefel@coldboreballisticsllc.com` |
| **Classification** | Confidential (03_-_Confidential/) |
| **Location** | `OneDrive/CBB_Corporate/03_-_Confidential/Infrastructure/Atlassian/Atlassian_Recommendations.md` |
| **Cross-references** | `Atlassian_Architecture_Reference.md`; `Atlassian_Operating_Runbook.md`; `Atlassian_Rebuild_Guide.md` |
| **Created** | 2026-06-06 |
| **Last updated** | 2026-06-06 |
| **Next full review due** | 2027-06-06 |

---

## Revision Control Block

| Rev | Date | Changed By | Reviewed By | Approved By | Summary |
|-----|------|------------|-------------|-------------|---------|
| 0.9 | 2026-06-06 | jschwefel | — | — | Initial release |
