Hi @Kustagi Suma I've just come across your question, have you found your solution already? One of those suggested here or another one? If you're still looking for the right approach, I wanted to suggest that Jira's native cascading select field is worth considering first. You can create a single cascading select custom field where the top level contains the 12 team names, and each team's sub-level contains the values A, B, C, D. That way, you avoid creating 12 separate fields. When creating an issue, the user picks their team from the first dropdown, and the A/B/C/D options appear in the second dropdown. Native Jira supports exactly 2 levels of cascading select, which covers your scenario.
The limitation with the native approach is that every team would see every other team's name in the first dropdown - there's no way to restrict visibility so that, say, Team 3 only sees 'Team 3' as an option. If that kind of scoping matters to you, native Jira can't help with it.
If you'd like that visibility control, there's a Marketplace app worth looking at: Awesome Custom Fields. Its Cascading Select field type supports visibility restrictions by user, role, or group, so you can configure it so each team only sees their own branch of the dropdown. It also supports multi-select per level, which might be useful if users need to pick more than one value from A/B/C/D.
I am affiliated with the team that built this app, so if you have any questions about setting it up for your project, I am happy to help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.