2. Who am I
• Hans Van de Velde
• Technical project manager @ Amphion.be
• www.novio.be/blog
• hans at novio dot be
3. What is Unfuddle?
Web application with secured access (paid service)
• Bug tracking software
• Groupware
• Source Versioning repository
= easy alternative for Basecamp, Trac, JIRA, etc.
RESTful API, widgets, freebies, …
4. Reasons to use Unfuddle
• Clean & clear organization of bug reports
– Fights clutter (1000s of e-mail messages)
• Project team communication
– All notified at once
– Keeps track (history)
• Source versioning
– SVN, GIT
– Versioning & backups on demand
5. How does it work?
• Create a project
• Add people to a project
• Set permissions per person
• Go create tickets / Post info / Commit code
6. Ticketing
• Set title and describe scenario to reproduce the
problem. Be precise about browser + platform
and actions taken.
• Set priority & severity
• Assign to a specific person
• Set a due date (deadline)
• Typical flow: accept – resolve – verify and close
• Custom ticket reports (i.e. status report)
• Time effort entry per ticket
7. Milestones
Set important dates into everybody’s mind
Such as…
deadlines for deliverables,
release dates,
launch dates,
etc.
8. Messages and notebooks
• Messages for team communication
(with commenting)
• Notebooks are like a Wiki:
– Create pages
– Attach files
(with version comments)
9. Source repository per project
• Central repository = latest development version, with revision history
• Ideal when working with different remote development teams
• Powerful commit messages:
– “resolves”, “resolved”, “fix”, “fixes”, “fixed” changes status of specified tickets
to be resolved
– “closes”, “closed” changes status of specified tickets to be closed
– “assigns”, “assigned”, “reassign”, “reassigns”, “reassigned” reassigns tickets to
the specified username
Examples:
fixed #123, embedded Zombie font in SWF
resolves #123 and reassigns #123 to hvandevelde
references #123, #124 and closes #124
spent 5.5 hours on #498
resolved #47 spending 2:45 on #47
