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.

[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.