Customer story
As Avalara grew and underwent several Jira migrations, redundant custom fields, legacy configurations and increasing complexity made administration harder. With Optimizer for Jira, its administrators found a more manageable way to clean up their instance and prepare for further site consolidation.
Key outcomes
Avalara is a global provider of cloud-based tax compliance automation, helping businesses manage complex tax requirements.
Its development and engineering teams use Jira to support the development, maintenance and delivery of its software solutions.
As the business grew and its Jira environments evolved through successive migrations, keeping configurations organized and manageable became increasingly important.
Over time, several smaller Jira migrations left Avalara with an increasingly complex and inconsistent instance. Redundant custom fields, legacy schemes and configurations carried over from previous projects were adding to the administrative workload.
Avalara needed a practical way to understand its configurations, identify what could be cleaned up and make Jira easier to maintain as the business continued to grow.
The team faced three connected challenges.
Redundant custom fields and issue types
Duplicate and unnecessary configurations made it harder to maintain a clear, consistent Jira setup.
Legacy configurations and technical debt
Unused schemes and outdated settings accumulated over time, making administration more time-consuming and increasing the risk of errors.
An upcoming site consolidation
With plans to combine two Jira sites, administrators needed to identify and address existing clutter before taking on another major change.
“This app has been amazing for us. It has helped us clean up after several small migrations and we’re looking forward to using it on migrated fields for two sites we’re now combining.”
Avalara customer reviewGlobal provider of cloud-based tax compliance automation
Avalara turned to Optimizer for Jira to address the clutter left by previous migrations and support its preparation for further site consolidation.
Rather than relying on time-consuming manual investigations across Jira administration screens, Optimizer provided the visibility and tools needed to approach configuration cleanup more systematically.
Optimizer helped administrators inspect custom fields and other Jira configurations, making it easier to identify redundant items, legacy schemes and areas requiring attention.
Challenge addressed
Redundant custom fields and issue types
Duplicate and unnecessary configurations made it harder to maintain a clear, consistent Jira setup.
With clearer visibility into the instance, administrators could prioritize unnecessary configurations for cleanup.
Optimizer’s bulk-action capabilities also provide a way to manage multiple configuration changes without repeating the same administrative tasks individually.
Challenge addressed
Legacy configurations and technical debt
Unused schemes and outdated settings accumulated over time, making administration more time-consuming and increasing the risk of errors.
Having used Optimizer following several smaller migrations, Avalara planned to use it again when addressing migrated fields as two Jira sites were combined.
Challenge addressed
An upcoming site consolidation
With plans to combine two Jira sites, administrators needed to identify and address existing clutter before taking on another major change.
Optimizer helped administrators inspect custom fields and other Jira configurations, making it easier to identify redundant items, legacy schemes and areas requiring attention.
Challenge addressed
Redundant custom fields and issue types
Duplicate and unnecessary configurations made it harder to maintain a clear, consistent Jira setup.
With clearer visibility into the instance, administrators could prioritize unnecessary configurations for cleanup.
Optimizer’s bulk-action capabilities also provide a way to manage multiple configuration changes without repeating the same administrative tasks individually.
Challenge addressed
Legacy configurations and technical debt
Unused schemes and outdated settings accumulated over time, making administration more time-consuming and increasing the risk of errors.
Having used Optimizer following several smaller migrations, Avalara planned to use it again when addressing migrated fields as two Jira sites were combined.
Challenge addressed
An upcoming site consolidation
With plans to combine two Jira sites, administrators needed to identify and address existing clutter before taking on another major change.
The result was a more structured approach to managing technical debt and keeping Jira maintainable as the environment evolved.
Optimizer for Jira became a useful part of Avalara’s Atlassian administration toolkit, helping the team tackle configuration problems accumulated through multiple migrations.
By identifying redundant custom fields and unnecessary configurations, Avalara was able to address technical debt left behind by earlier migrations.
Greater visibility into the instance and its configurations made it easier for administrators to organize and prioritize cleanup work, reducing the complexity of ongoing maintenance.
With two Jira sites being combined, Avalara planned to continue using Optimizer to address migrated fields and manage the configuration work involved.
For Avalara, the value extended beyond one cleanup project. Optimizer provided a practical way to maintain oversight of a growing Jira environment and prepare for further changes.
Whether you’re cleaning up after a migration, preparing to combine Jira sites or tackling years of configuration clutter, Optimizer for Jira helps you identify what needs attention and make cleanup easier.
Reduce repetitive admin work and keep track of Jira health as your environment evolves.