Jira Stalled Work Visualizer

@bojans9

Hello Hope you are doing well I can set up a scalable Minecraft mini-games server with a polished lobby system and a structure that makes adding many games straightforward. I’ll handle the server configuration, permissions, game plugins/modules, matchmaking or game-join flow, lobby navigation, optimization and essential administration settings. I’ll also test the mini-games, player flow and server performance to ensure the experience remains stable as the player count grows. For the lobbies, I can create a distinctive hub layout with clear navigation, themed areas and intuitive portals/NPCs or menus for accessing each game. I can also document the setup so ongoing management is simple. I can deliver the initial server setup in 1 weeks. Do you already have a preferred Minecraft version and a list of mini-games you want included? Best regards, Bojan

@rimiloca

I can configure a maintainable stalled-work view for your existing Jira project: a preserved original start date, explicit blocker reasons, flagging across development/testing/review, and visible age information on cards. I would first check your Jira edition and board type, then build and test the rules with sample issues before touching the live workflow. Native scheduled automation can refresh a days counter daily; a genuinely live calculated counter may need an existing add-on, which I would confirm with you rather than promise unsupported behaviour. My bid covers one project/board, the agreed rules, and a short handover guide. Are you using Jira Cloud or Data Center, and do you already have ScriptRunner?

@vascubrian

Hi, I’m an Atlassian/Jira Developer and Software Engineer with 7+ years of experience building Jira workflows, automation, custom configurations, and development processes. I can configure your Jira project to automatically flag stalled or blocked issues, including external dependencies, Development, Testing, and Review blockers. I’ll also add a clear “days since start” indicator so your team can immediately see how long each task has been active. I can implement this using Jira Automation, JQL, workflow configuration, and lightweight add-ons such as ScriptRunner where necessary, while keeping everything maintainable. I’ll deliver the configured workflow/board, automation rules, and a short guide for future changes. Ready to get started.

@nakabirik

Hi, I am Muheebwa. I understand you need your existing Jira project to make stalled work obvious, flagging cards waiting on external approvals, dependencies, development, testing, or review blockers wherever they sit, with a clear visual cue and a days since start counter that updates live, using standard Jira features or lightweight add-ons your team can maintain. What usually matters most is defining stall, since days since start does not show whether work is moving, and time since the last status change or comment is the reliable signal, so a status age rule beats an issue age rule. A common issue is storing the counter in a field updated by scheduled automation, which lags up to a day, when a Scripted Field computes it live on each view. The tricky part is the cue itself, since Jira cannot colour individual cards, so the flag has to come from a label, flag, or swimlane a board can render. My approach would be to define the stall rules with you, implement them with JQL and Automation to set a flag or label, add a Scripted Field for days since start, build a board or swimlane that surfaces stalled items, and hand over a short how-to so you can change thresholds later. Do you have ScriptRunner available, or should this stay within native Automation and JQL only? Looking forward to hearing from you.

@alfatrade2

The tricky part is the 'days since start' counter — Jira doesn't track that natively per status, so it'll need a custom date field set on first transition plus an automation rule recalculating it daily, not just a color label on the card. Are the stall thresholds the same for Backlog and In Progress, or different per column? I've scoped and built data-exchange automations for CRM-style workflows before, and this maps cleanly onto Jira's rule engine and JQL-based board filters.

@zuaibahmedd

Hi, I can configure your Jira project so stalled issues and dependencies are immediately visible without making the setup difficult to maintain. I’ll implement: * Clear visual flags for external, technical, development, testing, and review blockers * A reliable **days-since-start** counter visible directly on issue cards * Automation/JQL to keep blocker status and timers updated automatically * A maintainable workflow using native Jira features, Automation, or ScriptRunner where appropriate * Updated workflow/board configuration plus a concise handover guide I’ll work with your existing Jira setup rather than forcing an unnecessary redesign, and ensure your team can easily modify the rules after hand-off.

@mozamh91

Hi, I can set this up using standard Jira features that your team can maintain. Yes: stalled issues waiting on external approvals or technical dependencies get a clear visual flag. Yes: Development, Testing and Review blockers get the same treatment, in any column (Backlog, In Progress or custom). Yes: every card shows the days since work started, set by an automation rule when work begins. Yes: I will use Jira Automation, JQL and board card colours/layout, with no custom code. Yes: you get the updated workflow scheme, automation rules, board configuration and a short how-to. First step: I review your current workflow statuses and fields and confirm which Jira plan you are on, since that decides which automation options are available. Relevant work: I rolled out Xray in Jira for a QA team (30% less test-management time) and built a customised Jira dashboard with the Jira API. Freelancer record: 6 reviews, 4.97 average, 100% on time and on budget. Moizam

@chamanrajragu

Jira has no built-in "days since start" counter on cards, so that's the part I'd build first. Automation stamps a Started date the first time an issue enters In Progress, and a daily scheduled rule writes the day count into a field shown on the card layout. Your team can edit all of it later without a paid add-on. Plan: - Blockers: a "Blocked by" reason (external approval, technical dependency, dev, test, review) plus "is blocked by" links. Automation flags the card while the blocker is open and clears the flag when it resolves - Stalled work: JQL for issues with no status change in N days, flagged the same way in any column - Board: card colours and quick filters driven by that JQL, so stalled cards stand out - I'd build and test everything on a separate Jira Cloud test site first, then hand over the exported rules, workflow changes and a short how-to Is your project company-managed or team-managed? It changes which board settings I can use. Chaman

