What is the recommended method (or best practice) for using JIRA to manage multiple projects with multiple clients? We are a web agency with a single project manager, who is responsible for managing the projects and tasks for all clients across each internal team (design, dev, and marketing).
I've searched quite a bit through the documentation, use cases, and via Google - perhaps not searching on the right keywords - but have not found any details on how best to implement.
I've considered using project categories to define the clients. I've considered creating a single project for each team - managing clients and requests on a per-task basis. But, both methods appear to be cumbersome to manage by a single person - especially as the list of clients and projects grows.
Here's some info about my own implementation, which I find rather easy to manage (I'm the only system admin)
All this represents a significant time (and money) investment from the system admin, especially JEMH, which is powerful and works very well, but is quite complicated to configure for a junior admin. But it pays off after a few months.
I don't think anyone could recommend a single foolproof method that works in every case. I suggest you take a look at the plugins I mentioned, and make sure your project manager gets really good with JQL notation for filters. The managers who can make good filters are the ones who have the easiest time keeping track of issues across multiple projects.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs