Setting up Jira for work management with multiple teams (Not Software)

[Josey Varughese]

Hello Jira Community,

I am tasked with finding a solution that works for us at work. We have Jira Work Management. We have 2 teams, each with their Team-Managed project. Both teams report to the same director now. The ask is for us to create 1 project (TM or CM) that we can use to track incoming work from any other department (we have deptA and deptB). So far, so good. What I am having trouble with is figuring out which team gets which task. Currently, we have 2 TM Projects with statuses like 3d printing, fabrication, CNC, etc, that are displayed on a board. Each TM project has its own automation based on a custom field. We want a clean board that has 3 statuses (TODO, In Progress, and Done) that the reporter sees, but our teams will have a much larger view. individual members also create their own tasks so that they can keep track of what is on their plate.

• What is the best way to organize this?
• IT said CM Project is the way to go. What is everyone's take on it?
• What is the best way to tackle this?
• Can categories, labels, components, and/or some other field to sort it to the appropriate teams?

[John Funk]

Hi Josey,

Yes, CM Project is ALWAYS the way to go. I strongly dislike using TM projects - especially in a shared environment. 

Would the new project just be an intake project where requests are gathered and then cloned to one of of the TM projects? 

If so, then you need to find a field that has values that are unique to each TM project. Maybe that is the custom field you have described in your question. Is that correct? Is that a field that you could put in the form for the user and based on the selected value would differentiate for the two TM projects? 

[Josey Varughese]

Hey John,

Thank you for your response. I was awaiting access to a CM-work management sandbox.  I have played with it for a few days now, and here are answers to your questions and my thoughts. The new project was going to be a buffer between the company and the 2 teams, but we have decided to stick with one large project that has, for lack of a better term, buckets that issues will fall into for each process/work ( 3d printing, fabrication, CNC, etc). CM has a lot more functionality than TM projects.

That said, I started organizing the tasks using components/categories instead of statuses. Does this make sense? 

I like components because they are very easy to use, and I can automate them. Categories are not as easy to use and can be grouped by categories ( components lack this capability).

This is an existing TM project and in a board view.

The next 2 are CM projects with status and category in a board view, respectively.

Based on this, can you point me in the right direction? I am at an impasse about which direction to take. Whatever we choose must be simple and practical for our technicians, who avoid technology as much as they can.

[John Funk]

I agree with the approach of using Components for right now.

[Josey Varughese]

Thank you. Is there any way to display components similar to groupby categories, status, and priority?

[John Funk]

Not sure that I understand your question. Do you have an exact use case?