What is the easiest way to achieve custom fields for sub teams sharing a single project?

Question

Three teams share one project. We currently dictate what team owns a ticket by assigning the correct team in the Component field.

The problem - Each team needs their own custom fields , irrelevant of the issue type in their tickets.

Ex: Team 1 needs the field "Customer" in their tickets, while Team 2 needs the field "Server" in theirs. Neither Team 1 or Team 2 need the other's fields.

What is the best way to go about breaking this down? I've seen customization that shows fields based on what the Component field is set to, but that seems a bit convoluted for us. Right now it feels like the best route may be to give each team their own project, but we don't want that overhead either. Another option is to create a ton of issue types, is that right?

Ideally, there would be a solution to add a field customization scheme to the issue once the Component dropdown is selected.

Lachlan_m9c4si · Answer

@Doug Clendening

ProForma might be the plugin you are looking for. Our forms can be dynamic, meaning certain custom fields only show based on certain conditions.

For example, if you have a single-option checkbox corresponding to "Team 1", "Team 2" and "Team 3", if the "Team 1" option is selected, different fields can be shown than if the user select "Team 2" or "Team 3".

This can be a powerful tool to make sure that even when different teams are using the same form, the right information is still captured every time.

If you're interested, you can try our fully featured Lite version here

Joe Pitt · Answer

Yes. The added advantage of components is you can assign a component lead and they will be automatically be assigned the issue when the component is selected

Doug Clendening · Answer

Would continuing to use the Component field to tag the teams correctly make sense as well, or is there a better way?