Difference between activities and tasks
In Rabbiit, task and activity are not the same object with different names. Mixing the two leaves you with a bloated catalog of “work types” that only apply in one project — or a board full of generic cards that should have been an hour category.
A task is the account’s work type: Consulting, Development, Meeting. It repeats across several projects and is used in time entry so reports and billing make sense.
An activity is the work of this project: the card in the list or on the kanban, with assignee, due date, estimate, steps, file, and conversation. It is “what we are delivering”, not “the hour type”.
Task: the account’s work type
Tasks tab: the account work type
The task lives in the account catalog and is reused. You add the relevant ones on the project Tasks tab — the walkthrough is in how to add tasks to a project. When you log time, you choose the task to classify the entry.
Use a task when the name applies in more than one project and finance or reporting needs to group by type (“how many consulting hours this month”).
Do not use a task for a one-off deliverable (“send the proposal for client X”). That is an activity.
The walkthrough for building the catalog on the first project is in the getting-started tutorial. Whoever manages the account catalog needs permission to create and edit tasks.
Activity: the work of this project
Activities tab: the work of this project
The activity lives in Projects > Activities (list) or Kanban. Each card is a slice of that project’s scope: it has a name, an assignee, a due date, and — if the team agrees — an hour estimate. The card walkthrough is in how to create an activity.
This is where the work-management pieces come in:
- How to create an activity — title, path, stopwatch, assignment, description, comment, and history.
- Kanban board — the same activities in columns; drag the card when the stage changes.
- Subactivities — steps inside the card, without creating three parent activities.
- Estimate — planned hours on the parent and the children; the card total is the sum.
- Attachments and comments — file and agreement in the same place as the work.
- Activity permissions — what the member can see and do on that project, inherited from the account default.
Whoever only logs hours still enters time with project + task. The activity organizes the work; the task classifies the hour.
How to choose in practice
| Situation | What to create |
|---|---|
| “Development” repeats on every project | Catalog task |
| “Sign off on company X’s website by Friday” | Project activity |
| Layout, content, and sign-off of the same website | Subactivities of the same activity |
| Brief in PDF and “the client cut scope B” | Attachment and comment on the activity |
If the team creates a new task for every card, the catalog becomes junk and the report stops grouping. If the team only uses activities and never classifies the hour with a task, billing by work type disappears.
Where each one appears
- Project tasks: Projects > Tasks (and the task field on the time entry)
- Activities: Projects > Activities or Kanban
- Default of what the member can do on activities: account settings, activities section — and the fine-tuning in Edit project > Activities