Tasks
A task is the unit of work in Ithura. It has a state, an assignee, a priority, labels, dates and a description, and it keeps a record of everything that happened to it. This page covers the task itself: the views you read it in, what it holds, and the parts that behave in a way worth knowing before you rely on them.
Tasks work on every plan. The only part of this page with a plan gate is how far back the activity feed goes.
The five views
The same tasks, laid out five ways. Switch with the buttons in the toolbar. Your choice is remembered per project.
| View | What it is for | What you can edit in place |
|---|---|---|
| List | The default. Grouped rows with inline editing | State and the other pickers, inline. Add a task straight into a group |
| Board | Columns by state, or by whatever you group on | Drag a card to another column to change that field |
| Table | A spreadsheet grid with sortable columns | State, Priority and Due date. Other cells open the task |
| Calendar | A month grid, placed on the due date | Nothing. It is a read view |
| Gantt | Bars over time | Hidden on a narrow screen |
Two things differ between them more than you would expect:
- Only List and Board support drag. In List, a drag reorders rows inside one group and only for top-level tasks. In Board, a drop changes the field you grouped by, says "Task moved", and can be undone. Table and Calendar have no drag at all. Drag is off on touch devices.
- Bulk select lives in List. The checkboxes, and so the bulk action bar, are a List view feature. Table has sortable columns and no grouping; it is the view for scanning, not for operating on many tasks at once.
Calendar places a task on its due date only. A task with no due date does not appear there. When a day holds more than three, it shows "+N more".
What a task holds
- Name, required, up to 255 characters.
- State, from the project's own set. A new task starts in the project's default state.
- Priority, which starts at none.
- Assignees, labels, estimate.
- Start date and due date. The start date must not be later than the due date.
- Description, a rich document with the same editor as Pages.
- Sub-tasks, relations, attachments and links, each in its own section of the detail panel.
The person who creates a task is subscribed to it, so they get its notifications without opting in.
You can open a task in a side peek, a modal or full screen, whichever you prefer.
States and completion
Moving a task into a state in the completed group stamps it as completed. Moving it into any other state clears that stamp, so a task reopened after being closed does not keep a completion date it no longer deserves.
If the state you are moving to has an approval rule, the move is refused until the approval is in place. See Approvals and SLAs.
Sub-tasks
A task can have sub-tasks, and the detail panel lists them under Sub-tasks. Sub-tasks are ordinary tasks, so they have their own state, assignee and everything else.
Deleting a parent does not delete its children. They are detached and carry on as top-level tasks. This is deliberate: losing a tree of real work because its parent was tidied away would be worse than leaving the children behind.
Finishing a parent finishes its open sub-tasks. However the parent gets there: you move it to a completed state yourself, an agent's pull request is merged, or you close a task an agent handed back. The sub-tasks land in the same state as the parent.
Finishing a sub-task this way also ends any agent work on it. An agent part way through is asked to stop and keeps what it has on its work-in-progress branch; a run still queued is cancelled. So finishing one parent can stop work on several children you were not looking at. Nothing it had already done is thrown away.
Three things it leaves alone. A sub-task you cancelled stays cancelled, because cancelling is a decision and finishing the parent is not a reason to undo it. A sub-task already finished is not touched again. And it goes one level down: a sub-task's own sub-tasks wait for their parent rather than being swept up from above.
If a sub-task is genuinely not done when its parent is, that is worth noticing before you finish the parent rather than after.
Relations
Under Relations, use Add relation and pick a type:
| Relation | Meaning |
|---|---|
| Blocking | This task blocks the one you pick |
| Blocked by | This task is waiting on the one you pick |
| Duplicate of | The same work, recorded twice |
| Related to | Worth reading together, with no dependency |
Both sides are written, so the other task shows the inverse relation and you can follow the chain from either end.
Two limits to know:
- Relations stay inside one project. You cannot link a task to a task in another project.
- Blocking does not enforce anything. It records the dependency and shows it. It does not stop you moving a blocked task along. If you want a hard stop before work can proceed, that is what an approval rule is for.
Deleting a task stops its relations being listed on the tasks at the other end.
Comments and reactions
Comments appear in the task's feed, newest activity mixed in with them. Anyone who can see the task can comment and react, guests included.
- You can edit your own comment. It is then marked "edited", with the time on hover.
- You can delete your own comment. A project admin can delete anyone's.
- A reaction is one per person per emoji, and you can only remove your own.
- Mentioning someone notifies them.
- Comments arrive live for anyone else with the task open.
Comments are a flat list, not a thread. Replies to a specific comment are not a feature here; if you need a side conversation, the project channel is the better place for it.
Description history
Every version of a description is kept. Open History from the detail panel to read them and restore one.
Each entry is labelled so you can tell how it was written:
| Badge | What it means |
|---|---|
| Auto | A typing session, saved as you wrote |
| Edit | A deliberate save |
| Restored | The result of restoring an earlier version |
A run of typing becomes one entry rather than hundreds. The window is three minutes and slides while you keep typing, so a long session is one version, and a pause of more than three minutes starts the next one. When more than one person contributed to the same session, the author reads "Collaborative session" instead of naming one of them.
A restore is itself reversible. Before replacing the text, Ithura saves what is there now as its own version. So restoring the wrong one costs you nothing: restore again, the other way. Restoring needs Member access.
The newest 100 versions per task are kept, and a daily job trims the rest.
Activity and history
The feed records who changed what, and when: state moves, assignee and label changes, dates, relations, and description edits. Comments, votes, reactions and drafts are left out of it, since they are the conversation rather than changes to the work.
On Free, the feed goes back 30 days. Older entries are not deleted, they are just not served. They come back when the workspace moves to Starter or above. Every other part of a task is unaffected.
Saved views
A filter you will want again can be saved as a view.
- Set up the filters you want, then use Save as View in the toolbar. You get a name and nothing else to decide.
- The Views page, under the project, lists them. New View there gives you the full form: name, description, access and filters.
- A view saved from the toolbar is shared with the project. To make a private one, create it on the Views page and set Access to Private.
- Each view can be duplicated, favourited and deleted. Deleting needs you to own it, or to be a project admin.
Opening a view shows a banner with its name. Change a filter and the banner says "edited", with Save to view to keep the change and Reset to drop it.
Some views are locked, which freezes the definition so it stops drifting as people tweak filters. A locked view says so in the banner, and its filters cannot be saved over. Locking is set through the API rather than the web app, so you will meet a locked view more often than you will make one.
Bulk edit
Select tasks with the checkboxes in List view and a bar appears saying how many you picked. From it you can set state, priority, assignees or estimate, add or remove labels, move to a sprint or a module, archive, or delete.
- Everything happens in one pass, and only to tasks in the project you are in. Anything else in the selection is reported back as failed rather than silently skipped.
- Delete needs admin. Everyone sees the button; a member who presses it is told admin access is required.
- Sprint and module moves replace what was there. Assignees can be added or cleared.
- Archive is separate from delete and needs Member access.
Deleting a task is a soft delete, so it leaves the views rather than being destroyed, whatever the confirmation says.
What a guest sees
A guest in a project sees only the tasks they created themselves. Someone else's task is not just hidden from their list, it is not reachable: opening it reports that it does not exist.
Within that, a guest can comment, react and read the activity on their own tasks. They cannot create or change a task.
Troubleshooting
| What you see | What it means |
|---|---|
| "Member access required" | Creating and changing tasks needs Member or above. Guests can comment but not edit. |
| "Admin access or issue ownership required" | Deleting a task needs admin, the delete permission on a custom role, or being the person who created it. |
| "Issue not found" | Either it does not exist, or you are a guest and it is not yours. The two are deliberately indistinguishable. |
| "Approvals required before transitioning to this state" | The target state has an approval rule that has not been satisfied. |
| "Refusing to clear a substantial description without force_description" | You cleared a long description in one move. It is a guard against an accidental wipe, not a permissions problem. Restore the version if it was a mistake. |
| "Name must be 255 characters or fewer" | Shorten the title. The detail goes in the description. |
| "Start date must not exceed target date" | The dates are the wrong way round. |
| "Only the comment author can edit" | Comments can be edited by the person who wrote them. Admins can delete, not rewrite. |
| "Locked views cannot be updated" | The view's definition is frozen. Duplicate it and change the copy. |
| Activity stops about a month back | The workspace is on Free, which serves a 30-day window. The older entries return on upgrade. |
Related
- Custom fields and templates: adding the fields your process needs.
- Approvals and SLAs: a required approver, and response targets.
- Sprints and Modules: grouping tasks into a plan.
- Tasks that follow their pull request: what happens when an agent picks one up.