---
sourceDocument: Xanadu Strategic Portfolio Management
sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/it-business-management

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Strategic Portfolio Management

ft:clusterId :

    - itbm

bundleId :

    - itbm

workflow :

    - Technology


---

# Add issues for a demand

# Add issues for a demand {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Add an issue to a demand to escalate a risk or to track an unexpected problem such as
a technical malfunction or resource unavailability that occurs during any phase of the
demand life cycle. If the issue remains unresolved, unnecessary conflicts, delays, or even a
failure can occur.

## Before you begin

Role required: it_demand_manager

## Procedure

1. Navigate to AllDemandDemandsAll.
2. Select the demand to which you want to add an issue.
3. From the Issues related list, click New.
4. On the Issue form, fill in the fields.  
   For a description of the field names, see [Issue form](https://www.servicenow.com/docs/aDG7y7nLWX_lA7aNGh3obQ "Use the issue form to add an issue to a demand.").
5. **Optional:** Search in the knowledge base for any article related to the issue.
   1. Click the search knowledge icon (![Search knowledge icon]()).
   2. If you find relevant articles, click the title of an article to view its content.
   3. If you want to include the content of the article in the issue, click Attach to Issue.  
      The article content is copied in to the Description field of the Issue form. You can modify the text if necessary.
   {#add-issues-for-demand__substeps_dt4_ndv_lkb}
6. Click Submit.

## What to do next

* Convert an existing issue to decision, action, or request change and close the issue. For more information, see [Convert one RIDAC (Risk, Issue, Decision, Action, and Request Change) record to another for a demand](https://www.servicenow.com/docs/7rmh0FKH_iisDXXd2U1J2g "Convert one RIDAC record (risk, issue, action, decision, and request changes) to another, in that order, to retain the record information instead of having to create a new record manually and to more easily track the issue.").
* Associate the issue with your existing risks so you can track dependencies and recognize trends for future. For more information, see [Associate existing RIDAC (risks, issues, actions, decisions, and request changes) records for a demand](https://www.servicenow.com/docs/PttyGCkNsgE0JqoFSlHb2A "Link existing RIDAC records (risks, issues, actions, decisions, and request changes) to one another for your demand. Associating RIDAC records with each other enables you to keep a record of risks or issues and their outcome for analysis at demand closure and planning. It also helps to track the risks and issues throughout the demand life cycle.").
{#add-issues-for-demand__ul_sgs_pvj_yjb}

*[\>]: and then


