Personal mode. A calm, task-first view of Jira. Every change verified.
In development · Being built now for Jira Cloud · Linear planned next
Projects / Atlas / Sprint 14
Sprint 14 board
SearchSwitching between the original page and Personal mode. Pick one to take over.
Five core tasks, done one way. Each maps to Jira’s official API. Two read, three change, every change checked.
Today
Next
Blocked
Illustrative data. The API calls shown are the ones Satin’s Jira Cloud adapter uses.
Verified changes
Done means done. Satin says it only after Jira does.
Every change takes the same four steps through Jira’s official API. If any step fails, Satin changes nothing, says why and offers the Jira page.
- Checks your permission and the field before writing
- Re-reads the task, so it never overwrites someone else’s change
- Writes once, and never repeats a change blindly
- Reads the result back from Jira, then says Done
What happens in Jira
- 1CheckYou can edit this field in Jira
- 2Re-readNobody has changed it since you opened it
- 3Write onceSent to Jira’s official API, one time
- 4Read backJira now shows: due Today
Undo and “What changed?”
Every change, reversible and on the record.
Right after a verified change, Undo puts it back as a new change, checked in Jira the same way. “What changed?” lists each change, with before and after.
- One click from Satin’s toolbar, or from its popup
- Satin’s look can be undone too; the undo is recorded
- Changes in Jira say what happened, including what didn’t
- Kept on your device, with no task titles or descriptions
What changed?
- SpacingComfortableCompact· 2 min ago
- WordsStandardPlain· Yesterday
- LayoutBoardList· Monday
The native switch. The original Jira page is one action away, from every screen.
One action, on every screen. A switch or keyboard shortcut hides Satin and hands focus back to Jira.
The page never left. Jira stays loaded and untouched underneath, which is why switching is instant and loses nothing.
Back where you were. Your scroll position, selection and half-typed text are where you left them.
Steps aside by itself. If Jira changes unexpectedly, Satin hands back the original page and tells you once.
Your keys stay yours. While Satin has focus, Jira’s shortcuts don’t fire, and Satin’s never fire on the Jira page.
Never hides what matters. Satin never covers the security, permission or billing notices that Jira shows you. It keeps them visible and clickable, without reading what they say.
- action back to the original
- 1action back to the originalOn every Satin screen
- to draw your view from cache
- 300 msto draw your view from cacheDesign target, p75
- for a verified change, end to end
- 2 sfor a verified change, end to endDesign target, p75
- changes to the wrong task allowed
- 0changes to the wrong task allowedA release gate for the beta
What it does, and leaves to Jira. Every control maps to a real, checked action.
Personal mode does
- Today, Next and Blocked; showing why a task is blocked is in development
- Find by words or by key, with / from anywhere
- Task detail, with a link to the same task in Jira
- Change status, due date and assignee, each one verified
- Layout, density, words and text size from your Interface DNA
It doesn’t
- Create or delete tasks: Jira does that, one click away
- Workflow steps that ask for extra fields: they open in Jira
- Redraw Jira’s own interface: Satin uses its own components
- Use AI: every step is deterministic. An optional command bar is planned for the beta
- Run anywhere you haven’t turned it on
In developmentPersonal mode is being built now for Jira Cloud. Linear is planned for a later phase.
Questions about Personal mode.
No. Jira keeps every feature and stays loaded underneath. Personal mode covers the five core tasks people do most; for everything else, the original page is one click away.