﻿<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
	<channel>
		<title>SB Project Management — Changelog</title>
		<link>https://www.sbassistant.com/</link>
		<description>New features, improvements, and fixes in SB Project Management.</description>
		<copyright>2026</copyright>
		<pubDate>Tue, 21 Jul 2026 00:18:48 GMT</pubDate>
		<lastBuildDate>Tue, 21 Jul 2026 00:18:48 GMT</lastBuildDate>
		<item>
			<title>A better fit on your phone</title>
			<link>https://www.sbassistant.com/project/changelog/mobile-pass</link>
			<description>&lt;p&gt;The app now behaves properly at phone width. The header no longer overflows, menus and the navigation drawer size themselves to small screens, and task rows wrap instead of forcing sideways scrolling.&lt;/p&gt;</description>
			<guid>https://www.sbassistant.com/project/changelog/mobile-pass</guid>
			<pubDate>Sun, 19 Jul 2026 00:00:00 GMT</pubDate>
			<content:encoded>&lt;p&gt;The app now behaves properly at phone width. The header no longer overflows, menus and the navigation drawer size themselves to small screens, and task rows wrap instead of forcing sideways scrolling.&lt;/p&gt;
&lt;h3 id="where-youll-see-it"&gt;Where you'll see it&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;The app shell — header, menus, and footer — on any phone-sized screen.&lt;/li&gt;
&lt;li&gt;Task lists and board cards, which wrap long content instead of clipping it.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;No switches to flip — open the app on your phone and the layout takes care of itself.&lt;/p&gt;
</content:encoded>
			<comments xmlns="http://purl.org/rss/1.0/modules/slash/">0</comments>
		</item>
		<item>
			<title>Per-project custom fields</title>
			<link>https://www.sbassistant.com/project/changelog/custom-fields</link>
			<description>&lt;p&gt;Every project tracks something the standard fields don't cover — an environment, a ticket number, a client priority. Projects can now define their own fields, and every task in the project carries them.&lt;/p&gt;</description>
			<guid>https://www.sbassistant.com/project/changelog/custom-fields</guid>
			<pubDate>Sat, 18 Jul 2026 00:00:00 GMT</pubDate>
			<content:encoded>&lt;p&gt;Every project tracks something the standard fields don't cover — an environment, a ticket number, a client priority. Projects can now define their own fields, and every task in the project carries them.&lt;/p&gt;
&lt;h3 id="how-it-works"&gt;How it works&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Define a project's fields in its settings.&lt;/li&gt;
&lt;li&gt;Set values on any task from the task's detail view.&lt;/li&gt;
&lt;li&gt;Values show up in the list and board views, so the data lives where you actually work.&lt;/li&gt;
&lt;/ul&gt;
</content:encoded>
			<comments xmlns="http://purl.org/rss/1.0/modules/slash/">0</comments>
		</item>
		<item>
			<title>Automations: let the board do the busywork</title>
			<link>https://www.sbassistant.com/project/changelog/automations</link>
			<description>&lt;p&gt;The predictable follow-ups — moving a card, reassigning it, flagging overdue work — can now run themselves. Each project can define automation rules that fire when something happens on the board.&lt;/p&gt;</description>
			<guid>https://www.sbassistant.com/project/changelog/automations</guid>
			<pubDate>Sat, 18 Jul 2026 00:00:00 GMT</pubDate>
			<content:encoded>&lt;p&gt;The predictable follow-ups — moving a card, reassigning it, flagging overdue work — can now run themselves. Each project can define automation rules that fire when something happens on the board.&lt;/p&gt;
&lt;h3 id="how-it-works"&gt;How it works&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Build a rule as a trigger plus an action — for example: when a task reaches a stage, assign it to someone.&lt;/li&gt;
&lt;li&gt;A daily sweep handles due-date triggers too, so overdue rules fire even when nobody touches the task.&lt;/li&gt;
&lt;li&gt;Manage a project's rules from its settings.&lt;/li&gt;
&lt;/ul&gt;
</content:encoded>
			<comments xmlns="http://purl.org/rss/1.0/modules/slash/">0</comments>
		</item>
		<item>
			<title>Tasks can now depend on other tasks</title>
			<link>https://www.sbassistant.com/project/changelog/task-dependencies</link>
			<description>&lt;p&gt;Some work can't start until other work finishes. You can now link a task to the tasks it depends on, so the order of operations is visible instead of living in someone's head.&lt;/p&gt;</description>
			<guid>https://www.sbassistant.com/project/changelog/task-dependencies</guid>
			<pubDate>Sat, 18 Jul 2026 00:00:00 GMT</pubDate>
			<content:encoded>&lt;p&gt;Some work can't start until other work finishes. You can now link a task to the tasks it depends on, so the order of operations is visible instead of living in someone's head.&lt;/p&gt;
