Jira Tasks

Every morning, the Jira tickets that are actually on you today.

What you get

One page, waiting for you at 8. Every ticket with your name on it gets one line — its key and a short human title, where it stands, how urgent it is, and the one thing that happens next. The tickets other people are stuck behind sit at the top; the ones parked on somebody else sit at the bottom, where you can safely leave them.

Your work, not the project. Not a sprint board, not a report for your manager: the tickets assigned to you, plus anything of yours holding someone else up. Finished tickets drop off entirely. Nothing is created, edited, commented on or moved — it only reads.

About the status column

Every Jira team invents its own statuses, so one project says Selected for Development where the next says Ready to start. This page does not show you that zoo: it sorts every ticket into five plain words — Blocking, In progress, To do, Unclear, Waiting.

How to look at it

Open the My Tickets app in this cabinet. It comes pre-filled with a made-up example so you can see the shape of it straight away — the page says clearly that those tickets are fake. Your first real list takes its place.

Before it can read your real Jira

Connect Jira in Cabinet's integrations screen. This is the easy kind: one step, and you paste nothing. Click Connect, sign in with your Atlassian account in the browser tab that opens, approve it — the same sign-in also covers Confluence, which nothing here uses. Until you connect, the page keeps showing the example.

What's inside

• Ticket Reader — the one agent. Reads your tickets, writes the list.
• Morning Jira Tasks — the one routine. Runs at 08:00 every day.
• My Tickets — the one page. Opens on today, with a dropdown for earlier days.