
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.)
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.
If you like what you see and want to work together, get in touch!
morgan@morganpdeangelis.com