This question is in reference to Atlassian Documentation: Permissions overview
In the Jira logical model, it seems that Boards are subordinate to Projects. Is this correct? Boards and Projects also seem to have a many-to-many relationship, which is why I'm asking the question.
The JIRA Boards are just a presentation of the JIRA Project issues. One board can display issues from multiple projects hence many-to-many. Hence, It's just another way to view the JIRA issues on which you can do some agile stuff (in a SCRUM Board) and some Kanban stuff.
I wouldn't say "subordinate", a board simply needs issues to work with, and issues live within projects.
The many:many relationship is correct although it's two-steps, via issues. A board can include issues from many projects, and a project's issues could be shown on many boards.
Not exactly. Boards can be built from a filter, which might not even include a project in the query.
You are right that projects and boards have a many to many relation. But that's pretty much it. Boards are created for teams and can be created off any valid filters. It could draw issues from one project, multiple projects or even a subset of a given project.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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