Jira

Connect Jira to Flowstate and your project effort, cost attribution, and R&D reporting updates automatically as your team works.

What syncs

From Jira	Into Flowstate	Used for
Projects or Epics	PMS Projects	Linking to roadmap projects, effort attribution
Issues (Stories, Tasks, Bugs)	PMS Tasks	Effort calculation, CapEx attribution
Issue status changes	Task activity	Effort tracking based on status movement
Assignees and reporters	Employee mappings	Attributing effort to the right people

Flowstate reads from Jira — it never writes back or modifies your boards.

How data stays in sync

Webhooks (real-time): Jira sends a notification to Flowstate when issues are created, updated, or transitioned. Changes appear in Flowstate within seconds.

Scheduled sync (catch-up): A daily full sync catches anything webhooks might have missed.

Getting started

1. Connect Jira

1. Go to Settings → Data Integrations → Jira
2. Enter your Jira instance URL (e.g., https://your-company.atlassian.net)
3. Enter your Jira email and API token
4. Click Connect & Test

How to create a Jira API token

Go to id.atlassian.com/manage-profile/security/api-tokens and create a new token. Use the email address associated with your Atlassian account.

2. Choose what to sync

Flowstate can treat Jira projects in two ways:

• Jira Projects as Flowstate projects — Each Jira project maps to a PMS project. Works well when your Jira projects align with your roadmap.
• Epics as Flowstate projects — Each Jira Epic becomes a PMS project. Better for teams that use a single Jira project with Epics for different workstreams.

3. Set up webhooks

Flowstate provides a webhook URL during setup. Configure it in Jira:

1. In Jira, go to Settings → System → Webhooks (requires admin)
2. Click Create a Webhook
3. Paste the Flowstate webhook URL
4. Select events: Issue created, Issue updated
5. Save

4. Map your people

Flowstate matches Jira users to employees by email address. If emails don't match, add manual mappings in Settings → Data Integrations → Employee Mappings.

Custom field mapping

Jira's custom fields can be mapped to Flowstate behaviours:

CapEx classification

If you have a custom field like Is Capitalised (boolean or checkbox), map it so that matching issues are automatically attributed to your CapEx cost centre.

Project name mapping

If your Epics have a custom field that references a project name (e.g., a "Product Area" field), you can map it to control which Flowstate roadmap project the Epic links to.

To configure:

1. Go to Settings → Data Integrations → Jira
2. Open Custom Field Mappings
3. Select the Jira field and the Flowstate behaviour

Sync schedule

Set the daily catch-up sync time under Settings → Data Integrations → Jira → Sync Schedule.

You can also trigger a manual sync at any time.

Troubleshooting

Projects aren't appearing

• Verify the API token has access to the Jira projects
• Check that the correct Jira URL is configured
• Try a manual sync

Epic keys like PROJ-123 aren't matching

• Make sure you've selected "Epics as projects" mode if you're using Epics

People aren't matched

• Check that Jira email addresses match Flowstate emails
• Add manual mappings for mismatched accounts