We don’t want to create subtasks for everything, and we don’t want to create a hundred statuses in the workflow.
— Razvan Nechifor, Jira Global Team Leader, Edenred

About

Edenred is a global company headquartered in France, operating across 44 countries with around 12,000 employees. It works in employee benefits, workforce mobility, and corporate payment solutions, giving the company a broad international footprint and a complex operating environment.

At a glance

Challenge: Support varied regional and team workflows without creating subtask sprawl, unwieldy status lists, or constant admin overhead for a small central Atlassian team.

Solution: Use Checklists for Jira Pro as a lightweight, in-issue execution and governance layer that makes process steps visible without overcomplicating Jira workflows.

Impact: Cleaner workflows, clearer standards, more self-service flexibility for teams, and a scalable way to support process governance across a large, distributed Jira environment.

‍

As a global digital platform company operating across multiple countries, Edenred manages a large and varied Jira environment. Different teams, regions, and business units have their own workflows and requirements, but the central Atlassian team still needs to maintain consistency, control, and quality across the whole system.

That created a familiar enterprise challenge: how do you support local flexibility without losing global governance?

For Edenred, Checklists for Jira Pro became a practical way to solve that problem. The team initially started with the Free version, but as their Jira environment and governance needs grew, they outgrew its capabilities and moved to Pro. Instead of adding more custom statuses, relying on unnecessary subtasks, or asking teams to manage process steps in free-text fields, Edenred uses checklists to bring more structure and visibility into work as it moves through Jira.

Supporting Edenred’s broader OneJira approach

At Edenred, the central Atlassian team is driving a global “OneJira” approach: building a more unified platform that increases process visibility while giving teams a consistent place to manage work. Checklists for Jira Pro fits naturally into that operating model.

Where Jira provides the shared system of record, checklists help make the smaller process steps inside each issue visible, repeatable, and easier to complete. That means teams can document what needs to happen without hiding critical actions in comments, descriptions, or disconnected tools.

This is especially valuable in a global environment where different teams need room to adapt their work, but the organization still needs consistent standards and transparent execution.

Reducing Jira complexity while keeping teams flexible

At Edenred, Jira has to support many different teams with different ways of working. Standardizing everything too aggressively would create friction. But leaving every team to build its own process independently would make governance harder and increase administrative overhead.

Checklists for Jira Pro helps Edenred strike the right balance. Teams can capture important procedural steps directly inside an issue without requiring constant workflow changes or additional Jira configuration. That makes it easier to support local needs while maintaining a more consistent operating model across the organization.

Rather than turning every process requirement into a status or a subtask, Edenred can keep workflows cleaner and easier to manage. Checklists provide a lightweight layer for operational detail that would otherwise create clutter or push teams toward less structured workarounds.

Helping a small central team support a large Jira environment

This balance matters even more because the Atlassian environment is supported by a relatively small central team. In that context, reducing administrative effort is not just convenient, it is necessary.

Checklists for Jira Pro gives teams a way to manage more of their operational process inside Jira without depending on Jira administrators to model every nuance in workflows, issue types, or project configuration. That helps the central team maintain control where it matters most while giving delivery teams more day-to-day flexibility.

The result is a more scalable way to support growth. As Jira usage expands across departments, regions, and use cases, Edenred can provide teams with more structure and governance without increasing complexity at the same pace.

With checklists, the teams can manage the details they need without asking us to change the workflow every time.
— Razvan Baciu, Global Head of Stability and Infrastructure Services, Edenred

Making process visible across teams and departments

One of the strongest themes in Edenred’s Jira approach is process visibility: the idea that work becomes easier to manage when teams have a shared platform for seeing what is happening. Checklists for Jira Pro extends that principle to the issue level.

Instead of requiring every department or regional team to request custom workflow changes, checklists give teams a familiar way to capture important steps directly where the work is already happening. That makes the app useful not only for technical delivery teams, but also for cross-functional processes in areas such as approvals, onboarding, operational readiness, and service management.

For non-technical teams, a checklist is easier to understand than a heavily customized workflow. For the central Jira team, it is easier to govern than a growing collection of statuses, subtasks, and one-off configuration requests.

Creating structure, quality, and clearer execution

Checklists for Jira Pro also helps Edenred create better process discipline inside Jira. Instead of relying on users to remember every expected step or document everything in unstructured text, teams can work through clear, visible, repeatable check items embedded directly in the issue.

That improves execution quality and makes expectations easier to follow. It also creates a clearer operational standard across teams, even when those teams work differently in other respects.

For Edenred, that value is practical and immediate. Checklists for Jira Pro helps reduce clutter from unnecessary subtasks, avoid the sprawl of excessive custom statuses, replace unstructured text-based workarounds, and maintain clearer standards across a diverse Jira landscape.

It’s much easier to enforce a process when the steps are directly visible in the issue.
— Razvan Nechifor, Jira Global Team Leader, Edenred

Meeting enterprise expectations for trust and security

Security also played an important role in adoption. Edenred only adopts apps that meet its security expectations, including participation in the Atlassian Bug Bounty program. That made security verification a baseline requirement for consideration.

For a global organization operating at scale, trust in marketplace apps matters alongside functionality. Checklists for Jira Pro met that bar, which helped make it a viable fit for Edenred’s environment.

A stronger way to justify value in Jira

Checklists for Jira Pro gives Edenred a simpler way to capture process detail in Jira without relying on heavier workarounds for functionality Jira does not provide out of the box.

That matters both operationally and strategically. Operationally, teams can work with more clarity and consistency. Strategically, the Atlassian team can support governance and scale without overcomplicating Jira administration.

For Edenred, the value is not just in adding another app. It is in making Jira easier to manage, easier to use well, and better suited to the realities of a large, distributed organization.

Looking ahead

Looking ahead, Edenred sees a lot of opportunity to introduce more advanced use cases with automation and templates. With Checklists for Jira Pro already established as a practical governance and execution layer in Jira, the team can continue building on that foundation and extend its value through deeper feature adoption.