Your projects and SOPs can now receive email directly, turning incoming messages into tasks or runs without copying anything between tools. Replies stay with the work, and attachments come along too.
This week also brings team and project sprint schedules, automatic sprint creation, and clearer rules for where tasks belong. A cross-project task list, easier access to archived projects, and filter fixes round out the update.
Turn incoming email into work
Every project and SOP can now have its own email address. Send or forward a message to create a project task or start an SOP run, including the email text and attachments. Enable it under Project settings > Email, or choose Email address on an SOP.
The sender receives a short confirmation from your organization. Replies to that confirmation, or to the same email thread, become comments on the original task or run. Email-started runs also show the original email and replies on the run page.
You can attach more file types to tasks, task descriptions, and comments:
Spreadsheets: Excel, CSV, and OpenDocument.
Presentations: PowerPoint.
Structured text: Markdown, JSON, XML, and YAML.
Archives: zip, 7z, rar, tar, and gz.
Media: Short audio and video clips.
These join the existing image, PDF, Word, and plain-text formats. AI assistants connected through MCP can also read attached CSV, Markdown, JSON, XML, and YAML files as text.
Uploads now accept files that Windows labels differently, including CSV files identified as Excel, zip archives, and Markdown files with no reported type. Incoming email supports the same attachment types as the app, including Markdown, JSON, and files sent without a specific type.
Give each team and project the right sprint schedule
Teams and projects can now set their own sprint length, and projects can have a home team. A project's tasks follow its own sprints first, then its home team's, then the organization's. Automatic assignment never puts those tasks into an unrelated project's or team's sprint, and the team assigned directly to a task does not override that rule.
Open a team from Teams, or a project's new Sprints settings tab, to see whose schedule applies, including its length and start day. Choose Set own sprint length to configure the length, start day, and meeting lengths; Use ... instead returns to the home team's or organization's schedule. The next three sprints appear below.
Organization owners and admins can choose a project's home team. Team leads and admins can change their team's sprint length and those of projects that have it as their home team. Everyone else sees read-only settings; on plans without sprints, the settings identify which plans include them.
A project's sprint filter now includes its home team's sprints, and the team's sprint view includes tasks from projects that have it as their home team. The same settings are available through /api/sprint-settings, and project API responses now include homeTeamId and homeTeam.
New sprint schedules start in the current week, with a sprint covering today, even if you switch a schedule off and back on the same day. The AI assistant and API require a team or project to have its own sprint length before creating its sprints manually; organization sprints are unaffected. The API also clearly rejects a sprint assigned to both a project and a team, matching the assistant's existing check.
Teams and projects now correctly show and list the organization's sprints and offer the option to return to them, even when the organization has no sprint length configured. Previously, those missing controls could prevent you from removing a local schedule.
Keep sprints moving without rebuilding your plans
On plans with sprints, OKiDO now checks organization, team, and project schedules nightly and adds sprints until each has 10 remaining, counting the running sprint. Existing sprints stay unchanged, and archived projects are left alone.
Saving settings rebuilds only upcoming sprints whose dates would change. Saving unchanged values mid-sprint does nothing, including after a running sprint was closed early. When upcoming sprints are rebuilt, their tasks, sprint columns, and planned run steps move to the replacement sprints for those dates.
Your open work follows schedule changes without losing its place:
Saving or removing a sprint length reassigns applicable open tasks with deadlines to running or upcoming sprints, never finished ones. Changing a project's home team does the same for its tasks.
Setting a team's or project's first local schedule, removing it, changing a home team, or deleting a team moves unfinished tasks and their sprint columns to the corresponding time at the level the project now follows.
Saving without changing the level moves nothing, preserving tasks you placed manually.
Closing a sprint moves open tasks only to the next sprint at the same project, team, or organization level. Ending the running sprint early moves its open tasks into the new running sprint.
Choosing Use the organization's sprints instead, or the team's equivalent, ends the local running sprint today and keeps it in history with its notes. Open tasks from it and upcoming sprints move to the inherited schedule. Upcoming local sprints are removed, except those with meeting notes, which are cancelled and retained.
A sprint now remains current throughout its final day, so tasks created or moved that day land in it, and the Sprints page continues to mark it as current. Finished sprints preceding a sprint series now appear in date order rather than after upcoming sprints. Editing or deleting an upcoming organization sprint also works when another organization is selected in the sidebar.
The organization's Regenerate Upcoming Sprints button is gone: saving handles rebuilding, and nightly updates keep schedules populated. Older meeting lengths display as the nearest allowed option: none, 15, 30, 45, 60, or 90 minutes. POST /api/sprints/regenerate now accepts only those values too.
See project work together and find what matters
The Projects page now has a Projects | All tasks switch. All tasks shows open tasks from every project you can access in the selected organizations, grouped by project. You get search and the same filters, sorting, grouping, and columns as a project's List view.
Choose All tasks in the toolbar to include completed work, and click a task to open it in its project. The page remembers which view you used last, so you can return to your preferred overview.
Archived projects are now available in a collapsed Archived projects section at the bottom of the Projects page. Search and status buttons filter that section too. Archived project pages clearly show their status, and organization owners and admins can bring them back with Restore project.
Finding the right tasks is more predictable across these views:
Tasks I follow now shows only tasks you follow, rather than every task, in project List and Board views and the cross-project All tasks list.
Selecting multiple values within one filter matches any of those values. Selecting To do and In progress, for example, shows both; filters across different fields still all need to match.
Group appears only in List view, where grouping applies. Board, Calendar, and Gantt no longer show the inactive control.
Together, these changes give you more ways to bring work into OKiDO and keep it visible as your team's plans change. Try enabling an email address for a project or SOP, checking which sprint schedule your projects follow, or opening All tasks for a broader view of your work.
