Support
Kanban boards
For: Managers and members
Every project has a board of issues. Managers decide the columns and who may move issues between them; members and your customers then work on the same cards. This article follows that order.
Design the workflow
The columns and the allowed moves are one workflow for the whole workspace. Only workspace managers see it: open Workspace and choose the Issue Workflow tab.
Columns
A new workspace starts with three columns: To Do, In Progress and Done, and any move between them is allowed. Under Columns you can:
- Click “Add status” and type a name. “Add” puts it at the bottom of the list.
- Rename a status in place. Renaming never touches the issues in it.
- Pick a colour from the swatch, and a category: Open, In Progress, Done or Declined.
- Move a status up or down with the arrows. The order is the order of the board columns.
- Delete a status. If issues use it, a dialog asks where to move them (“Delete & move”). You cannot delete the last status.
The category is not decoration. Done and Declined count as finished: the dashboard hides issues in those columns once they are older than two weeks.
Transitions
Under Transitions you draw which moves are allowed. Drag from one column to another to add an arrow. Hover an arrow to show two toggles and a delete button:
| Control | Meaning |
|---|---|
| U (“Toggle users”) | Your team (workspace members) may make this move. |
| C (“Toggle customers”) | Customer contacts may make this move from the client portal. |
| Delete transition | Removes the arrow. An arrow with neither U nor C is not kept. |
- With no arrows at all, issues can move freely between any statuses, for everyone. The page says so: “No moves defined, so issues can move freely between any statuses.”
- Drawing the first arrow restricts everything else. From then on only the arrows you drew are allowed, for the actor each one lists. Draw every move you want to keep.
- Moving a card inside its own column is never a transition and is always allowed.
Who bypasses the workflow
Workspace managers and the project’s leads can move an issue to any existing column, whatever the arrows say. Make someone a lead with “Make lead” on the project’s Users tab (seeProjects). Everyone else, members and customer contacts alike, is held to the arrows. A blocked drop snaps the card back and shows “This status change is not allowed by the workspace workflow.”
Saving
Click “Save workflow”; the toast says “Workflow saved”. “Reset” discards unsaved edits after a confirmation. If you leave the tab with unsaved changes you are asked “Discard workflow changes?”. If another manager saved first you get “Workflow changed elsewhere. Your edits are kept — review and Save again to apply.”
Work on a board
The same board appears on the Dashboard, on every project page below its tabs, and in the customer portal. Which issues it shows depends on where you are.
| Board | Shows |
|---|---|
| Project page | Every issue of that project. Workspace managers see it for every project; other members only for projects they can access (public projects, or ones they are a member of). |
| Dashboard | Issues from all your accessible projects, managers included. Done and Declined issues older than two weeks are hidden, with a note under the board. |
Boards never show issues of an archived customer, project or task. Such an issue can still be opened by its key but is read-only.
Create an issue
- Click “New issue” at the top of the first column.
- Type a Title (at least 2 characters, at most 200), pick the Project (fixed on a project board) and optionally a Task, an Assignee and a Description.
- Click “Create”. The issue starts in the initial status and gets a key such as P3-7.
The key is the project key and a running number, and it never changes. The Assignee list has two groups, Members and Customers: an issue can go to one of your team or to a customer contact who has board access to the project.
Move and edit
- Drag a card to another column, or within a column to reorder. While you drag, columns you may drop on get a green outline and the others are dimmed.
- Click a card to open it. Title, Status, Assignee and Task save as you change them; the Description has its own Save button.
- Each column shows about five cards and scrolls beyond that. An empty column folds into a narrow strip with its title and a count; you can still drop on it.
- Frozen issues (archived customer, project or task, or an inactive task) cannot be edited, moved or deleted by anyone.
Quick filters
Above the board: avatars to filter by assignee (with an Unassigned chip), and Project and Task pills (Project only where the board mixes projects). Select several values, then “Clear all” to reset. Filters only hide cards; the URL keeps them, so you can share a filtered view.
Live refresh
An open board checks for changes every 15 seconds and when you return to the tab. A hidden tab does not refresh. Issues created by a colleague or by the bot appear without reloading.
Write an issue
Description and comments use the same editor and are stored as Markdown. Both are capped at 5000 characters.
The editor
The toolbar offers Bold, Italic, Strikethrough, Inline code, Code block, Bullet list, Numbered list, Link and “Attach file”. Links accept http, https and mailto and open in a new tab. Click a saved description to edit it, then “Save” or “Cancel”.
Comments
- On the Comments tab type under “Add a comment…” and click “Comment”. Comments are a single flat list; there are no replies.
- You can edit or delete only your own comments, from the menu on the comment.
- Customer contacts comment from the portal; their comments show their name.
Mentions
Type @ in a description or comment and pick a person. The list holds the people you could assign the issue to: members with access to the project and customer contacts with board access. A mentioned person becomes a recipient of the email digest.
Attachments
- The Attachments tab takes files by drag and drop or “Attach file”. The dropzone says “Up to 25.0 MB per file”; any file type is accepted.
- A second file with the same name on the issue is refused with “File name already exists”; the dialog suggests a name such as
name (2).extto upload instead. - Images and PDFs open in a new browser tab; everything else, SVG included, downloads.
- Anyone who can open the issue can add or remove attachments, not only the uploader. A frozen issue allows neither, but its files can still be opened.
Pictures inside text
Paste an image into a description or comment, or use the toolbar’s “Attach file”, and it appears inline; drag its corner to resize. These files also list on the Attachments tab, but they have no delete button: they go away when you remove them from the text, once no description or comment on the issue uses them. An image pasted into a draft you then cancel is deleted too.
Link and reference issues
Two separate things connect issues: “Related issues” are recorded links, and the
# reference is a chip inside text.
Related issues
- Open the issue and choose the “Related issues” tab.
- Click “Link issue”, search by key or title and pick the other issue. The toast says “Issue linked”.
- Remove a link with the cross on its row and confirm. The toast says “Link removed”.
- Both issues must belong to the same project. A link to yourself or a link that already exists is refused.
- A link shows on both issues and is written to the history of both.
- Customer contacts can link and unlink issues in the portal as well.
# references in text
Type # in a description or comment and pick an issue of the same project. It becomes a chip with the key, the current title and the status; clicking it opens the issue in a new tab (while you are editing, Ctrl or Cmd and click). A chip for an issue that cannot be found is greyed out and struck through. A reference creates no link and sends no notification.
# in time entry comments
The same picker works in a time entry’s comment: the member’s Details dialog on Timesheets, the entry comments on the approval page, and the entry comment on a statement. It needs the entry’s project; the two dialogs then show the hint “Type # to reference an issue”.
- The picker inserts the bare key and a space, for example
P3-7. Time entry comments are plain text with a 250-character limit, so no link is stored. - The key shows as plain text on reports, statements and exports. Nothing checks that a key you typed by hand exists.
- Issues of the entry’s task are listed first.
Email notifications
OneShift emails a digest instead of one message per edit. The email goes out once an issue has been quiet for 5 minutes, and a check runs every minute, so it arrives a little later than that.
Who receives it
- The creator, the current assignee, the project’s leads, everyone who commented or changed the issue, and everyone mentioned with
@. - You never get mail about your own changes. If others also edited in the same burst, you get the digest with just their changes.
- Team members need current access to the project: public, or they are a project member.
- Customer contacts are mailed only while they have Board access to the project, checked when the mail is sent. Removing the access drops them even if they are the assignee.
What the mail looks like
The subject is [Project name] KEY: Issue title. Team members get a link to the issue in the app; contacts get a link to the issue in the portal.
What does not send mail
- Reordering a card without changing its status.
- An issue deleted before the 5 minutes pass.
Delivery is at least once: after a failure a digest can arrive twice. When a person says they got no email, check their access first.
Delete issues and read the history
Deleting is rare and permanent. The history is what you use to see what happened.
Deleting an issue
- Open the issue and choose “Delete issue” from the menu (the three dots).
- Confirm. The toast says “Issue deleted”.
| Who | May delete |
|---|---|
| Workspace managers and project leads | Any issue in the project. |
| Other members | Only issues they created. Otherwise the server says “You can only delete issues you created.” |
| Customer contacts | Only issues they created in the portal. |
Comments, history, links and attachments are deleted with the issue and it cannot be undone. A frozen issue cannot be deleted by anyone.
The History tab
Each change is one line with the person, the time and the change: “created this issue”, “changed status” (from one status to another), “changed assignee from … to …”, “changed the title to …”, “edited the description”, “changed task from … to …”, “commented”, “edited a comment”, “deleted a comment”, attachments added and removed, and links added and removed. Changes made together are grouped. Edits made by customer contacts show the contact’s name. The issue also shows who created it and when it was created and last updated.
The Issues report
The Issues report lists every issue in the workspace in one table. It is for workspace managers; open it from Reports → Issues, or go to the report.
- Filter by Customer, Project, Task, Assignee and Status, then click “Apply”. “Clear all” resets the filters. Customer, Project and Task have an active/archived switch that starts on active only.
- Columns: Key, Title, Customer · Project · Task, Assignee and Status. Key, Title and Status sort; status sorts in board order, not alphabetically. A key opens the issue in a new tab.
- Unlike boards, the report includes issues of archived customers, projects and tasks, shown struck through. An empty result reads “No issues match your filters.”
For the other reports, seeReports.