Practicality of having multiple boards for the same project

[Schups]

Some of our Jira projects have multiple boards.

These boards are based on mutually exclusive filters, i.e. a task shown in a board, can't be see on the other.

It happens way too often that a user forgets to set a specific field upon task creation, making that task invisible after the creation. Lots of frustration follows.

In the scrum board, the in-line creation feature is useless because the specific field used be the filers can't be filled. Again, upon creation the task does not appear in the backlog. Users are forced to follow a longer path to create their issues.

My users and I find this difficult to accept.

Considering Jira the market leader, I am wondering if I am missing something...

How do you manage the same need?

Thank you!

PS: Of course, projects with a single board have no problems of this kind!

[John Funk]

Hi @Schups ,

Maybe I am missing something, but why can't you make the field mandatory to create the issue?

[Schups]

Thank you for the quick feedback!

So far we avoided going this way. Using mandatory fields would make us personalize the schema configurations for pretty much for every project, which we have avoided so far, re-using as much as possible.

Before going down this road I would like to make sure this is the best / only way to go.

[John Funk]

So, you are using different fields on every project that need to be filled in? In other words, the filters are based on different fields and not the same one? 

What if you used Components to capture the values and just made the components field mandatory across those projects?