Recommended Structure

Question

What do you recommend for the following configuration?

I have a system with multiple components, including firmware from multiple devices. The component section works great for this. All the hardware gets grouped into a single product.

I have a derivative of that system for 600VAC instead of 480VAC; Much of the system is the same, but there are some differences and different firmware in each component.

Should I have one project for the 480 and 600 or somehow group both into a single project? The reason I ask is that if there is an issue in one, there is probably an issue in the other.

Thoughts?

Jim Birch · Answer

The bottom line is that if you want to track version numbers for separate products using Jira version numbers you need to have separate projects.  Do you firmware versions run in parallel numbers or independently?  i.e. Is there one codebase, with multiple products?  Other that that you can choose whatever suits, using either components and projects.

Not sure, but it sounds like you may need a client issues project and a few product projects.  You then clone/link the client issues to the product issue.

Remember that you can change later by splitting or joining projects if you get something wrong so don't stress too much.

Jon Cotter · Answer

If they get completed as the same issue by the same person, then maybe think about adding a custom field to each ticket that determines which system the ticket applies to (600, 480 or both).

I have a similar situation where we have international versions of the product and sometimes changes apply to all, or just some.  It would have been too much overhead to create separate projects for each, since they are usually completed by the same person.