Recurring Ticket Templates

Extension for automated periodic creation of service requests (UserRequest) based on configurable templates. A background process runs every hour, checks active templates, auto-resolves previous tickets, and creates new ones with rendered titles using placeholder tokens.

Rozsireni pro automaticke periodicke zakladani pozadavku (UserRequest) na zaklade konfigurovatelnych sablon. Background process bezi kazdou hodinu, kontroluje aktivni sablony, automaticky resi predchozi tikety a vytvari nove s renderovanymi nazvy pomoci tokenu.

• Configurable recurrence (weekly, biweekly, monthly, custom N days)
• Placeholder tokens (year, month, month_name_cs/en, week, date, quarter, period_num)
• Auto-resolve of previous ticket with configurable resolution code
• Optional initial stimulus application (e.g. ev_pending)
• Full EN/CS localization
• Admin menu for template management

• Konfigurovatelna periodicita (tydenni, dvoutydenni, mesicni, vlastni N dni)
• Tokeny pro nahrazovani (year, month, month_name_cs/en, week, date, quarter, period_num)
• Automaticke reseni predchoziho tiketu s nastavitelnym kodem reseni
• Volitelne aplikovani pocatecniho stimulu (napr. ev_pending)
• Plna EN/CS lokalizace
• Admin menu pro spravu sablon

1. Copy jpnet-recurring-ticket/ to iTop extensions/ directory.
2. Run iTop Setup (upgrade).
3. After setup, "Recurring Tickets" menu appears in admin section.

1. Zkopirujte jpnet-recurring-ticket/ do adresare extensions/ v iTopu.
2. Spustte iTop Setup (upgrade).
3. Po dokonceni se v admin sekci objevi menu "Recurring Tickets".

Templates are managed via admin menu Recurring Tickets > Templates. Each template has: name, status (active/inactive), title template, description template, recurrence settings, organization, caller, optional service/team, initial stimulus, resolution code, and auto-resolve note.

Sablony se spravuji pres admin menu Recurring Tickets > Templates. Kazda sablona obsahuje: nazev, stav (aktivni/neaktivni), sablonu nazvu, sablonu popisu, nastaveni periodicity, organizaci, zadavatele, volitelnou sluzbu/tym, pocatecni stimulus, kod reseni a poznamku k automatickemu reseni.

The RecurringTicketProcessor class implements iBackgroundProcess with 1-hour periodicity. It also extends UserRequest lifecycle by adding ev_pending transition from 'new' state.

Trida RecurringTicketProcessor implementuje iBackgroundProcess s 1-hodinovou periodicitou. Rozsiruje take zivotni cyklus UserRequest pridanim prechodu ev_pending ze stavu 'new'.