DuckyDive
Project tracking that keeps up.
A serious tracker, already on your desktop beside your chat, documents and calendar. It works for one person in a personal organization too.
One set of tasks, four ways to look at it
Board, List, Timeline and Calendar all read the same tasks and honor the same filters, so a view you save works in every one of them.
- Saved views with their own filters and sort, private or shared with the project.
- Filter on built-in and custom fields, and match all conditions or any.
- The same filters drive automation conditions and dashboard widgets.
Shaped like your process
Name your own statuses, QA or Code review or whatever you actually call them. Each one maps to a category, so progress and reports keep working however far you customize.
- Custom workflows per project.
- Eight kinds of custom field: text, number, date, select, multi-select, person, checkbox and URL.
- Epics, stories, tasks, bugs and subtasks.
- Labels, sections and task dependencies.
- Project templates, built in or saved from your own projects.
Rules that do the chasing
When something happens, if the conditions hold, do these things. And when a rule changes a task, the history says the rule did it.
- 14 triggers: changes to status, priority, assignee, section, fields, labels and comments, tasks created, blocked or unblocked, and on the clock, due soon, overdue, blocked too long or gone stale.
- 15 actions: set a status, assign, prioritize, move, label, set a due date, comment, notify, add a watcher, create a subtask, archive and more.
- Up to 10 actions on a rule.
- A log of 90 days of runs, so “why did this change?” has an answer.
Planning above the task
Work comes in Dashes: a set stretch of time, often a week or two, with a goal and the tasks the team chose to finish in it. Above them sit releases, goals and portfolios, and beside them, what everyone actually has on their plate.
- Dashes with burndown and velocity charts.
- Releases and epics.
- Goals that take their progress from linked projects, sub-goals, a metric, or by hand.
- A goal going at risk or off track needs a note saying why.
- Portfolios, to look at a set of projects together.
- Workload against each person's capacity.
- Time tracking, with a running timer and a timesheet, set against your estimates.
- Dashboards built from bar, share, number, trend and table widgets.
Work from outside the project
Requests rarely arrive tidy. Forms and chat turn them into tasks, and a task that belongs to two projects can appear in both.
- Forms that map each answer to a field, public or for signed-in readers only.
- Turn on /duckydive in a DuckyFlock channel and a line of chat becomes a task.
- Recurring tasks that create themselves on a schedule.
- One task can appear in several projects, while keeping a single home.
Blocked means something here
A red flag with no explanation tells nobody anything. So blocking a task from the board, in bulk or by a rule takes a reason, and you can create the subtasks that will clear it in the same step. The time a task spends blocked is recorded.
What you can't open stays out of sight
Goals, portfolios and shared tasks never show the name of a project you can't open. You get a count instead.
Smart features, where they're switched on
Smart Project Creation turns a description, or a conversation's notes, into tasks for you to check before any are added.
Worth knowing: It depends on your plan and on what the site's administrators have set up. Everything above works without them.