> For the complete documentation index, see [llms.txt](https://developer.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.collibra.com/workflows/out-of-the-box-workflows-walk-throughs/issue-management/issue-management-configuration.md).
# Issue Management configuration
Access the workflow configuration via 
**Settings** → **Workflows** → **Definitions** → **Issue Management**.
## Description
This process handles all issues. It will automatically be started when a new issue is created. Roles are assigned dynamically by the process using the configured user expressions. First a reviewer can accept to do the review, or if no reviewer responds within time-limit, the issue manager is asked to assign a reviewer. The reviewer can then choose to ask more information, choose another reviewer, reject the issue or accept the issue and propose a solution. If the issue is accepted, the stakeholders are asked to vote for the proposed solution and if accepted, the reviewer can assign a assignee and ask him to implement the solution. The assignee can reassign to another assignee or implement the solution himself. After implementing the reviewer is asked to review the solution and when accepted, the requester is notified of the resolution and the process is ended.
## Applies to
This workflow definition applies to the **Data Issue** asset type.
## Configuration variables
You can edit the configuration variables directly from the workflow definition page by clicking 
in the upper-right corner of the variables table.
| Variable | Description | Default value |
| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------ |
| voteTimeoutDuration | Time before the voting task expires. The variable is passed to the [Voting Sub-Process](/workflows/out-of-the-box-workflows-walk-throughs/voting-sub-process.md) | B5D |
| reviewerUserExpression | User expression for reviewers of the issue | {role(Business Steward)} |
| voteWarningTimeDuration | Time before a warning is sent to the stakeholders for approving the proposed solution | B3D |
| assigneeUserExpression | User expression for assignees of the issue | {role(Business Steward)} |
| issueManagerUserExpression | User expression for issue managers of the issue | {role(Issue Manager)} |
| fallbackUserExpression | User expression for users to fallback to when the users of the initial user task are empty | {user(Admin)} |
| sendVotingActionEmails | Send an action email to users that are required to vote in the process | false |
| stakeholderUserExpression | User expression for stakeholders of the issue | {role(Business Steward)} |
## Start label
Default value: Manage Issue
Click **Edit** to edit the label.
## Start event
A start event is an event that triggers the workflow, for example starting the workflow when an asset is created.
The Issue Management workflow starts automatically when an issue is created.
## Roles
The roles define the permissions to manage the workflow. For example, if a certain tasks must be urgently executed but the responsible person is on sick leave, a user with the defined role can reassign that task to somebody else.
| Action | Roles |
| ------------------------------------------------------------------------------------------ | ------------------------------------------------------------ |
| Start workflow An action item with the start label is available to users with these roles. | - Community Manager
- Business Steward
|
| Stop workflow The option to cancel the workflow is available to users with these roles. | - Community Manager
- Business Steward
|
| Reassign tasks The option to reassign the task is available to users with these roles. | - Community Manager
- Business Steward
|
## Other
The settings in this section define global restrictions that apply to the workflow such as:
* Accessibility to guest or logged in users.
* Checking that the roles required by the workflow are not empty.
* Preventing the same worflow or other workflows from running on the same resource.
* Making the workflow available to be added to a dashboard.
| Setting | Enabled |
| ------------------------------------------------------------------------ | ------- |
| Any user can start the workflow. | No |
| Perform candidate user check on workflow start. | No |
| This workflow can only run once at the same time on a specific resource. | Yes |
| Lock resource. | No |
| Show in global create. | No |
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://developer.collibra.com/workflows/out-of-the-box-workflows-walk-throughs/issue-management/issue-management-configuration.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.