Jira Automation Program

Process Automation · ICF International
Project Overview
Manual workflows and inconsistent process governance were slowing delivery across the division. Jira tickets arrived with incomplete fields, incorrect data, or in the wrong queue, which made reporting unreliable and created an estimated 500+ hours of manual admin work per month.
My Contributions
Identified the opportunity and led the full lifecycle as Lead IT Business Analyst: researched requirements, built custom fields and advanced automation rules in JavaScript and JSON, beta tested across international projects, led the cross-team rollout, and mentored external stakeholders. Worked with operations and finance managers, division directors, and engineering technicians.
~$250K
saved within 12 weeks
40+
custom Jira automations built
30
Jira projects standardized
10–20 min
saved per Jira request
500+ hrs
of monthly manual admin targeted
How it was delivered

From manual workflows to a standard framework

1
Discovery
Mapped each team’s workflow and pain points.
→
2
Prioritize
Ranked fixes by the time they would save.
→
3
Build
Custom fields and rules in JavaScript and JSON, in 30 days.
→
4
Beta test
12 weeks of testing and performance analysis.
→
5
Roll out
Director sign-off, training, and demos across teams.
Jira admin Custom fields screen with the Select a Field Type dialog, showing checkbox, date picker, labels, and number field options

Step 3 in practice: custom fields were the foundation of the framework. Every automation rule relied on structured, validated data captured when a ticket was created. (Illustrative Jira screen.)

ICF International
IT Business Analyst
Apr 2023 – Jun 2025

Solution: One standardized automation framework replaced each team’s ad-hoc workflows. Rules took over the repetitive admin of routing, field completion, and status updates, so tickets entered the system complete and in the right queue, and reporting could finally be trusted. The division’s Director of Technology signed off the documentation, and teams were brought on board through training sessions, demos, and support resources.

Results: Beyond the headline savings, the division gained a replicable framework that future automation work could build on, rather than each team starting from scratch. Also at ICF: led requirements for custom mobile HVAC technician measurement tools, and helped deliver a cloud migration ahead of an accelerated 2-month deadline.

Tools: Jira, Jira Automation, Confluence, JavaScript, JSON, As-Is / To-Be process analysis, and UAT.

Lessons learned: Automation is a change-management effort as much as a technical one. Early stakeholder engagement, training, and a fast feedback loop turned expected resistance into adoption.

Before and after

What changed for the teams

Before
Tickets arrived with incomplete fields or incorrect data
Requests landed in the wrong queue
Reporting couldn’t be trusted
An estimated 500+ hours of manual admin every month
After
40+ rules handle routing, fields, and updates automatically
10–20 minutes saved on every request
Consistent data and shared visibility across 30 projects
About $250,000 saved in 12 weeks
Tech stack

Built with

Jira
Jira Automation
Confluence
JavaScript
JSON
As-Is / To-Be analysis
UAT