Codebase quality · AI workflows · Data updates

University Entry Requirement Monitoring

Entry requirements can be university-wide, nationality-specific, or course-specific. The workflow checks updates against existing records and routes the next action.

My role Maintenance and workflow supportPrimary implementation Colleague-ledAI use Ticket interpretation

ENTRY REQUIREMENTS · MONITORING WORKFLOW

A scheduled check, routed to the right next step.

See how ticket interpretation, record comparison, and clear workflow rules work together.

JIRA TICKETAI INTERPRETATIONRULE-BASED CHECK
JJIRA · REQUIREMENT UPDATE
University entry requirement

Ticket details guide the workflow to the relevant university update.

CHECKPOINTSCHEDULED
AITicket interpretedUpdate context identified…
REQUIREMENT CHECKREADY
↕
▤EXISTING RECORDCurrent requirement on file·
○Comparison routes the next step
EXPLORE THE ROUTING

Choose the comparison result to see its next step.

STEP 01 · SCHEDULEA configurable schedule starts the next requirement checkpoint.

Illustrative workflow · no real ticket or email content

Some entry requirements apply across a university. Others vary by nationality or by course. A monitoring workflow needs to find the relevant update and compare it with the current database record before an update is prepared.

Jira tickets are the checkpoint for updates. A scheduled bot checks tickets, follows the ticket to the related university email, and compares the email content with existing data. When requirements change, the workflow prepares an import file; matching records let the ticket close and the scheduled process continue.

My contribution was keeping the workflow dependable

A colleague led the primary implementation. I supported the system through codebase and script maintenance, quality checks, storage improvements, README documentation, updates from generated files, and Hermes-based checkpoint bots and schedules.

My work

Maintenance and quality

  • Maintained scripts and codebase quality.
  • Improved project READMEs and documentation.
  • Built configurable scheduled checkpoint bots in Hermes.
  • Updated records from generated files.

Team boundary

Colleague-led implementation

My colleague led the implementation; my contribution focused on dependable maintenance, scheduled checkpoints, documentation, and data updates.

A practical use of AI

Adapt the tool to the messy part of the process.

Ticket wording varies. AI helps interpret that checkpoint; explicit workflow rules handle schedules, comparisons, and ticket movement.

Back to all projectsContact