Scribd
Upload
2 views2 pages

Important Tables in Site Schema

The document outlines various database tables related to project management and agile methodologies, detailing their purposes and the types of information they hold. Key tables include ACME_REPORT_TEMPLATE for report metadata, PM_RELEASE_BACKLOG_ITEM for backlog items, and PM_TEAM_MEMBERS for team assignments. Each table serves a specific function in managing project data, user settings, and team configurations.

Uploaded by

Fabian Esquivel
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
2 views2 pages

Important Tables in Site Schema

The document outlines various database tables related to project management and agile methodologies, detailing their purposes and the types of information they hold. Key tables include ACME_REPORT_TEMPLATE for report metadata, PM_RELEASE_BACKLOG_ITEM for backlog items, and PM_TEAM_MEMBERS for team assignments. Each table serves a specific function in managing project data, user settings, and team configurations.

Uploaded by

Fabian Esquivel
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

1.

ACME_REPORT_TEMPLATE - Holds all the graphs and reports metadata, such as the type,
category, name description and more.
2. ACME_SCENE - Holds the dashboard layout information, similar to the FAVORITE table (see
below) used only by the dashboard.
3. ACME_WATCH - Holds information about watched items (backlog items that a user wants to follow).
4. BUG (defect) - Holds defect information. Since defect is presented as backlog item in AGM, this
table holds all the defect only fields which do not exists in the PM_RELEASE_BACKLOG_ITEM
table (see PM_RELEASE_BACKLOG_ITEM).
5. DATACONST - Holds configuration parameters which cannot be changed from the application,
these parameters effect only this Site (See System table PARAMS - for cross site configuration
parameters).
6. FAVORITES - Holds the grid favorite information.
7. GROUPS - Holds all supported roles.
8. PM_ACCEPTANCE_TEST - Holds User Story Acceptance Test information.
9. PM_AGGREGATION_MAP_DATA - Holds metadata information needed for Over Time Reports
(Agile graphs).
10. PM_CONFIGURATION_STORAGE - Holds Site configuration which can be changed by the
application (workspace settings for example).
11. PM_KANBAN_STATUS - Holds the Storyboard (Kanban) configuration data.
12. PM_PRIVATE_BUCKET_ITEMS - Defects that are placed in a specific private bucket (See
PM_PRIVATE_BUCKETS).
13. PM_PRIVATE_BUCKETS - The private bucket, containing private bucket items (See
PM_PRIVATE_BUCKET_ITEMS).
14. PM_PRODUCT_GROUP - The workspace data.
15. PM_PRODUCT_GROUP_USERS - The users (see USERS) assigned to a workspace (see
PM_PRODUCT_GROUP) and their role in it.
16. PM_PRODUCT - The application data
17. PM_RBI_TEMPLATE - The Template container, contains elements from
PM_RBI_TEMPLATE_ITEM (see PM_RBI_TEMPLATE_ITEM)
18. PM_RBI_TEMPLATE_ITEM - An item in a specific PM_RBI_TEMPLATE container (See
PM_RBI_TEMPLATE)
19. PM_RELEASE_BACKLOG_ITEM - Holds the backlog item agile information such as release, team,
story point and more. Can be one of the following: Theme, Feature, User Story, or Defect. The
distinction is according to the RBI_ENTITIY_TYPE column (REQ is for Theme, Feature, User Story
and BUG is for Defect - see REQ table and BUG table). The RBI_ENTITY_ID column holds the id of
the item in the BUG or REQ table. The item workspace (see PM_PRODUCT_GROUP) is according
to the RBI_PRODUCT_GROUP_ID column.
20. PM_RETROSPECTIVE - The retrospective data for each team in every sprint.
21. PM_TASKS - The task data, linked to the backlog item entity(see RELEASE_BACKLOG_ITEM).
22. PM_TEAM_ACTIONS - The actions created in the retrospective entity (see PM_RETROSPECTIVE)
23. PM_TEAM_MEMBER_TEAM_SPRINTS - Holds information about the team member (see
PM_TEAM_MEMBERS) on a specific team sprint (see PM_TEAM_SPRINT), such as how many
working days the member will work on a specific team in a specific sprint.
24. PM_TEAM_MEMBERS - Holds information about the user (see USERS) assignment to a team (see
PM_TEAMS).
25. PM_TEAM_RELEASE - Holds information about the team (see PM_TEAMS) assignment to a
release (RELEASES).
26. PM_TEAM_SPRINT - Holds information about the assignment of a team (see PM_TEAMS) to a
sprint (see RELEASE_CYCLES).
27. PM_TEAMS - Holds the team information.
28. RELEASE_CYCLES - Holds the sprint information. The containing release (see RELEASES) is
according to the RCYC_PARENT_ID column.
29. RELEASES - holds the release information. The release workspace (see PM_PRODUCT_GROUP)
is according to the REL_PRODUCT_GROUP_ID column
30. REQ - Can be one of the following: Theme, Feature or User Story, the distinction is according to the
RQ_TYPE_ID column (see REQ_TYPE). Since Theme, Feature and User Story are presented as
backlog item in AGM, this table holds all the fields, which do not exist in the
PM_RELEASE_BACKLOG_ITEM table (see PM_RELEASE_BACKLOG_ITEM).
31. REQ_TYPE - All available requirement (see REQ) types
32. USER_SETTINGS - Holds user specific configuration, such as last page, don't show this message
again check box and more...
33. USERS - The users assigned to this site, derived from the USERS table in the System Schema.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy