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.
You can use the NBI clearance built-in system to identiyfy the double case. Want to lern how nbi NBI online appointment portal work, visit this site. This is a helping site, I always use to visit for NBI related assistance. You should also check it out.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.