> ## Documentation Index
> Fetch the complete documentation index at: https://learn.nextedy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Shared and Cross-Project Templates

> Reference a checklist template stored in another Polarion project, for both work item and document (LiveDoc) checklists.

export const LastReviewed = ({date}) => {
  if (!date) return null;
  const formatted = new Date(`${date}T00:00:00Z`).toLocaleDateString("en-US", {
    year: "numeric",
    month: "long",
    day: "numeric",
    timeZone: "UTC"
  });
  return <p className="mt-10 text-sm text-gray-400 dark:text-zinc-500 not-prose">
      Last reviewed on {formatted}
    </p>;
};

## Reference a template in another project

Checklist templates normally live in the same project as the object that uses them. To point at a template stored in a different project, prefix the template ID with the source project ID and a colon:

```text theme={null}
PROJECTID:TEMPLATEID
```

### Work item templates

1. Open **Administration > Nextedy CHECKLIST** in the project where the checklist is used (the *consuming* project).
2. Add a configuration property in the form:
   ```text theme={null}
   nextedy.checklist._TYPEID_._FIELDID_.workItemTemplateId=myOtherProject:WI-124
   ```
   For example, to reuse a `chkApproved` checklist template stored as `WI-124` in project `myOtherProject` for the `requirement` type:
   ```text theme={null}
   nextedy.checklist.requirement.chkApproved.workItemTemplateId=myOtherProject:WI-124
   ```
3. Save the property.

### Document (LiveDoc) templates

Use the equivalent `documentTemplateId` property, with the shared-project path pointing at a space/document location in the other project:

```text theme={null}
nextedy.checklist.checklist.documentTemplateId=myOtherProject:Specification/SpecificationTemplate
```

The value after the colon is the **space/document name** path inside the target project, not a work item ID.

At resolution time, the consuming project's `documentTemplateId` property is read and followed across the project boundary to the named space and document in the source project, which then acts as the checklist template source.

<Warning>
  **Cross-project document templates are not confirmed to resolve**

  A support ticket reported that a user configured a cross-project `documentTemplateId` pointing at a document template in another project ("eFLP Template Resources" referenced from "Kautex Mechatronics Template Reference"), and although the path was correctly configured, **the checklist content did not appear**. The gathered context does not confirm a fix or a documented root cause for this case. The `PROJECTID:TEMPLATEID` syntax is documented and known to work for **work item** templates; treat cross-project **document** templates as unverified until you confirm the behavior in your own environment.
</Warning>

## Verify project-level scope

Configuration properties are set per project. If you copy a document template (or an entire document type configuration) into a new project, the `documentTemplateId` / `workItemTemplateId` properties do **not** travel with it automatically — you must re-add the relevant `nextedy.checklist.*` properties in **each** target project.

<Tip>
  **Document templates reused across projects need per-project setup**

  A support ticket confirmed that when document templates are reused across projects, the checklist template / document-type mapping is **not** automatically shared — each project that uses the reused document template needs its own `nextedy.checklist._TYPEID_._FIELDID_.documentTemplateId` (or `workItemTemplateId`) property configured in **Administration > Configuration Properties**. Plan for this step whenever you copy or replicate a document template between projects.
</Tip>

## Combine with per-type or per-field targeting

The same property hierarchy used for local templates applies to shared templates — you can scope the pointer by type, field, or both, exactly as you would for a template inside the same project:

```text theme={null}
# All work items of type 'requirement' pull the 'chkApproved' checklist from another project
nextedy.checklist.requirement.chkApproved.workItemTemplateId=myOtherProject:WI-124

# Any work item type using the 'chkDone' checklist pulls from another project
nextedy.checklist.chkDone.workItemTemplateId=myOtherProject:WI-125
```

See [Create a Checklist Template](/checklist/guides/templates/create-a-template) for the full property hierarchy and how type/field scoping is resolved, and [Multiple Templates per Type and Reset on Type Change](/checklist/guides/templates/multiple-templates-per-type) if you also need to vary the template by a custom field value.

## Verification

You should now see:

* The checklist on the consuming work item or document populated with items from the cross-project template's source work item or document.
* Changes made later to the source template (in the other project) reflected the next time the checklist template is (re)applied.

If the checklist stays empty after configuring a cross-project `documentTemplateId`, treat it as the known limitation above rather than a misconfiguration — double-check the work item case works with the same project pair before spending time debugging the document case.

## See also

* [Create a Checklist Template](/checklist/guides/templates/create-a-template)
* [Multiple Templates per Type and Reset on Type Change](/checklist/guides/templates/multiple-templates-per-type)
* [Import Checklist Content](/checklist/guides/templates/import-a-checklist)
* [Set Up a Document (LiveDoc) Checklist](/checklist/guides/setup/documents)

<Accordion title="Sources">
  **KB Articles**

  * How to create checklist template?
  * Multiple templates per one work item/document type
  * How to reset Checklist to the Template on WI type change

  **Support Tickets**

  * [#497](https://support.nextedy.com/helpdesk/tickets/497)
  * [#6344](https://support.nextedy.com/helpdesk/tickets/6344)
  * [#6955](https://support.nextedy.com/helpdesk/tickets/6955)

  **Source Code**

  * `proc-checklist-src/com.nextedy.polarion.checklist/src/com/nextedy/polarion/checklist/internal/ChecklistSetupService.java`
  * `proc-checklist-src/com.nextedy.polarion.checklist/src/com/nextedy/polarion/checklist/ChecklistProduct.java`
  * `proc-checklist-src/com.nextedy.polarion.checklist/src/com/nextedy/polarion/checklist/internal/ChecklistAdminService.java`
  * `proc-checklist-src/com.nextedy.polarion.checklist/src/com/nextedy/polarion/checklist/internal/ChecklistService.java`
  * `proc-checklist-src/com.nextedy.polarion.checklist/src/com/nextedy/polarion/checklist/ChecklistItem.java`
</Accordion>

<LastReviewed date="2026-08-31" />