Welcome
Developing
Learn how to develop schemas by using the DevOps Plan Designer.
Developing Schemas
You can develop or modify schemas with the DevOps Plan Designer.
Packages and integrations
This topic explains the concepts of DevOps Plan packages and integrations.
Visualization package
The Visualization package helps to enable the creation of custom Kanban boards in DevOps Plan.

Overview
Learn general information about the product.
Install and deploy DevOps Plan
Find information about installing and deploying DevOps Plan client and server software.
Developing
Learn how to develop schemas by using the DevOps Plan Designer.
- Developing Schemas
  You can develop or modify schemas with the DevOps Plan Designer.
  - Understanding the functions of the DevOps Plan schema developer
    This topic provides an overview of the tasks typically performed by a schema developer.
  - Overview of the DevOps Plan Designer interface
    The DevOps Plan Designer includes several different windows, or views, that you will use to perform your schema development tasks.
  - DevOps Plan schemas
    This topic explains the concept of a DevOps Plan schema.
  - Customizing a schema
    To modify how change requests are handled, you need to use the Designer to customize the records and fields of a schema.
  - Schemas and packages
    This topic explains the concept of using schemas and packages in DevOps Plan.
  - Packages and integrations
    This topic explains the concepts of DevOps Plan packages and integrations.
    - Precautions when applying packages
      Follow these guidelines when you apply a package to a schema.
    - Packages available
      This topic lists the DevOps Plan packages that are currently available, grouped by category.
    - Overview of package application process
      This topic explains the general steps involved in applying a package to a schema.
    - Examples: The Notes, Attachments, and Email packages
      The most commonly used packages are Notes, Attachments, and Email.
    - Checking which packages have been applied to a schema
      Before you apply new packages or package versions, you can check which package versions have already been applied to a schema.
    - Upgrading packages
      This topic explains the concept of upgrading packages in DevOps Plan.
    - The AuditTrail and eSignature packages
    - EmailPlus package
    - Attachments package
      The Attachments package stores record attachments on an external server instead of in the DevOps Plan database.
    - Visualization package
      The Visualization package helps to enable the creation of custom Kanban boards in DevOps Plan.
    - Exploratory package
      The Exploratory package helps to enable the use of the Exploratory Test Charter feature in DevOps Plan.
    - Capacity Planning package
      The Capacity Planning package helps to enable the use of the Capacity Planning feature in HCL DevOps Plan.
  - Test Management and Requests
    You can use the DevOps Plan TestManagement and Requests feature to create and track test plans and add approval processes to the record.
  - Working with Forms
    You must create a record form for each record type in your schema. You can also define a submit form for each record type.
  - Working with charts
    Charts are essential tools for visualizing data and managing projects. You can use Gantt and timeline charts for project management based on availability in different schemas.
  - Working with approvals
    Users can use Approvals to view and manage approval requests that are either pending or completed using the Pending Requests and Completed Requests tabs.
  - Creating a security model
    This topic provides an overview of the process to create a security model.
  - Using hooks to customize your workflow
    This topic provides guidelines for using hooks to implement your workflow.
  - Record locking
    When multiple users attempt to simultaneously update a record, the database locking model ensures that the update from each user succeeds as a unit, but each update overwrites the previous update.
  - Customizing the Web
    The Designer provides many ways to customize the underlying schema and functionality that the DevOps Plan Web client accesses.
  - DevOps Plan email
    This topic provides a description of the supported DevOps Plan Web client email features.
  - Importing and exporting data
    This topic describes how to import and export data between DevOps Plan databases, and how to import data into a DevOps Plan database from another defect tracking system.
  - Importing data into DevOps Plan using Import feature
    The Configuration > Import feature allows teamspace admins or userdb super-users to add data to the DevOps Plan application. There are two primary methods for bulk data import: using sample data and uploading a zip file.
  - Enhancing the Export to JSON feature
    You can use the Export to JSON feature to export detailed information related to a record into a JSON format.
  - Cloning existing records
    By cloning existing records you can create an exact copy of an existing record. This ability is useful when you have to create similar records frequently, ensuring consistency and saving time.
Integrating
You can integrate DevOps Plan with other software by adding packages to existing schema.
Extending product function
Learn how to extend the product.

Visualization package

The Visualization package helps to enable the creation of custom Kanban boards in DevOps Plan.

The Visualization package is used by the Custom Kanban Board feature of DevOps Plan. You must apply this package in order to use this feature.

The Visualization package adds the following fields to a record type being enabled for "Custom Kanban Board":

Title of type SHORT_STRING (254)
StateDate of type DATE_TIME
Owner of type REFERENCE to users record type
Tags of type MULTILINE_STRING
Description of type: MULTILINE_STRING
DescriptionPT of type MULTLINE_STRING
Priority of type SHORT_STRING (254)

If the record type for which the Visualization package is being applied has one or more of those fields, you cannot apply the package. You must exampine the record type and manually add the missing field(s) with the correct type as listed above.

To learn more about packages and how to apply the Visualization package, see Packages and integrations.