Views
Note
All views changes are handled via a standard deployment.Creating a view
For these, you will need to create a corresponding view file in the sync repo.
You should also do this in a way that creates a MR. Said MR should always be peer reviewed before merging (the MR should enforce this).
The exact nature of what you need to put into the YAML file will vary based on the issue’s request.
Be sure to read Working with sync repo files for more information.
Editing a view
For these, you will need to locate the corresponding view file in the sync repo and make changes to it.
You should also do this in a way that creates a MR. Said MR should always be peer reviewed before merging (the MR should enforce this).
The exact nature of what you need to put into the YAML file will vary based on the issue’s request.
Be sure to read Working with sync repo files for more information.
Deactivating a view
Note
Due to the nature of the multi-step process, this will result in a pipeline failure when step 1 is completed. This will be fixed in step 2.To deactivate an view, you must perform a two-step process
Step 1
- Locate the managed content file for the view
- Move the file from the active folder to the the corresponding location in the inactive folder (if it does not exist, create it)
You should also do this in a way that creates a MR. You will require someone from Support Leadership to approve this MR before you can merge it.
Only proceed to step 2 once all changes in step one are merged.
Step 2
-
Locate the YAML file for the view in the sync repo
-
Move the view from the active folder to the the corresponding location in the inactive folder (if it does not exist, create it)
-
Change the value of the
active
attribute in the YAML file tofalse
-
Change the
conditions
section to be:- field: 'brand_id' operator: 'is_not' value: 'GitLab Support' - field: 'status' operator: 'less_than' value: 'closed'
-
Change the
restriction
value to benull
You should also do this in a way that creates a MR. Said MR should always be peer reviewed before merging (the MR should enforce this).
Deleting a view
Note
We do not delete views except during an annual review of our views. Any other time, leave it as deactivated.
If you are looking for information about the annual review of views, please see Annual Review workflow
The process to delete a view is exactly as described in the views documentation page.
Exception deployment
To perform an exception deployment for views, navigate to the views project in question, go to the scheduled pipelines page, and click the play button. This will trigger a sync job for the views.
Repo links
- Zendesk Global sync repo
- Zendesk US Government sync repo
- Zendesk Global managed content repo
- Zendesk US Government managed content repo
9196a840
)