Use different default values for a custom field for the same project but different issue type

[GC]

Context:

I have a custom field called 'qa/testing requirements'.

This field has been set up with a configuration scheme so that a specific default value is populated in the 'create' screen for a specific project and issue type (test sub-task).

I want a different default value to populate on the same project but a different ticket type called 'test' so that this ticket type has a different template to a 'test sub-task'

Problem:

I cannot add 'test' to the same configuration scheme as it will populate the incorrect template (default value).

But if I go to add a new context (configuration scheme), the project I am looking for does not show up on the list which leads me to believe that because I have already set up a configuration scheme for that project, I cannot create another one - even though the other one would be for a different ticket type.

Question:

Can anyone tell me if that is the reason? 

And if so, are there any suggested workarounds to:

• use Automation to add the desired template post ticket creation - which is not the ideal solution
• use a different custom field specifically for this ticket type where I would be able to create a new configuration scheme with its own default value

And if I'm incorrect then what am I missing? 

I would have thought this was something that Jira would allow you to do. 

[Nic Brough -Adaptavist-]

Putting everything on a single board is probably pretty useless.  When you've got a lot of issues on a board, Jira will limit the selection in order to keep it small enough for the computer to handle, but your humans will simply be overloaded and won't grasp it all.

Your best option is to create boards for each team selecting what they need to work with, and use other reporting for overviews of everything.

[Nadja Agreiter]

What you say in your last sentence, is exactly what I want: one board for each team, where all issues that team has to handle are displayed. What kind of "other reporting"? Is there any helpful support from Jira?

[Nic Brough -Adaptavist-]

Ok, great, you can create as many boards as you need, with different filters to draw in each different team's issues.

Other reporting would usually start with saved filters (often, the filters your boards are based on), which you then reuse in project reports, the issue navigator and, most powerfully, dashboards.  A user can create and share dashboards which can have lots of useful summary gadgets on it.  I personally prefer dashboards, but some people do prefer the project and board reports.

[Nadja Agreiter]

Ok, I'm going to try that. Thank you very much!