{"id":18,"date":"2026-04-12T13:24:00","date_gmt":"2026-04-12T13:24:00","guid":{"rendered":"https:\/\/demo.fasterthemes.com\/mywiki-wordpress-theme\/task-fields-priorities-and-due-dates\/"},"modified":"2026-04-12T13:24:00","modified_gmt":"2026-04-12T13:24:00","slug":"task-fields-priorities-and-due-dates","status":"publish","type":"post","link":"https:\/\/demo.fasterthemes.com\/mywiki-wordpress-theme\/task-fields-priorities-and-due-dates\/","title":{"rendered":"Task fields, priorities, and due dates"},"content":{"rendered":"<p class=\"has-large-font-size\">Lattica gives you a small set of standard fields out of the box and lets you add custom ones when you need them. The trick is using as few as possible.<\/p>\n<h2>Standard fields<\/h2>\n<p>Every task has these from the moment you create it:<\/p>\n<ul>\n<li><strong>Title<\/strong> \u2014 keep it action-oriented. &#8220;Fix login redirect on Safari&#8221; beats &#8220;Login bug.&#8221;<\/li>\n<li><strong>Description<\/strong> \u2014 Markdown supported, including code blocks, tables, and embeds.<\/li>\n<li><strong>Assignee<\/strong> \u2014 exactly one person. If two people are responsible, neither is.<\/li>\n<li><strong>Status<\/strong> \u2014 workflow position; defaults to <em>Todo \/ In progress \/ In review \/ Done<\/em>.<\/li>\n<li><strong>Priority<\/strong> \u2014 <em>Low \/ Medium \/ High \/ Urgent<\/em>.<\/li>\n<li><strong>Due date<\/strong> \u2014 date, optionally with time of day.<\/li>\n<\/ul>\n<h2>Priority \u2014 the rule of one Urgent<\/h2>\n<p>If everything is Urgent, nothing is. Lattica shows a soft warning when you mark more than three Urgent tasks at once. The intended ratio across a healthy backlog: 5% Urgent, 25% High, 50% Medium, 20% Low.<\/p>\n<p>Priority drives default sort order on every view, and feeds into the <em>Today<\/em> dashboard which surfaces what to work on next.<\/p>\n<h2>Due dates and the calendar<\/h2>\n<p>Due dates can be a single date, a date with time, or a range (start \u2192 end). Range dates show as bars on the timeline view; single dates show as points on the calendar view.<\/p>\n<p>Working hours and weekends are configured per workspace. Lattica won&#8217;t auto-shift due dates onto a weekend \u2014 but it won&#8217;t auto-skip them either. That&#8217;s a deliberate choice; we found auto-skipping caused more confusion than it solved.<\/p>\n<h2>Custom fields<\/h2>\n<p>Add fields per project, per task type, or workspace-wide. Supported types:<\/p>\n<ul>\n<li>Single-select dropdown<\/li>\n<li>Multi-select (tags-style)<\/li>\n<li>Number (integer or decimal, with unit suffix)<\/li>\n<li>Currency (with currency code)<\/li>\n<li>URL<\/li>\n<li>Person<\/li>\n<li>Date<\/li>\n<li>Formula (computed from other fields)<\/li>\n<\/ul>\n<p>Resist the urge to add too many. Most teams that succeed with Lattica use 0-2 custom fields per project. The most common: <em>Customer<\/em> (person), <em>Sprint<\/em> (single-select), <em>Estimate<\/em> (number).<\/p>\n<h2>Required fields<\/h2>\n<p>You can mark any field as required for tasks to leave a particular status. For example, <em>Estimate must be set before a task can move to &#8220;In progress.&#8221;<\/em> Use sparingly \u2014 required fields are friction, and friction is sometimes warranted but usually isn&#8217;t.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The standard fields, the rule of one Urgent, custom fields, and when to make fields required.<\/p>\n","protected":false},"author":0,"featured_media":19,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[21,20,18,19],"class_list":["post-18","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-projects-tasks","tag-fields","tag-priority","tag-tasks","tag-workflow"],"_links":{"self":[{"href":"https:\/\/demo.fasterthemes.com\/mywiki-wordpress-theme\/wp-json\/wp\/v2\/posts\/18","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/demo.fasterthemes.com\/mywiki-wordpress-theme\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/demo.fasterthemes.com\/mywiki-wordpress-theme\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/demo.fasterthemes.com\/mywiki-wordpress-theme\/wp-json\/wp\/v2\/comments?post=18"}],"version-history":[{"count":0,"href":"https:\/\/demo.fasterthemes.com\/mywiki-wordpress-theme\/wp-json\/wp\/v2\/posts\/18\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/demo.fasterthemes.com\/mywiki-wordpress-theme\/wp-json\/wp\/v2\/media\/19"}],"wp:attachment":[{"href":"https:\/\/demo.fasterthemes.com\/mywiki-wordpress-theme\/wp-json\/wp\/v2\/media?parent=18"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/demo.fasterthemes.com\/mywiki-wordpress-theme\/wp-json\/wp\/v2\/categories?post=18"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/demo.fasterthemes.com\/mywiki-wordpress-theme\/wp-json\/wp\/v2\/tags?post=18"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}