Upon connecting to Jira, Rally, ADO, or GitHub, you can view your tickets in the Work log report and manage your projects on your Ticket projects page. Data from Jira and ADO services appears in ticket-based reports like Ticket log, Retrospective, Sprint movement, and Investment profile.
In this article
Managing 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 the projects, when they were last updated, and their current status.
To find the Ticket projects page:
- In the top navigation bar, click Settings.
- In the left navigation under Integrations, click Ticket projects.
Refreshing your ticket projects
Click the Refresh button to refresh your ticket projects.
Refreshing your ticket projects forces a project discovery. This is particularly helpful if you're not seeing a project in your list or if a new project was created but was not yet imported.
Flow periodically refreshes ticket projects automatically,
Using the 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 list of advanced filters.
Removing projects
Remove imported ticket projects at the integration level.
To remove ticket projects:
- Click Settings.
- Click Integrations in the left navigation.
- Click an integration.
- In the list under the integration, toggle the Import button 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.
Ticket project configurations for Jira and ADO services
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 | Issue | 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.
While on the Ticket projects page, use the Integration column to identify which integration a ticket project has been ingested under. 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. If the column says:
- 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.
Note: 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.