How do service-based businesses organize recurring operational tasks in Jira?

[Olivia Carter]

We're exploring Jira for managing recurring operational work in a service-based business rather than traditional software development projects.

Some examples include:

• Customer requests and follow-ups
• Scheduling field teams
• Equipment and vehicle management
• Recurring maintenance tasks
• Internal operational workflows

For teams using Jira in this type of environment:

• Do you use separate projects for different departments or keep everything in one project?
• How do you handle recurring tasks efficiently?
• Are there specific automations, workflows, or dashboards that have worked well?
• What challenges did you encounter during implementation?

I'd appreciate hearing real-world examples and best practices from organizations using Jira beyond software development.

[Olivier_OSTConsulting]

Hi @Olivia Carter 

For service operations the structure usually comes down to how different the workflows and SLAs really are. If field scheduling, maintenance, and customer follow-ups each need their own statuses, request types, or permissions, separate projects keep them clean and let you report per team. If they mostly share one process, a single project with a component or a "service line" field is easier to run day to day and still gives you per-team views through saved filters.

For the recurring work itself, Jira Automation is the native tool. A scheduled trigger (you can give it a cron expression) creates an issue, or a whole set of issues, on whatever cadence you need: daily, weekly, or on the first of the month. That covers preventive maintenance and routine follow-ups without anyone having to remember to open the ticket.

Dashboards built on saved filters (by component, assignee, due date, or status) are the part teams tend to underinvest in early, so it is worth setting them up from day one.

The piece native Automation does not handle well is recreating the same multi-step task set each cycle. If every maintenance run is really one parent issue with the same five sub-tasks and pre-filled fields, rebuilding that by hand gets old fast.
A templating app saves that hierarchy once and recreates it in a single action, and you can have a scheduled rule fire it. We are the ones behind Issue Templates for Jira Cloud, if it can help!

Olivier

[Rik de Valk _Brainboss_]

Hi @Olivia Carter , 

It sounds like Jira Service Management (JSM) might be a good fit for some of your teams. JSM offers a self-service portal where your (internal or external) customers can submit requests, using forms the service-teams can configure themselves. This allows service-teams to add fields to these forms so that they get the information they need to fullfil requests. And it allows customers to request anything from a single portal. JSM also enables you to connect shared maiboxes so that emailed requests also automatically generate new tickets (or comments on existing tickets). 

For JSM as well as Jira, you can use Automation Rules to automatically create tickets on a configurable schedule. Automation Rules don't require any coding; it is a no code (drag and drop) which is easy to use. 

Some of your example use-cases seem to require maintaining an inventory of some sort. As Nikola mentioned, this can be done using Assets. Assets allow you to maintain a 'database' of 'things' to which you can also relate tickets. For example, if someone reserves a vehicle, you can set the status of 'reserved', taking the vehicle out of stock. 

With regards to your other questions: 

• Do you use separate projects for different departments or keep everything in one project?
  The most common practice is to have a Space for each team. But there are exceptions. If multple teams work together on a single product or service, it can be best to have them work in a single space. Also, for an IT servicedesk, a single Space for all IT tickets is common practice. 
• How do you handle recurring tasks efficiently?
  As mentioned above: Automation Rules are the go-to solution
• Are there specific automations, workflows, or dashboards that have worked well?
  This is a very open question. But typical automations are automatic assignment based on selected 'affected service', or setting the Priority based on Impact and Severity of an incident. 
• What challenges did you encounter during implementation?
  In general: don't try to implement everything at once. Start with one team, a couple of use-cases. Start simple. Build it out from there. Also, if you're totally new to Jira, consider contracting an Atlassian Partner. 

Have a nice day, 

Rik 

[Nikola Perisic]

Hi @Olivia Carter 

Beyond software development, Jira uses business spaces as well that are not following Agile methodology. This is good for the teams that don't want software development. Some might be asking, why not use Trello? Trello is all good, but it has it's limitations. 

For any kind of inventory management, the combination of JSM which includes forms and also Assets from Service collection is a perfect choice.

If we are talking about the external customers, CSM would be the best choice to go from there.

Every product has its own purpose.