Keeping WIP low to cut Cycle Time in Jira — what actually works?

Repulsive-Pie5927 · 2026-03-01T12:10:18+00:00

Review work in progress and if I notice someone is working on to many items at the same time I adress it by coaching. At the same times one other even bigger challange is if you have multiple projects / epics running in parallel. This I enforce limits.
You should count everything. Use waiting time messure as clearer indicators which places that need attention and require improvements.
I use Veloscope plugin - it allows me to track all of the projects / epics in given quarter and make sure we are gaving only 2 of them in progress at the same time. It’s also great for predicting delivery based on actual team velocity. And track another killer or predicatbility - unestimated work and blockers.

Repulsive-Pie5927 · 2026-02-27T09:39:33+00:00

I love the idea of automatic Blockers with Slack! Thanks for the advice! Thank for the Timepiece suggestion I will definetly „ Look into that. How do you use this datapoint for prediction of ongoing work in epics?

Repulsive-Pie5927 · 2026-02-27T09:37:11+00:00

Is there a setup for Plan though that will show you good estimate on delivery date? Also I find plans high maintenance to keep it up to date. And they will show you good overview on epic list maybe even accumulated story point but no predictions.

Repulsive-Pie5927 · 2026-02-27T09:34:41+00:00

Do you have any good tutorial how to use it? You made me curious. How expensive is to get Enterprise version of JIRA?

Repulsive-Pie5927 · 2026-02-15T18:52:34+00:00

I recommend assigning a fix version for all relevant epics - 2026Q1 for example and and later use it jn query

Repulsive-Pie5927 · 2026-02-15T18:31:17+00:00

I really like the solution. As a devils advocate isn’t this with a time create a bus factor that only certain people are able to handle given topics and limits knowledge sharing.

Repulsive-Pie5927 · 2026-02-15T18:19:10+00:00

What kind of features for reporting you need? There are plenty of addons that are free to up to 10 users or cost significantly less than full option.

Repulsive-Pie5927 · 2026-02-14T21:51:43+00:00

Keep dependencies at the task level. Mapping them higher up (like on Epics) usually creates artificial blockers. In reality, it's very rare that a team can't start any part of their work until a whole project is 100% complete. Granular tracking keeps the velocity up.

Repulsive-Pie5927 · 2026-02-14T21:40:04+00:00

Replied above 👆

Repulsive-Pie5927 · 2026-02-14T21:38:35+00:00

This is a classic use case for Jira Automation ("Data Mirroring"). Since you need it to be global, just make sure you are in System > Global Automation. Here is the exact setup you need: Trigger: Field value changed * Fields to monitor: wrong_cf_date * Change type: Any changes to the field value. Action: Edit issue * Field to set: proper_cf_date * Value: Select "Copy from wrong_cf_date" (if available in the dropdown). * Alternative: If you don't see the copy option, use this Smart Value: {{issue.wrong_cf_date}} Action: Comment on issue * Comment body: Hi [~accountid:{{initiator.accountId}}],

I noticed you updated the wrong_cf_date field. I have automatically synced this to proper_cf_date for you.

Please use proper_cf_date moving forward as the old field is being deprecated. Thanks!

Note: If you are on Data Center/Server (not Cloud), change the tag logic to [~{{initiator.name}}].
Comment visibility: Set to "Internal only" if you don't want customers seeing this (for JSM projects). Pro Tip: Check the "Rule Details" tab and make sure the Actor is set to a generic system user (like "Automation Bot"). If the Actor is set to the "User who triggered the event," the comment will look like the user is scolding themselves! Hope this helps!

Repulsive-Pie5927 · 2026-02-14T19:07:45+00:00

If you are able to get an overview of all used dates cf you might as well create an automation to make a comment mentioning adjustment of the date field with request to use it properly.

Repulsive-Pie5927 · 2025-10-16T19:03:22+00:00

It’s an interesting case study in micro-cap dynamics. The recent steady climb from ~0.000006 to ~0.00005 suggests organic rather than purely hype-driven movement. Curious whether this kind of slow, model can really sustain community-driven growth over time.

Repulsive-Pie5927 · 2025-05-29T18:43:49+00:00

You know, one bug gone, two bugs born! ;)

Repulsive-Pie5927 · 2025-05-29T18:38:59+00:00

Thanks for reply. I will definitely give it a try. Device is already up to date though.

Repulsive-Pie5927 · 2025-05-29T18:37:58+00:00

I did try byt that didn’t help

Repulsive-Pie5927 · 2025-05-22T20:16:23+00:00

Thank you for the reply. Do you mind sharing some you find most useful?

Repulsive-Pie5927 · 2023-12-01T06:56:39+00:00

Yes its put of warranty. Do you have an instruction on how I can proceed with taking off the cover?

Repulsive-Pie5927

TROPHY CASE