Time in Status for Jira

TimeFeed shows you which Jira tickets are stuck — the ones spending longer than usual in their current status — in one vertical feed, and helps you clear them card by card. There is nothing to configure: install it, open it, and the feed is already right. TimeFeed is a desktop app inside Jira on the web.

How “stuck” is decided

TimeFeed looks at tickets that finished in your project over the last 90 days and works out the normal (median) time tickets spend in each status. An open ticket is flagged as stuck when it has been in its current status for more than twice that normal time. Each card shows how far past normal it is.

On a brand-new Jira site there is no finished-ticket history yet, so there is no “normal” to compare against and the feed honestly shows “Nothing stuck.” That is the app working as designed — real customers install on sites with history.

The Feed

The feed lists every stuck ticket as a card, most abnormal first. Filter chips narrow the list by work type (Bugs, Tasks, Stories, and so on), and the sidebar's quick filters show everything, only tickets assigned to you, or only unassigned tickets. A panel on the right — “Items to Review” — shows a progress ring that fills as you review, with how many items are left, and a Recent activity log of what you did today: each entry shows the ticket — key and title — as a link to the ticket, with what you did and when on a line underneath.

Each card leads with the ticket's title — click it to open the full ticket in Jira — then a line with its owner (or “Unassigned”), its key, and badges for its work type and status, then the ticket's description (long ones expand in place). Below that, a band shows the two numbers that matter, side by side: how long the ticket has been in its current status, and the usual time for that status.

Every card carries its own actions — there is no queue to unlock. Acting on a card counts it as reviewed for you, and the ring in the right panel fills as you go. Each action is confirmed by a status bar at the bottom of the app that says what just happened — for example, that a reminder was posted and the owner was mentioned — then fades away.

What the actions do

Every action sits on the card — nothing is hidden in a menu: a main button, Change owner, Change status, Move to bottom as a plain text action, and an × to remove it. The app's left column carries this same list as an “Action guide,” one line per action, and it folds away when you don't need it:

• Remind owner (the main button when the ticket has an owner) — Posts a comment on the ticket mentioning the person it is assigned to, saying how long it has been in its status and what the usual time is. They get a Jira notification. Nothing else about the ticket changes.
• Change owner (the main button when the ticket has no owner; its own button when it does) — Opens a people search; pick a person and the ticket becomes theirs. Jira notifies the new owner.
• Change status (button) — Shows the statuses Jira offers for this ticket; pick one and the ticket moves there, right then. Closing the ticket is the Done choice in that list.
• Move to bottom — Sends the card to the bottom of the feed. The ticket is untouched and stays in your feed — just last, so you can deal with the rest first.
• Remove (the × at the top of the card) — Takes the card out of your feed. It asks first — “Remove from your feed? It stays removed until you restore it from Reports.” — so it cannot happen by accident. The removal is saved for your account only: other people still see the card, and the ticket itself is untouched.
• Open in Jira — Click the card's title to open the full ticket in Jira.

Remind owner, Change owner, Change status, and Remove count as “reviewed” — the ring in the right panel fills as the count of items left goes down. Move to bottom does not — the ticket is still to review, just at the end of the line. Your reviewed marks and removals are saved for your account, so they are still in place after a reload; a removed card drops out of the review count, and the Report is where it is accounted for.

Removing a card

A removal covers only the spell of stuck-ness it was made in. If the ticket later leaves its status — finished, moved on — and then gets stuck again, the card comes back to your feed on its own. A removal can hide a card you have dealt with; it cannot hide a future problem forever. To undo a removal, open the Report: removed tickets are marked there, with a Restore button that puts the card straight back in your feed.

The Report

The Report tab lists every open ticket in the project in a table: key, summary, status, assignee, time in current status, total age, the normal time for that status, and how far past normal the ticket is. Tickets you removed from the feed are marked in the table, and can be restored from there. The table can be downloaded as a CSV file.

Privacy

TimeFeed runs on Atlassian Forge, Atlassian's own app platform. Your issue data never leaves Atlassian.

Support

Questions or problems: reach us through the TimeFeed listing on the Atlassian Marketplace.