Float + Jira
Connect Float and Jira to Keep Resource Planning in Sync with Project Delivery
Sync your capacity planning and issue tracking so your team always knows who's working on what — no manual updates required.
Why integrate Float and Jira?
Float is the go-to resource management platform for scheduling people and tracking team capacity. Jira is the standard for agile project tracking and issue management. Float tells you who has bandwidth; Jira tells you what needs to get done. Integrating them cuts the constant context-switching between platforms and keeps your resource schedules in line with your actual project pipeline.
Automate & integrate Float & Jira
Use case
Auto-Create Float Allocations from New Jira Epics
When a new epic is created in Jira and assigned to a team member, automatically generate a corresponding allocation in Float for that person based on the epic's estimated start and end dates. Resource schedules get populated as soon as new work is committed in Jira, so over-allocation surprises don't sneak up on you later.
Use case
Update Float Allocations When Jira Issue Status Changes
Automatically adjust or remove Float time blocks when a Jira issue moves to Done, Cancelled, or a custom closed status. This stops ghost allocations from hanging around on the resource schedule after work has been completed or deprioritized, freeing up capacity for the next sprint or project.
Use case
Sync Jira Project Timelines to Float Team Schedules
When a Jira project's target start or due date changes, trigger a workflow that updates the Float allocation dates for all assigned team members on that project. Resource planning stays in lockstep with shifting delivery timelines without anyone having to touch Float manually.
Use case
Create Jira Issues from Float Allocation Notes
When a resource manager logs a new allocation in Float with specific task notes or project codes, automatically create a corresponding Jira issue or sub-task in the right project. This bridges the gap between high-level resource decisions and the granular task tracking that happens in Jira.
Use case
Alert Resource Managers When Jira Sprints Are Over Capacity
When a Jira sprint is loaded with issues that collectively exceed the assigned team members' available hours in Float, automatically send an alert via email or Slack before the sprint begins. Catching over-capacity risks early prevents burnout and delivery failures — not after the sprint is already in trouble.
Use case
Log Float Timesheet Data Back to Jira Issues as Work Logs
When team members log time against allocations in Float, automatically push those entries to the corresponding Jira issue as a work log, keeping time tracking consistent across both platforms. This is especially useful for teams that report on project actuals in Jira but schedule resources in Float.
Use case
Sync New Jira Projects to Float as Scheduled Projects
When a new project is created in Jira and tagged with a defined label or project type, automatically create a matching project in Float with the correct team members, color coding, and timeline. Every new initiative tracked in Jira has a resource plan in Float from day one.
Get started with Float & Jira integration today
Float & Jira Challenges
What challenges are there when working with Float & Jira and how will using Tray.ai help?
Challenge
Matching Users Across Float and Jira
Float and Jira each maintain separate user directories, and team members may have different email addresses, display names, or IDs in each system. That makes it hard to reliably map a Jira assignee to the correct Float person record without manual lookup tables.
How Tray.ai Can Help:
Tray.ai's data transformation tools let you build a dynamic user-mapping lookup that cross-references Jira user emails or account IDs against Float person records via the Float API. Store that mapping as a reference table and reuse it across all your integration workflows — no hardcoded user mappings needed.
Challenge
Handling Date Format and Timezone Discrepancies
Float and Jira store dates in different formats and may run on different timezone settings. When data passes between the two systems, allocation dates can shift by a day or more, producing inaccurate schedule entries.
How Tray.ai Can Help:
Tray.ai has built-in date and timezone transformation helpers that normalize date values to ISO 8601 format and convert between timezones before writing data to either platform. You can set timezone defaults at the workflow level so all date operations stay consistent regardless of where team members are located.
Challenge
Avoiding Duplicate Allocations on Re-triggered Workflows
In busy Jira environments, issues can move through multiple statuses quickly or be edited in rapid succession. Without a deduplication check, the integration can fire on every change event and create multiple Float allocations for the same issue.
How Tray.ai Can Help:
Tray.ai lets you implement idempotency logic by storing processed Jira issue IDs in a data store, or by checking Float for an existing allocation linked to a given issue before creating a new one. Conditional branching in the workflow makes sure duplicate creation attempts are skipped cleanly and logged.
Challenge
Mapping Jira Story Points to Float Allocation Hours
Float schedules work in hours per day; Jira estimates effort in story points — a relative unit whose meaning varies across teams and sprints. Translating story points into Float hour allocations requires team-specific conversion logic that neither platform provides out of the box.
How Tray.ai Can Help:
Tray.ai workflows can incorporate a configurable story-point-to-hours conversion ratio stored as a workflow variable or reference table, so each team can define their own velocity baseline. The resulting hour value then sets the Float allocation's hours-per-day field, giving resource managers a practical estimate rather than an abstract point score.
Challenge
Keeping Workflows Resilient to Jira API Rate Limits
Jira's REST API enforces rate limits that can throttle integrations during high-activity periods — sprint planning, end-of-quarter project creation bursts — causing workflow failures or missed updates if errors aren't handled gracefully.
How Tray.ai Can Help:
Tray.ai's built-in error handling and retry logic automatically detects 429 rate-limit responses from the Jira API and retries the failed request after an appropriate back-off interval. You can also configure dead-letter queues and alerting so persistently failed workflow steps get flagged for manual review instead of silently dropped.
Start using our pre-built Float & Jira templates today
Start from scratch or use one of our pre-built Float & Jira templates to quickly solve your most common use cases.
Float & Jira Templates
Find pre-built Float & Jira solutions for common use cases
Template
New Jira Epic → Float Allocation
Automatically creates a Float allocation for the assigned team member whenever a new epic is created in Jira, mapping the epic's start date, due date, and assignee to the corresponding Float fields.
Steps:
- Trigger: New epic created in a specified Jira project
- Lookup the Jira epic's assignee, start date, end date, and story point estimate
- Match the Jira user to their corresponding person record in Float
- Create a new allocation in Float with the mapped dates and a link back to the Jira epic
- Post a confirmation message to the relevant Slack channel or send an email notification
Connectors Used: Float, Jira
Template
Jira Issue Status Change → Update or Remove Float Allocation
Monitors Jira issues for status transitions to Done or Cancelled and automatically updates or deletes the corresponding Float allocation to free up capacity on the team schedule.
Steps:
- Trigger: Jira issue transitions to a configured terminal status (e.g., Done, Cancelled)
- Search Float for an existing allocation linked to the resolved Jira issue
- If found, update the allocation end date to reflect actual completion or delete it entirely
- Log the change in a Google Sheet or internal audit log for reporting
Connectors Used: Float, Jira
Template
Jira Sprint Load vs. Float Capacity Check
Runs an automated capacity check before each sprint planning session, comparing the total story points or estimated hours in an upcoming Jira sprint against each team member's available hours in Float, and flags conflicts to resource managers.
Steps:
- Trigger: Scheduled trigger fires before sprint start date (e.g., two days prior)
- Fetch all issues assigned to the upcoming Jira sprint and sum estimated hours per assignee
- Query Float for each team member's available capacity during the sprint window
- Compare planned hours against available hours and identify over-capacity individuals
- Send a structured Slack or email report to the resource manager listing conflicts
Connectors Used: Float, Jira
Template
New Float Allocation → Create Jira Sub-Task
When a new allocation is added in Float with a specific project tag or note, automatically creates a linked Jira sub-task under the relevant epic so the work is tracked at both the resource and issue level.
Steps:
- Trigger: New allocation created in Float with a designated project tag or keyword in notes
- Extract the allocation details including person, dates, hours, and project reference
- Identify the corresponding Jira epic using the project reference or custom field mapping
- Create a new Jira sub-task under the matched epic with allocation details as description
- Update the Float allocation notes with a link to the newly created Jira sub-task
Connectors Used: Float, Jira
Template
Float Time Log → Jira Work Log Sync
Automatically pushes time entries logged in Float to the corresponding Jira issues as work logs, eliminating duplicate time tracking and keeping Jira's reported actuals up to date.
Steps:
- Trigger: New or updated time entry logged in Float
- Identify the linked Jira issue using a custom field or naming convention in Float
- Format the logged hours and date into Jira's work log API structure
- Post the work log entry to the corresponding Jira issue
- Mark the Float time entry as synced using a tag or custom note to prevent duplication
Connectors Used: Float, Jira
Template
New Jira Project → Float Project Setup
Automatically creates a corresponding Float project with the correct team members and timeline whenever a new Jira project is created and labeled for resource tracking, so every initiative has a resource plan from day one.
Steps:
- Trigger: New Jira project created with a specific label or project category
- Extract project name, description, start date, target end date, and team members from Jira
- Create a new project in Float with matching metadata and color code
- Add the relevant team members to the Float project based on Jira role assignments
- Post a setup confirmation to the project's designated Slack channel
Connectors Used: Float, Jira