&lt;h3 id="how-it-works"&gt;How it works&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Add &lt;em&gt;depends on&lt;/em&gt; links from the task's detail view.&lt;/li&gt;
&lt;li&gt;A task with unfinished dependencies shows a blocked indicator wherever it appears, so you can see what's waiting before anyone starts it.&lt;/li&gt;
&lt;li&gt;Dependencies are advisory — they flag the conflict rather than hard-locking the task, so an urgent exception never has to fight the tool.&lt;/li&gt;
&lt;/ul&gt;
</content:encoded>
			<comments xmlns="http://purl.org/rss/1.0/modules/slash/">0</comments>
		</item>
		<item>
			<title>Task templates: build it once, reuse it everywhere</title>
			<link>https://www.sbassistant.com/project/changelog/task-templates</link>
			<description>&lt;p&gt;Repeatable work shouldn't mean retyping the same task every time. There's now a company-wide template library: save a task description or checklist as a template, then pull it into any project.&lt;/p&gt;</description>
			<guid>https://www.sbassistant.com/project/changelog/task-templates</guid>
			<pubDate>Sat, 11 Jul 2026 00:00:00 GMT</pubDate>
			<content:encoded>&lt;p&gt;Repeatable work shouldn't mean retyping the same task every time. There's now a company-wide template library: save a task description or checklist as a template, then pull it into any project.&lt;/p&gt;
&lt;h3 id="how-it-works"&gt;How it works&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;When writing a task description, pick a template to prefill it.&lt;/li&gt;
&lt;li&gt;Checklist templates drop a ready-made checklist onto the task in one click.&lt;/li&gt;
&lt;li&gt;Templates are shared across your company, so the whole team draws from one library instead of everyone keeping private copies.&lt;/li&gt;
&lt;/ul&gt;
</content:encoded>
			<comments xmlns="http://purl.org/rss/1.0/modules/slash/">0</comments>
		</item>
		<item>
			<title>Richer task descriptions and comments with Markdown</title>
			<link>https://www.sbassistant.com/project/changelog/markdown-task-descriptions</link>
			<description>&lt;p&gt;Task descriptions and comments now render Markdown — headings, lists, links, bold, inline &lt;code&gt;code&lt;/code&gt; — so a task can carry real structure instead of one long paragraph.&lt;/p&gt;</description>
			<guid>https://www.sbassistant.com/project/changelog/markdown-task-descriptions</guid>
			<pubDate>Thu, 02 Jul 2026 00:00:00 GMT</pubDate>
			<content:encoded>&lt;p&gt;Task descriptions and comments now render Markdown — headings, lists, links, bold, inline &lt;code&gt;code&lt;/code&gt; — so a task can carry real structure instead of one long paragraph.&lt;/p&gt;
&lt;h3 id="how-it-works"&gt;How it works&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Write plain text as before; the formatting renders when you save.&lt;/li&gt;
&lt;li&gt;Long descriptions get an expandable editor, and the rendered text sits in its own panel on the task drawer.&lt;/li&gt;
&lt;li&gt;Formatting is limited to safe Markdown — raw HTML is ignored.&lt;/li&gt;
&lt;/ul&gt;
</content:encoded>
			<comments xmlns="http://purl.org/rss/1.0/modules/slash/">0</comments>
		</item>
		<item>
			<title>Team leads can now manage their own teams</title>
			<link>https://www.sbassistant.com/project/changelog/team-delegation</link>
			<description>&lt;p&gt;Managing who's on a team no longer requires a company admin. Managers can create teams, and each team's lead can add or remove members and control which projects the team can reach.&lt;/p&gt;</description>
			<guid>https://www.sbassistant.com/project/changelog/team-delegation</guid>
			<pubDate>Tue, 30 Jun 2026 00:00:00 GMT</pubDate>
			<content:encoded>&lt;p&gt;Managing who's on a team no longer requires a company admin. Managers can create teams, and each team's lead can add or remove members and control which projects the team can reach.&lt;/p&gt;
&lt;h3 id="how-it-works"&gt;How it works&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Managers and above can create teams; whoever creates one becomes its lead.&lt;/li&gt;
&lt;li&gt;A team lead can manage their own team's membership and project access — no admin needed.&lt;/li&gt;
&lt;li&gt;Archiving a team stays admin-only.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="who-it-affects"&gt;Who it affects&lt;/h3&gt;
&lt;p&gt;Admins keep full control of every team. The change is for growing companies where one person shouldn't be the bottleneck for every roster tweak.&lt;/p&gt;
</content:encoded>
			<comments xmlns="http://purl.org/rss/1.0/modules/slash/">0</comments>
		</item>
	</channel>
</rss>