Product proposal · Synthetic data only
RefineBrief inside Jira
This review page contains actual captures of the local product prototype and text descriptions. It does not require JavaScript, login, an API connection or an active development tunnel.
The interactive version uses in-memory examples only. No analysis, source refresh or real Jira issue is created. Reloading resets the sample.
Updated lifecycle proposal · 27 September 2026. Requests uses the confirmed open-only query and its page totals. Partial and full publication keep a demand open. Move to history is explicit and warns about unpublished items. Reopening preserves results, edited drafts and links without starting analysis. The interactive preview contains the latest behavior; the reference captures below illustrate selected states, not an exhaustive screen inventory.
History and reopening
Publication progress comes from individual recorded links. Moving to history with a Jira link does not mean every item was published. Reopening returns Pending, with retained work available for review and published items protected from republication.
Requests: open work and personal resume
Start a demand, resume your last open request, or open another project request. The personal highlight does not reorder the work of other users.
Open full-resolution screenshot
Create a demand
Describe the problem and outcome, select Bug, Task, Feature or Spike, and choose sources and a template. Request intent is separate from the Jira issue type.
Open full-resolution screenshot
Prepare before analysis
Saving the request does not start analysis. The current ACTIVE map remains usable when newer code is available. Starting analysis is a separate confirmation.
Open full-resolution screenshot
Review results and code evidence
Review suggested work and acceptance criteria alongside source, branch, template, file, lines and the commit from the same analysis execution. Code excerpts are expandable. Draft edits are separate from destructive demand edits.
Open full-resolution screenshot
Partial publication
The first suggestion has the synthetic recorded Jira key DEMO-41. The second suggestion is still a draft with its own confirmation. Each creation targets the linked project backlog; there is no bulk publish, board or sprint selector.
Open full-resolution screenshot
Project setup: code sources
Repository updates use a compact disclosure. ACTIVE maps remain usable. Source configuration and administrative actions sit behind contextual details.
Open full-resolution screenshot
Project setup: templates
Review the structure and guidance of the active template. Detailed administration is secondary to everyday refinement.
Open full-resolution screenshot
Project setup: connection and defaults
The linked project and fixed backlog destination are summaries, with support details and shared web defaults separated into disclosures.
Open full-resolution screenshot