> For the complete documentation index, see [llms.txt](https://docs.ativo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ativo.io/configuration/art-program.md).

# ART (program)

### Create an ART

An ART can be created once the [teams are configured](/configuration/team.md).

Only *Ativo Programs for Jira* **administrators** can create, edit and delete ARTs ([more info](/configuration/permissions.md)).

To create a new ART:

* In the ART selector in the top navigation, click on ***Create ART***
* Enter an ART **name** and **key**, then click **Create**.
* Add **teams** to the ART. Use the handle on the left to drag teams into the desired order.\
  You can later change the team composition for a specific PI in PI settings.

<figure><img src="/files/777ma5gCsPYhpZ8cjiC5" alt=""><figcaption><p>Adding teams to the program.</p></figcaption></figure>

* Select how the ART Feature (Jira epics) pool is built. You can either:

  use a Jira filter to define the Feature pool, for example if Features are managed in a separate Jira project or backlog, or\
  use the team filters, if Features are already included in the teams’ Jira data<br>

  <figure><img src="/files/5qLBEVrlDp5WWerfcuHr" alt=""><figcaption></figcaption></figure>
* Select how the ART Team-level item scope is defined.\
  Team-level items come primarily from the team filters. You can add additional rules here that apply to all PIs in this ART.\
  \
  To keep the board focused, you can limit scope to only show team-level items whose parent Feature is also in scope for the PI.\
  \
  If you are unsure, use the default option. You can always change this later.
* Click ***Save***

#### ART team-level item scope exceptions

You can manually include specific team-level items in a PI, even when they do not match the ART team-level item scope rules.

For example, you may configure the ART to show **Only team-level items under Features in PI scope**, so the board only includes Stories, Tasks, Bugs, or custom work types whose parent Feature is in the PI. If a few additional items still need to appear on the board, add them as exceptions.

To add an exception, set the item’s [**Program / ART PI Supplementary** field](/advanced/ativo-programs-custom-fields.md) in Jira to the combined ART-PI key:

`<ART key>-<PI key>`

For example:

* ART key: `ARTABC`
* PI key: `2027Q2`
* Combined ART-PI key: `ARTABC-2027Q2`

After this value is added to the work item, the item is included in the PI even if it does not match the ART team-level item scope rule.

### Modify an ART configuration

To modify an existing ART:

* Click on **Settings >&#x20;*****ART*** in the top navigation bar.&#x20;
* Update the settings as needed.
* Click **Save**.

### Archive an ART

To archive an ART:

* Click **Settings >&#x20;*****ART*** in the top navigation bar.
* Click the **•••** menu in the top right, then select **Archive ART**.
* **Confirm** that you want to archive the ART

You can always unarchive an ART later.