-
Notifications
You must be signed in to change notification settings - Fork 5
Object Hierarchy
This will go over the object hierarchy, and what objects have unique names in which contexts. It's beginning to be evident that we can't go on just assuming that people won't have overlapping board names. So, this document is there to organize the hierarchy and specify how these will be identified.
The project is the base entity. All boards and sprints belong to a project. An account belongs to an organization, and the access key is given by an organization, so this is already handled by the authentication structure. Therefore the Project is the top entity. These have unique names.
The project can have multiple boards. In fact, multiple projects might have boards with the same name. So it's necessary to somehow differentiate between boards belonging to different projects.
Sprints belong to particular Scrum boards. They cannot be created independently of a scrum board.
Issues belong to boards, although they can also appear in sprints.
There will be a hidden project object. We could use the inherent JIRA project objects to set a "default" project, and if there's any ambiguity, it will ask the user to specify the board. Similarly for Sprints, if there are multiple boards with sprints named similarly, it would ask you to specify the contexts that are necessary to uniquely identify a board.