Our department is about to start using Jira but I’m wondering if it’s the right tool for us. We handle theater equipment maintenance and repairs rather than traditional software development. My daily tasks include fixing communication headsets, monitoring display screens for marketing, and managing audio cable installations. We also work with coax cables for radio antenna systems and collaborate with IT on server room infrastructure.
My main concern is whether Jira will actually help our workflow since we’re planning to use it more for project tracking than as a standard help desk solution. I’m worried about getting bogged down with too much system administration when I should be focusing on actual equipment repairs and maintenance work. Has anyone successfully adapted Jira for similar non-software technical work? What configuration approaches work best to keep things simple and efficient?
totally get ur concerns! we used jira for event planning n it felt clunky. maybe try simpler tools first? keep it light so u can focus on ur tasks instead of the system.
We switched to Jira for our broadcast equipment about 18 months ago. The learning curve was quite a challenge, but it has been beneficial for tracking repair histories and maintaining department communication. The initial administrative overhead was significant, and we nearly abandoned the system after the first month. The key shift was treating it simply as an advanced ticketing system instead of aiming for perfection. For equipment maintenance, linking related issues has proved invaluable, revealing patterns in repairs that spreadsheets would miss. It’s advisable to start with default workflows and only make changes when necessary.
I’ve been using Jira for facilities management at a manufacturing plant for two years. Start basic - just create simple issue types like ‘Equipment Repair’, ‘Preventive Maintenance’, and ‘Installation Project’. Don’t overcomplicate workflows at first. What works for us: custom fields for equipment serial numbers, location codes, and parts needed. The reporting is surprisingly good for tracking maintenance schedules and spotting recurring problems with specific equipment. The mobile app lets me update tickets while I’m actually working on stuff, which beats our old paper system. You’re smart to worry about admin overhead though. We made one person our ‘Jira champion’ to handle configuration while everyone else just uses it daily. Keeps people from messing with settings and breaking things. Start minimal and only add complexity when you actually need it.