Creating and Managing Work Items

Overview

Work items (cards) are the unit of work in StretchProjects. This walkthrough covers creating an item, filling out its fields, editing and reassigning it, moving it between stages, and removing it — plus how each action is logged.

Create a new item

1. From a board, click New item in the toolbar, or the + on a column header to pre-select that stage.
2. In the New item form, complete the fields:
- Title (required) — the name of the work.
- Short description / description — a summary and optional full detail.
- Item type — a category such as task, docs, content, or admin.
- Column / status — which stage the item starts in (defaults to Planned).
- Priority — Low, Medium, High, or Critical.
- Owner — the person accountable.
- Assignees — a comma-separated list of people working on it.
- Due date and Target release — pick dates.
- Labels — comma-separated tags (e.g. seo, admin, platform).
- Related app / related brand — optionally connect the work to a suite app or brand.
3. Click Create item. The card appears in the chosen stage, receives a URL-safe key derived from its title, and a "created" event is logged.

Tip: Reuse a starting point with Templates. The New item form has a template picker — apply a saved template to pre-fill the fields, or save the current fields as a new template. See Templates, Collaboration & Customer Linking.

Example

To track a new content page, you create an item titled "StretchCreative pricing page", set Item type = content, Priority = Medium, Column = Planned, add labels content, pricing, public, and set a Target release date. It lands in the Planned column, ready to be scheduled, and appears in your task queues by its due date.

Understand priority

Priority is shown as a colored chip on the card and in tables:

Set a priority on every item so the dashboard's High priority, Overdue, and Due today counts stay meaningful.

Use documentation flags

Items can carry delivery-standard flags that appear as chips on the card:

• KB — a public knowledge-base article is required.
• Ops Doc — an internal operations doc is required.
• Changelog — the change must be logged for release.

These flags roll up into the dashboard's Docs required and Changelog required counts, so nothing ships undocumented. See Documentation Flags and Delivery Standards for how to use them as a gate.

Edit an item

1. Click a card to open its detail panel.
2. In Project details, change any field — title, description, type, stage, priority, owner, assignees, dates, or labels.
3. Click Save item. The status and priority chips update, and an "updated" event records the change on the item's timeline.

If you change the stage while editing (rather than dragging), StretchProjects moves the card to that column and syncs its status, just like a drag.

Reassign work

Change the Owner to move accountability, or edit the Assignees list to change who's working on it. Both are saved with the item and captured in its history, so it's always clear who picked up or handed off a piece of work.

Move an item between stages

You can move a card three ways, all equivalent:

1. Drag and drop it onto another column.
2. Use the card's Move to stage dropdown.
3. Change the Column / status field in the detail panel and save.

Each records a move and updates the card's status to match the new stage.

Delete an item

1. Open the item's detail panel.
2. Click Delete (bottom-left).
3. Confirm. The item is removed from the board and the action is recorded.

Tips

• The Create button stays disabled until you enter a Title — it's the one required field.
• Fill in Due and Target release dates so items surface in the Today/Upcoming queues and the dashboard's overdue counts.
• Use consistent, lowercase labels across items so filtering and grouping stay clean.

Note on the admin surface

On the workspace/client surface, writes are authorized through your signed-in session. On the admin surface, creating, editing, moving, and deleting are protected writes — you'll be asked to re-enter your admin password to authorize each one, minting a short-lived, single-use token that is never stored. See The Admin Surface and Step-Up Authorization.