IntegrationSprint tickets with a due date get real focus time carved out, instead of hoping the sprint sorts itself out.
Quick answer
Daylo connects with Jira using the permissions listed on this page, so you can plan around the information that integration makes available.
The narrowest set that makes the features below work.
Read Jira work items
Reads the connected information so Daylo can turn it into scheduled work. It does not change it.
Create and update Jira work items
Writes back only the changes you make in Daylo.
Read Jira user
Reads the connected information so Daylo can turn it into scheduled work. It does not change it.
Maintain Jira webhook
Keeps the connection in sync so changes reach Daylo reliably.
Handle privacy requests
Lets Daylo complete a privacy request for information held in the connected tool.
Stay connected
Keeps the connection alive so you are not re-authorising every hour.
Generated from the scope list the consent screen is built from, so this cannot drift from what is actually requested. Revoke any of it from settings, or at the provider, without losing what Daylo already created.
Second item in the sidebar. Every provider Daylo supports is on one screen.
One consent screen covers every service from this provider, so you approve once rather than per app.
Existing items appear straight away. Nothing is moved or rewritten without you asking.
A ticket estimated at 5 points and due by sprint end tells you scope, not schedule. Connected, Daylo can turn a Jira ticket's due date into an actual scheduled block across the days leading up to it.
Without Jira
Story points estimated. Time not scheduled.
With Jira connected
Move a ticket to "Done" and any remaining scheduled time for it clears; move it back to "In Progress" and Daylo can find new time for what's left.
With Jira connected
Without Jira
Every integration is included on Pro. Setup takes about a minute.
