TASK AUTOMATER
Make recurring Atlassian work repeatable
The Task Automater turns recurring Jira and Confluence manual work into executable tools. Bulk updates, migrations, permission audits, cleanup and reports run as CLI commands or web forms. Dry-run mode, JSON caches and issue streaming keep large operations predictable, repeatable and traceable.
A library of sharp tools
At its core sits a library of dozens of ready-to-run tools for Jira and Confluence routines. Each tool is a method on a Java class, marked with an annotation, picked up by the framework automatically. The catalog spans deletion of attachments, creation of components and versions, management of project-specific field options and permissions, up to Confluence migrations across instance boundaries. Adding a tool means adding a class — no framework changes needed.
Command line, browser, cron
The same tool can support different working modes. Scheduled runs start through the CLI and fit into scripts or cronjobs. Ad-hoc tasks run as browser forms, with predictable URLs and pre-filled parameters. Destructive actions default to dry-run and log what they would have changed. Only when the result looks right does the tool actually write. First runs stay controlled, recurring routines become production-grade.
Scales to thousands of tickets
A handful of tools makes the difference once you face thousands of tickets, hundreds of Confluence pages, or several Atlassian instances. Issue streaming loads only the fields a run needs. JSON caches keep intermediate state so a run can resume after an interruption. Bulk operations handle per-ticket failures without aborting the whole run. Excel imports wire up business lists directly, no intermediate formats.
Wired into the Atlassian environment
Beyond Jira and Confluence, the Task Automater talks to the systems around them: LDAP for person and group lookups, SharePoint for access requests, GitHub YAML for group definitions, Excel and CSV for business inputs, PowerPoint as a source for ticket imports. Multiple Atlassian instances are handled through Spring profiles — one configuration and one token set per tenant, the same tool catalog on top. Authentication uses per-instance personal access tokens in a strictly scoped properties file.