# GitLab label change - workflow:customer-review -\> workflow:needs-verification

**URL:** https://discourse.paraview.org/t/gitlab-label-change-workflow-customer-review-workflow-needs-verification/694
**Category:** Development
**Created:** [October 8, 2018, 3:43pm UTC](https://discourse.paraview.org/t/gitlab-label-change-workflow-customer-review-workflow-needs-verification/694 "2018-10-08T15:43:58Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [October 8, 2018, 3:43pm UTC](https://discourse.paraview.org/t/gitlab-label-change-workflow-customer-review-workflow-needs-verification/694/1 "2018-10-08T15:43:58Z")

</div>

We have made a slight change to the labels used to indicate an issue’s state on GitLab for ParaView to make its meaning clearer.

After an issue has been resolved to the satisfaction of ParaView developers, please mark issues as `workflow:needs-verification` instead of `workflow:customer-review`. The new tag serves the same purpose, which is to indicate the issue is ready for verification by an outside reviewer to sign off on (most often @wascott).