-
Bug
-
Resolution: Fixed
-
Low
-
10.112.3
-
1
-
Severity 3 - Minor
-
No
Issue Summary
Updates made in production on Jira Custom Team Mapping does not update in Enterprise Insights. Investigation found that ETL service doesn't update this table due to records with [Jira Project Key] = NULL being skipped in ETL, despite this being valid for some customers.
This is reproducible on Data Center: Yes
Steps to Reproduce
- Search the tables 'Jira Team Value' and 'Jira Align Team'
- IfNotExists – Click "Add New" at the bottom of the list
- At the top a new empty row will appear
- Enter the TeamName in the 'Jira Team Value' TextBox
- Select the TeamName in the 'Jira Align Team' DropDown
- Click "Update Teams" at the bottom of the list
- Validate the TeamName now exists in the list
- Run the following query in Enterprise Insights
SELECT [Jira Custom Team Mapping ID] ,[Jira Team Value] ,[Child Team Value] ,[Jira Project Key] ,[FK Jira Align Team ID] ,[FK Jira Project ID] ,[FK Connector ID] FROM current_dw.[Jira Custom Team Mapping]
Expected Results
Added Custom Team Mapping ID will appear in query results.
Actual Results
New Custom Team Mapping ID does not appear in queries or table data in Enterprise Insights.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available