Managing ticket projects
Once you connect Flow with your ticket vendor, manage your projects on the Ticket projects page. Data from Jira and ADO services appears in all ticket-based reports and is eligible for ticket project configuration.
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:
In the top navigation bar, click Settings.
In the left navigation under Integrations, click Ticket projects.
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:
Click Show filters next to the search box.
Select your filtering criteria from the advanced filters list.
You can create multiple filters using the Add filter button.
Remove projects
You can remove ticket projects directly on the Ticket projects page.
In the Imported tab, select the project(s) you want to remove.
Click the Actions button. From the dropdown, click Remove selected.
This action will delete the selected ticket projects and their associated ticket data.
Alternatively, you can remove imported ticket projects from the integration details page of the integration under which they were imported.
Click Settings > Integrations in the left navigation.
Select an integration.
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.
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:
In the Imported tab, select the project(s).
Click the Actions button. From the dropdown, click Assign investment layer fields.
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.
Confirm actions with the Apply button. The field you select will apply to all ticket projects you selected.
Learn more about ticket project configurations > 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.
In the Imported or Available tab, locate the ticket project.
In the Vendor ID column, click the copy ID icon.
Include projects with limited configuration features
If you want to see only fully configurable projects, toggle off Include projects with limited configuration features.
Import ticket projects
In the Available tab, select the ticket project(s) you want to import.
Click the Actions button. From the dropdown, click Import selected.
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.
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 and review them regularly, particularly if you notice ticket data appearing incorrectly in Flow.