See which work is stuck, before anyone has to ask.
Pulse finds stuck and stale issues: every work item in progress, how long it has been running, and whether that is normal for your team.
Flowing, slowing or stuck, at a glance.
Every item still in progress is compared with how long your finished work usually takes, from the first in-progress status until done.
- Flowing: less time than half of your work items usually take
- Slowing: longer than usual, still within what 85% take
- Stuck: longer than 85% of your finished work. Worth a conversation
Plain words, no judgement.
“3× longer than usual”
Said in plain words, for each item.
Any scope
The whole project, a single version or a single epic.
You decide
Pulse points at what has run longer than usual; the team decides.
Spot the requests open longer than usual.
Pulse also works in Jira Service Management projects.
What counts
Stories, tasks, bugs and other standard work items.
Left out
Epics and subtasks.
History needed
Five finished work items in twelve weeks.
Until then
It still lists what is running, and for how long.
Nothing to set up.
- Open any projectand choose Clearlane Pulse in the project sidebar.
- Pick the scopeThe project, a version or an epic.
- Nudge what is stuckbefore anyone has to ask.
Ask Rovo which work looks stuck.
Clearlane Pulse adds a Rovo agent. Ask it which work in progress looks stuck. It answers from the same Jira work items as the page, only with what you are allowed to see, and it only reads: it never changes anything. It works where Rovo is turned on for your Atlassian site; Clearlane adds no AI model of its own.
Permissions and data
Pulse reads your Jira work and its status history with the permissions of the person looking at the page. To spare Jira, it keeps what it has just read for at most 24 hours in Atlassian’s storage for your site, without account IDs or work item content, and sends nothing outside your Atlassian site.
Questions, answered.
- Where do I find it?
- Open any project in Jira and choose Clearlane Pulse in the project sidebar.
- Why does it ask for more history?
- Pulse needs at least five work items finished in the last twelve weeks, each having passed through an in-progress status. Until then it still lists what is running, and for how long.
- How do I find stale issues in Jira?
- Open Pulse in the project sidebar: work items in progress for longer than 85% of your finished work are marked stuck, oldest first, with how long each one has been in its current status.
- An item is stuck on purpose. Is that a problem?
- No. Pulse does not judge; it points at what has been running longer than usual so the team can decide.
- Does it work in French?
- Yes. The app follows each person’s Jira language, in English, French or German.
- Does Pulse add dashboard gadgets?
- Yes. Two dashboard gadgets come with it: the age of work in progress by status, and a cycle time control chart.
- Does Pulse work on very large Jira sites?
- Yes. To stay within Jira’s request limits, Pulse can read the usual pace of about four large projects per hour on a very large site; each pace is then usually kept for the day.
- Does it work with Rovo?
- Yes. Its Rovo agent answers questions such as “Which work in progress looks stuck?” from the same Jira work items as the page. It only reads, and only shows what you are allowed to see.
Clearlane for Projects
Clearlane for Projects: budgets, delivery forecasts, flow and timelines, built from the work already in Jira, with no extra data entry.
Built and supported by Maxime Ragionieri, founder of Clearlane. Who’s behind Clearlane →
Free for up to 10 users.
Larger teams pay per user, billed by Atlassian on the Marketplace. No setup, nothing to install outside your Atlassian site. See the price for your team size →