This page is in development, and focuses on Oracle connections & organization for JIRA-based views & tables.
...
| SCHEMA& USERNAME | DESCRIPTION | WHEN TO USE IT | NOTES |
|---|---|---|---|
| REPORTING | This is where to write view synonyms that point to JIRADWH views. This can also be where view code drafts get written before being transferred to JIRADWH. | For all report-related read access, or when creating a view in REPORTING schema | |
| JIRADWH | Home of actual DWH views. Home of ETL packages & functions that work on multiple JIRA schemas' data. This is where to write DWH code. | Only when creating views or tables in JIRADWH schema | |
| LABOPSJIRA_5 | Home of the labopsjira data that the DWH looks at. | Rarely | |
| PRODINFOJIRA_5 | Home of the labopsjira data that the DWH looks at. | Rarely | |
| GPDEVJIRA | This is the "LABOPSJIRADEV" clone of labopsjira_5, which is refreshed on demand. | During testing | |
| PRODINFOJIRA5_TEST | This is the "GPDEVJIRA" server test clone which can be anything, depending on current testing needs. | During testing |
...
Nasko built ETL functions to simplify view creation, standardize SQL structure, and provide scalability and schema flexibility.
More info here: Jira DWH
Custom fields
The ETL functions described above (Jira DWH) can be used to pull custom fields from specific JIRA schemas and projects.
This document (JIRA Custom Fields) facilitates view SQL creation (and is especially useful when you need to add several CFs to your SQL). If you aren't sure which ETL function to use (e.g. get_text_fields vs get_option_fields), trial and error is okay.
Creating a new view
New views are created using as much standardization as possible, and are generally created in REPORTING schema until peer code-review has been performed. Views in the JIRADWH schema are good templates. The Custom Field
...