unfuddled

why, what & how
Who am I

•   Hans Van de Velde
•   Technical project manager @ Amphion.be
•   www.novio.be/blog
•   hans at novio dot be
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, …
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
How does it work?
•   Create a project
•   Add people to a project
•   Set permissions per person
•   Go create tickets / Post info / Commit code
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
Milestones
Set important dates into everybody’s mind
Such as…
deadlines for deliverables,
release dates,
launch dates,
etc.
Messages and notebooks
• Messages for team communication
  (with commenting)
• Notebooks are like a Wiki:
  – Create pages
  – Attach files
 (with version comments)
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
Extending Unfuddle
• RESTful API
  – Build your own
  – SVN post commit hooks
  – Widgets
  –…
More info
• http://unfuddle.com/about/tour/dashboard
• http://unfuddle.com/blog
• http://unfuddle.com/support

Or, ask me!
Questions & answers
Go ahead, make my day… (Callahan, H.)

Unfuddle Unfuddled

  • 1.
  • 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? Webapplication 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 useUnfuddle • 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 itwork? • Create a project • Add people to a project • Set permissions per person • Go create tickets / Post info / Commit code
  • 6.
    Ticketing • Set titleand 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 datesinto 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 perproject • 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
  • 10.
    Extending Unfuddle • RESTfulAPI – Build your own – SVN post commit hooks – Widgets –…
  • 11.
    More info • http://unfuddle.com/about/tour/dashboard •http://unfuddle.com/blog • http://unfuddle.com/support Or, ask me!
  • 12.
    Questions & answers Goahead, make my day… (Callahan, H.)