@amulk9

Hello there, I’m Amul, a Jira & Workflow Automation Specialist with 7+ years of experience designing Jira workflows, boards, JQL, Automation rules, and maintainable issue-tracking systems. I can configure your Jira project so blockers are impossible to miss—whether an issue is waiting on an external approval, technical dependency, development, testing, or review. Here’s how I can help: • Create clear blocker statuses/flags across Backlog, In Progress, and custom columns • Add visual cues for stalled/dependent issues directly on the board • Build a reliable “Days Since Start” counter visible on every card • Use Jira Automation, JQL, and ScriptRunner where needed • Ensure timers update automatically without manual work • Deliver the workflow/board configuration + concise hand-off guide I’ll keep the solution as close to standard Jira as possible, so your team can easily maintain and modify it after hand-off. If you share your current workflow/board setup, I can quickly identify the cleanest approach and implement it without disrupting your existing process. Best regards, Amul

@anujb141

Hi, I can configure your existing Jira project to clearly highlight stalled and dependency-blocked issues across Development, Testing, and Review. I’ll set up a maintainable solution using Jira Automation, JQL, workflow conditions/post-functions, and lightweight add-ons where necessary. I can implement visual blocker indicators, dependency-based flags, and a visible “Days Since Start” counter that updates automatically. I’ll also provide the updated workflow/board configuration and a short, clear handover guide explaining how your team can modify rules, statuses, and timing later. I’m happy to review your current Jira workflow and recommend the simplest approach before implementation.

@marvind18

You need stalled Jira work to stand out immediately, with the blocker reason and elapsed days visible on every board card. At Marin Software, I worked with production workflows where dependencies and clear handoffs had to remain traceable. I’d add structured blocker fields for external approval, technical dependency, development, testing, and review. JQL-based card colours or flags would highlight matching issues across every column. A Start Date field plus Jira Automation would maintain a visible “Days Since Start” value on each card, with quick filters for blocked and ageing work. I’d also review workflow transitions so blockers are set and cleared consistently, then provide the rules, board configuration, and a short maintenance guide. Is the project Jira Cloud or Data Center, and is it company-managed or team-managed?

@RevS412

To avoid false stalled cards, the elapsed-days counter should be anchored to a dedicated start field, while the blocker logic distinguishes external dependencies from development, testing, and review states. I’d map the current workflow, implement the least-complex maintainable option with native Automation and JQL first, then test it on sample issues across the board. The handover includes the configured rules or board view and a concise guide for future changes. At the start, I’ll confirm whether this is Jira Cloud or Data Center and whether ScriptRunner is already available.

@akhila226

Hi, I’m an Atlassian/Jira Administrator with 4.6 years of hands-on Jira experience, including Jira Software, workflows, Kanban boards, JQL, Automation, ScriptRunner, custom fields, and workflow configuration. For your requirement, I can configure the existing Jira project to clearly identify stalled work and dependency-related blockers. I can use Jira Automation, JQL, workflow conditions/validators, and ScriptRunner where required to handle external approvals, technical dependencies, development, testing, and review blockers. I can also implement the “days since start” tracking so the team can easily identify how long each issue has been active, along with clear visual indicators on the board. I’ll focus on keeping the solution simple, maintainable, and easy for your team to modify after handoff. I can provide the updated workflow/board configuration, automation or ScriptRunner rules, and a short step-by-step guide. I’m available to start immediately and can complete the work within the requested timeline.

@Weiw71

I can take care of ‘Jira Stalled Work Visualizer’. I’ll map the trigger/action flow, implement the automation with idempotency and error handling, and test it against representative inputs, then deliver the working automation/source plus setup and handoff notes. The listed stack (Agile Development, Software Development, Atlassian Confluence) fits that delivery path. I can start immediately; proposed turnaround is 2 days. If you have one priority sample or edge case, I’ll use it as the acceptance check.

@apeksha44

Hi, I can configure your existing Jira project so stalled work is easy to spot across the Backlog and board, including items blocked by approvals, technical dependencies, development, testing, or review. I’ll review your current workflow and board first, then set up clear blocker indicators, suitable automation and card fields. I’ll also configure a “days since work began” value that keeps the original start date when an issue moves between columns. I’ll test the setup with sample issues and provide a short handover guide covering the rules, filters, and workflow changes. One detail I’ll confirm before implementation: Jira Automation can refresh a day count on a schedule, while a counter that changes live on every card may require a lightweight app. I’ll recommend the simplest maintainable option for your Jira setup. I’m a Certified Scrum Master and Jira trainer, and I regularly work with Jira workflows, boards, JQL, and automation.

@Paulbennetminnu

i got experience in big 4 and tier 1 company where worked on these kinda tasks on daily basis im confident enough to implement and make best solution and pay me as per my work once you see the result… as i’m starting off here so wanna offer this