Jira automation getting messy while handling NBI Clearance appointment follow ups

[SlideShare Downloader]

Hi guys,

Need small advice from people using Jira for support/process tracking.

We are handling many NBI Clearance appointment follow ups and verification requests daily and honestly workflow getting little messy now. Before we was using only sheets + email but now moved some process into Jira.

Main issue is when applicant appointment status changes again and again (pending, reschedule, verified etc), automation sometimes creating duplicate updates or ticket moving into wrong queue.

Also if 2 team members reply same case same time, comments and status become confusing.

Just want ask if anyone here handling similar approval/verification type workflow in Jira?

How you manage duplicate cases?
Best automation for repeated status changes?
Better way for assigning review tickets?
Maybe our workflow structure is wrong from start 😅

Would like hear some real setups from other

[Tomislav Tobijas · Accepted solution]

This seems like a duplicate of https://community.atlassian.com/forums/Confluence-questions/Anyone-using-Jira-Service-Management-for-appointment/qaq-p/3236340 

@SlideShare Downloader can we close/remove this one?

[NBI Clearance Online]

We've seen similar issues when managing NBI Clearance appointment requests. Keeping one ticket per applicant and using unique reference numbers (like the appointment or EOR number) helps prevent duplicate automations. Adding clear status transitions and automation conditions also makes Jira workflows much more reliable as the number of follow-ups grows.

[ali sial]

I think the biggest issue is usually too many automation rules reacting to the same event. If appointment statuses like pending, rescheduled, and verified change frequently, it helps to keep a single source of truth and use conditions to prevent duplicate triggers.

This becomes especially important in processes related to NBI Appointment Online, where applicants may update schedules or submit follow-up requests multiple times. I'd review automation logs first and check whether multiple rules are acting on the same status transition. That often reveals the root cause of duplicate updates and queue confusion.