I find it better to think of boards as being views of sets of issues, not issue containers.
The main thing that means is that a board has to select which issues to work with. It does that with a filter, and because Jira's filters are quite flexible, you can do all sorts of things with it. A board for all your Epics, a board for several projects, a board for assigned to Dave, a board for issues over 14 days old, and so on. And, of course, you can make much more complex filters too.
So, on your notes, yes, you can do most of that. But you can't quite do the last line. Workflows and fields on issues are done at a project and issue-type level, so a board has to represent those, not configure them (although you can configure boards to show or ignore the fields)
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs