Client
3 Stripes, a Neudesic product
Year
2023
Role
Product Designer, solo on the Jira extension
Status
Clickable prototype, not released

An AI inside Jira that asks before it writes, and changes nothing until it is accepted.

Three Stripes is Neudesic’s generative-AI product for the product-development lifecycle. This extension brings it into Jira, where teams already keep their epics.

I designed the whole Jira extension myself. It turns a rough epic into a clear one, then into features, and the person approves every change. Each decision below serves one HCI principle.

Start where the epic already lives

Consistency

An epic already has a page in Jira, so the extension opens from that page and is built from Jira’s own buttons, tabs and fields. It holds one way in, two dialogs, and three views in each.

Jira’s issue typesEpicits issue pageStory, Task, BugSub-taskThree stripesthe way inEnrich Epica dialog, three tabsGenerate featuresa dialog, three stepsDetailsthe epic as it standsEnrich titlecurrent title, enriched titleEnrich descriptionall of it, or a selected partQuestionsbefore any feature existsFeatures listfive, with issue keysOne feature1 of 5: Accept, Reject, NextEnrich, on one feature:the same dialogEvery dialog: the conversation on the right, Save changes at the foot

Ask before writing

Error prevention

The extension asks clarifying questions before it writes, and any of them can be skipped. An earlier version shared one answer box across the three questions. The prototype gives each question its own.

Earlier: one shared box

Prototype: a box on each question

Highlight and ask

User control

Selecting text in the description offers Enrich selected text. The request applies to the selection, and the rest stays as written.

Nothing changes without a yes

Human in the loop

What the AI writes appears under the original and waits for Accept. Generated features are reviewed one at a time, each with its own Accept and Reject.

Every step can be taken back

Error correction

Undo steps back once, and Reset returns to the start. Cancel and Discard changes sit beside Save changes, so the dialog can always be left without saving.

It says what it did, every time

Feedback

Each action gets its own line in the conversation: Epic enriched, Title enriched, Title accepted. A field with nothing written yet says so: Not yet enriched.

Enriching an epic

Generating features