---
name: devsecops-devsecops-how-to-set-incident-assignees
title: Assigning incident issues to users
description: Incident issues that are created by the continuous integration (CI) or continuous compliance (CC) pipelines can have default assignees.
last-updated: 2022-05-13
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/devsecops?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Assigning incident issues to users
{: #assign-incident-issues}

Incident issues that are created by the continuous integration (CI) or continuous compliance (CC) pipelines can have default assignees.
{: shortdesc}

To assign default assignees, set the `incident-assignees` environment property to one or more usernames that are separated by a comma. For example, `First-User` or `First-User,Second-User`. For more information about the `incident-assignees` environment property, see [Pipeline parameters](https://cloud.ibm.com/docs/devsecops?topic=devsecops-cd-devsecops-pipeline-parm&format=markdown).

The pipeline takes these usernames and assigns these users to the incident issues that are created by the [`collect-evidence`](https://cloud.ibm.com/docs/devsecops?topic=devsecops-devsecops-collect-evidence&format=markdown) script. If a username is invalid, the logs provide a warning about an unsuccessful assignment, but the evidence collection is successful.

You can define this environment property per trigger so that each trigger can assign different users.
{: tip}