Time tracking on Jira

[Alice Rischer]

Hi everyone,

Our team is using Jira for our Kanban board and it’s working really well for us. There are a few features we’d love to have to make it work even better for us, and I was hoping you Jira wizzes would be able to help out.

To give a bit of an overview:

• We have a lot of ‘issues’ on our board (we’re a big team), meaning we don’t know how long issues have been in each column/bucket. This means we can’t identify inefficiencies in the end to end and it’s harder to remove blockers for individual issues
• It’s also difficult to see when a ticket has been moved to another ‘bucket’, so team members have to sift through Jira or manually notify relevant team members

It’d be great to have:

• A solution in Jira or a solution that integrates with Slack
• A way to see how long each Issue has been in a particular bucket and how long issues, on average, spend in each bucket
• Notifications if an Issue has spent too long in one bucket (timeframe preferably to be set by team)
• Notifications when a ticket has been moved to a different bucket

Would any of you be able to guide me in how I can get this for our Kanban board?

Any replies greatly appreciated!

Thanks

[Jack Brickey]

The notifications are easy enough as that is associated with transitions between statuses. That should already be in place for you today. Certainly you can connect with slack and have these notifications sent to vested parties. See this integration.  

So that leaves the challenging part - displaying time in status and notifying when in a status “too long”. I don’t know how to do this on the Kanban but you could create filters with subscriptions. This would be pretty easy for the first status in a simple workflow, e.g. To Do - In Progress - Done. For ‘too long in To Do’ you would  create a filter of issue in To Do where issue createddate is >= -30d for example.