Database Collection Details
- Manoj Kumar Srivastava
- Hirenkumar Babariya
Sr No | Collection Name | Collection Description | Affected Area |
1 | access_requests | Stores all the requests to get access for any role, along with the status of that request. | Role-based access |
2 | account_hierarchy | Stores data which is responsible for filter creation. data is inserted when a new project has been created. Filter like sprint and bellow additional filters from JIRA/AZURE processor. | Dashboard filters |
3 | action_policy_rule | rules for access management and API access flow | Authorization |
4 | additional_filter_categories | Filters level below Sprint for scrum and below projects for kanban | Dashboard filters |
5 | authentication | User's authentication data is saved in this collection. | User login |
6 | auto_approve_access_config | Automatic approve access request | Access management |
7 | board_metadata | Project's metadata | KPI configuration |
8 | build_details | Stores data coming from build tools like Jenkins, bamboo, azure pipeline , team city | Code Build Time and Change Failure Rate KPI |
9 | capacity_kpi_data | Stores estimated capacity for sprints. Data is entered from the setting screen. | Sprint Capacity Kpi |
10 | commit_details | Bitbucket's , Gitlab , Github commit data stored in this collection. | Number of check-ins per day |
11 | connections | List of connections. Used to connects to tools server for data fetching. | Project Tools |
12 | delete_project_trace_log | saved deleted projects basic configs with metadata | Projects Config, KPI data |
13 | deployments | Stores data coming from deployments tools like Jenkins, Bamboo, Azure Pipeline | Deployment frequency KPI |
14 | field_mapping | Jira-based project configuration data is saved in this collection. | Jira configuration data. |
15 | forgotPasswordToken | Token for forgot password is stored in this collection | Forgot Password |
16 | global_config | Stores data that is used globally | Project Config |
17 | hierarchy_level_suggestions | Dynamic hierarchy structure values suggestions | Project Creation (Scrum and Kanban) |
18 | hierarchy_levels | Dynamic hierarchy structure for project setup | Project Creation and Dashboard Filters (Scrum and Kanban) |
19 | jira_issue | Jira's updated data in case of scrum is saved in this collection. | Jira Kpis (scrum) |
20 | jira_issue_custom_history | Jira's history data in the case of scrum is saved in this collection. | Jira Kpis based on history (scrum) |
21 | kanban_account_hierarchy | Stores filter data in case of kanban, which is fetched from the JIRA collector. KnowHOW filters are derived from this collection. | Dashboard filters (Kanban) |
22 | kanban_jira_issue | Jira's updated data in case of kanban is saved in this collection. | Jira KPIs (Kanban) |
23 | kanban_issue_custom_history | Jira's history data in case of Kanban is saved in this collection. | Jira KPIs based on history (Kanban) |
24 | kpi_category | Dashboard dynamic category creation | Category Dashboard (Scrum and Kanban) |
25 | kpi_category_mapping | as per category mapping to KPI master details | KPI wise Category Dashboard |
26 | kpi_master | Kpi master data. All KPIs details are saved in this collection like KPI name, Info, maturity, etc. | All KPIs |
27 | merge_requests | Stores Data for code related tools like github, gitlab | Check-Ins & Merge Requests KPI |
28 | metadata_identifier | Metadata of Jira project. Used to auto-suggest values for field mapping | Mapping |
29 | processor | When processor runs it creates an entry here. One entry per processor. | All Processors Tools |
30 | processor_execution_trace_log | Processors run status and last executed date of run | All Processors Tools |
31 | processor_items | Mapping of tools (other than jira) and processor is in this collection. toolConfigId is the key on which mapping is based | Non-Jira KPIs |
32 | project_basic_configs | Project configuration's basic data is saved in this collection. | Under Projects |
33 | project_release | Project releases information is stored in this collection | Release Frequency Kpi |
34 | project_tool_configs | Tool Configurations are saved here.Tool details along with mapped connection | Tools |
35 | roles | All the roles available in the system | role-based access |
36 | sonar_details | Sonar data is saved in this collection. | Sonar KPIs |
37 | sonar_history | Sonar historical data saved in this collection | Sonar KPIs |
38 | test_case_details | Stores data of Testcases like tools of Jira and zephyr | Jira KPIs |
39 | test_execution | Information related to automated test case execution is stored in this collection. | Test Execution Kpi |
40 | user_board_config | This collection stored all KPIs hide/show status. | Hide/show functionality |
41 | user_info | User information like auth type and authorization data is saved in this collection. | User authorization and authentication. |
42 | usertokendata | User tokens stores | Login User |
© 2022 Publicis Sapient. All rights reserved.