---
title: "Managing ticket projects"
canonical: "https://support.appfire.com/space/FD/1802338447/Managing%20ticket%20projects"
format: markdown
---
> Macro (aura-html)

Once you connect Flow with your ticket vendor, manage your projects on the *Ticket projects* page. Data from [Jira](https://appfire.atlassian.net/wiki/spaces/FD/pages/1802436761) and [ADO services](https://appfire.atlassian.net/wiki/spaces/FD/pages/1801912418) appears in all ticket-based reports and is eligible for [ticket project configuration](https://appfire.atlassian.net/wiki/spaces/FD/pages/1802010869). 

Ticket data from other vendors is only available in the Work log. These projects are not eligible for ticket project configuration.

## Access Ticket projects

To find the *Ticket projects* page:

1. In the top navigation bar, click **Settings**.
2. In the left navigation under *Integrations*, click **Ticket projects**.

![Ticket projects page.](media://f299e25e-e270-4507-93a3-f35b42311071)

## Manage ticket projects

The *Ticket projects* page gives you an overview of all your ticket projects across each Integration. See the project's key or ID, the integration associated with each project, who added it, when it was last updated, and its current status.

On the *Ticket projects* page, there are two tabs:

- The **Imported** tab lists all ticket projects that have already been imported into your account.
- The **Available** tab lists all ticket projects available to import.

### Refresh ticket projects

Click the **Refresh project list** button to refresh your ticket projects.

Refreshing your ticket projects forces a project discovery, which pulls a new list of all the ticket projects in your vendor system. This is particularly helpful if you are not seeing a project in your list, or if a new project has been created but not yet imported.

Flow automatically refreshes ticket projects periodically, but a manual refresh can help bring in new data sooner.

### Advanced filters

Use the advanced filters to find specific projects.

To use these filters:

1. Click **Show filters** next to the search box.
2. Select your filtering criteria from the advanced filters list.

![Ticket projects page filters.](media://81ce6bef-4a37-4350-8e34-0bc815aa056f)

You can create multiple filters using the **Add filter** button.

### Remove projects

You can remove ticket projects directly on the *Ticket projects* page. 

1. In the **Imported** tab, select the project(s) you want to remove.
2. Click the **Actions** button. From the dropdown, click **Remove selected**.

This action will delete the selected ticket projects and their associated ticket data.

![A dropdown under the actions button.](media://93d54e25-4835-430a-b5a2-f03bbf853217)

Alternatively, you can remove imported ticket projects from the integration details page of the integration under which they were imported.

1. Click **Settings** > **Integrations** in the left navigation.
2. Select an integration.
3. In the integration list, set the **Import **toggle to **off**. This removes the project and its data from your ticket projects list. A message appears confirming your selection.
4. Click **Yes, remove ticket data**.

You successfully deleted your project.

### Assign investment layer fields

> 📝 This action is available only to projects from full-featured integrations (Jira and ADO).

To assign the investment layer field to projects:

1. In the **Imported** tab, select the project(s).
2. Click the **Actions** button. From the dropdown, click **Assign investment layer fields**.
3. The **Bulk edit configuration** modal displays. On the modal, open a dropdown and select the field that contains the investment identifier in the ticket project.

![Bulk edit configurations modal.](media://fa842863-b7ee-47f7-8ee3-5c0ec128d2e1)

4. Confirm actions with the **Apply** button. The field you select will apply to all ticket projects you selected.

Learn more about [ticket project configurations](https://appfire.atlassian.net/wiki/spaces/FD/pages/1802010869) > Investment layers.

### Copy vendor ID

You can copy the vendor ID if you want to track down what a specific project is in your source system.

1. In the **Imported** or **Available** tab, locate the ticket project.
2. In the **Vendor ID** column, click the **copy ID** icon.

![Copying vendor ID.](media://a534bb3e-34ec-4145-8b96-afd3de5d18ea)

### Include projects with limited configuration features

If you want to see only fully configurable projects, toggle off **Include projects with limited configuration features**.

![Include projects with limited configuration features toggle.](media://5eb0f631-50cb-48d1-b2e0-7a09a6e68198)

### Import ticket projects

1. In the **Available** tab, select the ticket project(s) you want to import.
2. Click the **Actions** button. From the dropdown, click **Import selected**.

![Import selected option on the dropdown under the Actions button.](media://f88fb383-538d-45c5-aa06-1451809099ef)

This approach is helpful if you want to import multiple projects. If you want to import one project or a project one by one, you can use the **Actions** button > **Import selected **option or the **Import** button next to the respective project.

### Configure Jira and ADO services ticket projects 

Terms related to tickets and ticket projects vary between Flow and ticket vendors. Use this chart as a general reference for how terms differ.

| **Flow** | **Jira** | **ADO** |
| --- | --- | --- |
| Ticket | Work item | Work item |
| Ticket project | Project | Project/Board |
| Sprint | Sprint | Iteration |

For Jira and ADO services projects, you must complete additional configurations for your data to appear in ticket reports like Retrospective, Ticket log, Sprint movement, and Investment profile. Learn more about [ticket project configurations](https://appfire.atlassian.net/wiki/spaces/FD/pages/1802010869).

On the *Ticket projects* page, use the **Integration** column to identify which integration a ticket project has been ingested into. If you have multiple integrations with the same vendor, ticket projects ingested under different integrations will not have the correct association between tickets across projects, particularly when identifying epic relationships.

Use the **Configuration status **column to determine whether your ticket project is configured, has been automatically configured, or is from a vendor that is not supported for project configuration. To configure or update the configuration for an available ticket project, click **Edit configuration **in the **Configure **column.

Use the **Status mapping **column to determine which projects to pay the most attention to for configuration. There are three options for what can be in the column:

- **Unmapped** **status**: There is at least one unmapped status in the project.
- **Fully mapped** **status**: There are no statuses in the unmapped column in the project.
- **Unsupported** **vendor**: The project is not eligible for configuration.

> 📝 Even if all statuses are mapped, there are additional configurations you may need to complete to receive accurate data tailored to your workflow. Make sure to complete all [ticket project configurations](https://appfire.atlassian.net/wiki/spaces/FD/pages/1802010869) and review them regularly, particularly if you notice ticket data appearing incorrectly in Flow.