> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/command/prior-v26.0/features/lifecycle-editor-timeline.md).

# Lifecycle Editor & Timeline

{% hint style="warning" %}
**Previous release**

This page describes the release before v26.0, which used the classic ServiceNow forms and lists. It is kept for reference. For the current version, see [Lifecycle](/command/features/lifecycle.md).
{% endhint %}

## Lifecycle Editor

The Lifecycle Editor is part of all Portfolio Element forms in YouDesign Command. It enables admins, editors, and readers (readers with Business Owner, IT Owner, or Steward roles) to set the start date of lifecycle phases.

To access the Lifecycle Editor, open any Portfolio Element form and click the Lifecycles section.

**A** – Multiple lifecycle types may be available depending on the table configuration. Click on the lifecycle type name to expand or collapse the lifecycle phases.

**B** – All lifecycle phases are organized by the five lifecycle stages.

**C** – Lifecycle phases and start dates are grouped by lifecycle stages and sorted by order. When you enter a start date and save or update the Portfolio Element, the corresponding lifecycle visualizations update automatically.

![](https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-1d1dd42e214cb985fa5686c0a901882ba7d91a36%2F9fc36f9-lifecycle_editor.png?alt=media)

## Lifecycle Timeline

The Lifecycle Timeline appears at the top of all Portfolio Element forms.

This visualization represents all lifecycle types and phases based on their start dates, functioning as a roadmap for the specific Portfolio Element.

**A** – Displays the Portfolio Element name.

**B** – Shows the lifecycle types.

**C** – Marker indicating today’s date.

**D** – Lifecycle phase name and color as specified in the lifecycle definition table.

![](https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-60ea5b77fb27a47babffb65058fc380732cc3751%2F1013096-lifecycle_viz.png?alt=media)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ins-pi.com/command/prior-v26.0/features/lifecycle-editor-timeline.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.