Unfuddle: We bring your projects to life. Unfuddle builds tools that each approach project management from a different perspective. No matter the team, no matter the project, Unfuddle helps you do your best stuff. https://unfuddle.com/ Tue, 16 May 2017 13:40:48 -1000 Unfuddle: Notice of Data Breach
David Croswell

What Happened

We’ve identified and addressed security incidents which occurred on or about March 27 and April 13, where an unauthorized third party was able to initiate access to Unfuddle’s servers and its server information, potentially affecting Unfuddle products such as Unfuddle STACK, Unfuddle TEN or AgilePad projects (collectively, “Unfuddle”). We wanted to inform you about everything we know, as soon as we assessed the incident. We believe that this incident was not widespread, and that the vast majority of Unfuddle accounts were not affected. We have also found no other evidence of other Unfuddle systems or products being affected by this incident.

What Information Was Involved

Upon further analysis of the incident, some evidence showed signs of compromise to Unfuddle products. This means any sensitive data used during business, such as account details and source code data could have been affected or compromised by this incident. Personal customer information, financial and credit card data were not identified as being affected by this incident; unless, customers separately stored key personal or financial information on their accounts, which Unfuddle would not be aware of.

What We Are Doing

In addition to internal monitoring, we have engaged our security team to assess the incident, build and improve Unfuddle’s current processes, architecture, and controls. The following is being conducted in response and resolution to the incident:

  • We have completely replaced and updated all Unfuddle credentials related to Unfuddle infrastructure.
  • We have audited and strengthened access controls to keep potential unauthorized users off the system.
  • We have replaced Unfuddle’s SSL certificates to ensure communications continue to be encrypted and maintain the integrity of SSL.
  • We have enhanced monitoring and alerting to identify unauthorized access to our systems and machines.
  • We are designing and implementing a new network model with enhanced security zones and network segmentation.
  • We are improving our host-based Intrusion Detection System (IDS) software on all systems.

What You Can Do

  • As a precaution, Unfuddle STACK users should login to the platform and change their passwords immediately. You will be prompted to do so automatically the next time you log in. This step is not necessary for Unfuddle TEN or AgilePad customers.
  • Never store or share personal data on your Unfuddle accounts.
  • Make sure you are not storing third party credentials in your source code or attachments. While we generally believe customer repository data to be untouched, customers should change any credentials they may have stored in those repositories.
  • Any sensitive data or credentials stored in tickets or attachments should be changed.

Other Important Information

This is an ongoing investigation and Unfuddle will actively be working with law enforcement authorities on the investigation of this matter. Unfuddle’s Security Team will be increasing security monitoring, alerting, audit trails, and incident responses. We are also actively monitoring customer accounts to ensure that no further information was affected. We have already isolated the affected systems and confirmed that any further unauthorized access is not possible. To reiterate, we have found no evidence of other Unfuddle systems or products being affected beyond those mentioned in this notice.

For More Information

For more information, please go to https://unfuddle.com/blog/2017/05/important-notice/, contact us at support@unfuddle.com, or call us at +1-877-863-8335.

© 2017 Unfuddle LLC. All rights reserved.
Tue, 02 May 2017 00:00:01 -0000 https://unfuddle.com/blog/2017/05/important-notice/ https://unfuddle.com/blog/2017/05/important-notice/
A Simple Code Review Workflow in Unfuddle
Joshua W. Frappier

You should include code review in your development workflow

It can be intimidating to get started with git merge requests and code review and integrating them into your existing workflows. But as your projects and your team grow, having these built into your processes can significantly aid your development. Here are a few benefits you will see:

  • Code review facilitates knowledge sharing across your team.
  • Code review helps you maintain a more unified and consistent code base.
  • Code review helps you make better estimates.
  • Code review prevents technical debt from creeping into your projects.
  • Code review allows you to take more vacations.
  • Code review will save your team a lot of time in the long-run.

While it may sound complicated, Unfuddle makes it very easy to get started with code review in your team. Here's how it works.

Using Branches in Git

You probably track bugs, issues, and upcoming features for your products in your tasks. That's great! But are you using branches in your git repository to maintain a healthy workflow? Many teams make code changes right in the master branch of their repositories. They then close the task and move on. This can cause many problems and make it more difficult to undo changes to the code.

The taskboard

Rather than working only in master, code review depends on branching. Before working on any new task, a developer should first create a branch and make all relevant modifications in that branch. When the work is complete, then the developer should create a merge request on the task in Unfuddle.

Merge Requests

Merge requests give your team the opportunity to review and comment on the work BEFORE it gets merged into the master branch.

For example, if we are working to resolve a bug in our product, such as the one below:

A task representing a bug

We would first create a branch called "12-bat-gloves-bug" and make the necessary changes in that branch. When finished, we push our branch up to the repository in Unfuddle. Then we create a merge request from the task in Unfuddle, specifying the branch where we did our work.

Creating a merge request

Now the task has some new tabs that show the files and changes included in the merge request. Our team members can now easily see that this task has an open merge request waiting for review.

An open merge request

Now, it's time for the team to help out. Team members have the opportunity review each change and make comments right inline in the code. These are some of the types of issues a code reviewer might look for:

  • Does the code look correct?
  • Does the code conform to the project's style guidelines?
  • Are there any obvious logical errors?
  • Does the code meet the requirements of the original specification?
  • Were any necessary tests written and were they sufficient?
  • Do we need to update any other areas of the code to conform to these changes?

The team can comment on any of the lines in the changed files. These comments will appear inline with the code, but they will also appear on the task activity tab.

Code review comments

Making Modifications

Code review discussions will often lead to modifications to the code. Any necessary updates should be made in the same branch in which the original work was done. Once the new changes are pushed up to the Unfuddle repository, they will automatically be included in the merge request. Conversation can continue until the team reaches consensus on the code and it is ready to merge.


So we've finished our code review and have decided that the code is good! Alright! Now, we need to merge the code into master. We can do this using our git client, as normal. Or we can perform the merge right within the Unfuddle task:

Finally, once the merge is complete, we can delete the branch where we did our work.

And that's it. You just rocked code review!

© 2017 Unfuddle LLC. All rights reserved.
Thu, 06 Apr 2017 00:00:00 -0000 https://unfuddle.com/blog/2017/04/code-review/ https://unfuddle.com/blog/2017/04/code-review/
Unfuddle: Task Todos and Activity
David Croswell

This week, we launched a helpful new feature on tasks. You can now add a list of todos. This is great for remembering how much of a task you have completed. It’s also great for bigger tasks that you don’t want to break into into multiple separate tasks.

Tasks can now have todo lists

Click the add todo button on the upper-right hand corner of the task to get started. And don’t forget that you can reorder todos by just dragging and dropping them in the list.

We have also integrated task activity, such as tag and milestone changes, directly inline with the comments on a task. This gives you a great way to view how a task has evolved over time.

Activity for tasks is now shown inline with comments

Of course, we’ve also shipped a number of performance improvements and bug fixes. You might especially note that the Activity page is now significantly faster than before.

Keep those comments and requests coming!

© 2017 Unfuddle LLC. All rights reserved.
Thu, 23 Mar 2017 00:00:01 -0000 https://unfuddle.com/blog/2017/03/task-todos-and-activity/ https://unfuddle.com/blog/2017/03/task-todos-and-activity/
Unfuddle TEN: Multiple Repositories
David Croswell

Many software projects often rely on multiple repositories. Sometimes a project simply has multiple, significant components which make sense to keep separate. Sometimes it is just useful to fork the codebase to support significant variations of a product. No matter the reason, this is now possible in Unfuddle. All projects in Organizations can contain an number of Git repositories.

Adding tasks to specific taskboard columns

Each repository has a name and optional description to help you keep track of your code. You can drill down into each repo in the interface just as you would expect. The same commit history, merge requests, and code review abilities are all there.

We’ve got some more updates coming later this week, and plenty more in the pipeline. What’s the one thing you would want to see in Unfuddle TEN that’s not there yet? Let us know!

© 2017 Unfuddle LLC. All rights reserved.
Thu, 16 Mar 2017 00:00:01 -0000 https://unfuddle.com/blog/2017/03/multiple-repositories/ https://unfuddle.com/blog/2017/03/multiple-repositories/
Unfuddle TEN: Taskboard Update
David Croswell

You can now add tasks directly to any taskboard column. Regardless of the way your taskboard might be arranged, adding a task to a column will automatically give the task the appropriate tags or associate it with the column’s milestone.

Check it out:

Adding tasks to specific taskboard columns

It doesn’t get much easier that that – if your taskboard is arranged by @alias, adding a task to a column will automatically add that alias to the task. If your tasks are arranged by milestone then a new task added to the column will be associated with the milestone.

Please continue to give us your feedback. We love hearing from you and enabling you to be more productive in your projects!

© 2017 Unfuddle LLC. All rights reserved.
Thu, 09 Mar 2017 00:00:01 -0000 https://unfuddle.com/blog/2017/03/taskboard-update/ https://unfuddle.com/blog/2017/03/taskboard-update/
Unfuddle TEN New Features: Improved Task Card Features
David Croswell

Continuing with our recent usability updates, we’ve just rolled out a significant overhaul to how our task cards look and function. Say hello to the new look:

The New Task Cards

We’ve reduced the number of clicks necessary to find what you are looking for. There is more information on each task card, and they’re easier to read.

Specific types of info now appear in predictable places making a board full of tasks so much easier to parse. Status always appears in the top right and Milestone in the bottom left. Avatars for all people on the task now appear in the bottom right and replace the “@person” tags that would appear all over the place before. Finally, task cards now show information for comments, attachments, merge requests, and dates all in a consistent space.

Include Images On Task Cards

You can assign an images to cards now! Want to get your teams attention or visually represent what a task is for? Attach an image to the task and set it to show on the card. Boom! Your screenshot of that gnarly bug or sweet game asset will now be visible right on the card and easy to pick out at a glance.

Task Cards Can Now Have Images

Associate Tasks With Each Other

Sometimes you might want to refer to a task or to point out a duplicate. Or perhaps you want to define loose task dependencies to help you and your team know which tasks affect other tasks. Well, that’s now made easier as you can now create links between tasks. Do this by tagging a task with the number of any other task. These special hashtags automatically turn into links. Hover over one of these tags and you will see the card for the linked task. Tap on the card and you will immediately be taken to that task.

Task Cards Can Now Have Images

There is still a lot more coming! Continue letting us know how we can better serve you and your teams. We love making Unfuddle work better for you!

© 2017 Unfuddle LLC. All rights reserved.
Thu, 02 Feb 2017 00:14:00 -0000 https://unfuddle.com/blog/2017/02/unfuddle-ten-task-card-updates/ https://unfuddle.com/blog/2017/02/unfuddle-ten-task-card-updates/
Unfuddle TEN New Features: Backlog and Milestones
Danny Han

Today, you’ve got some new things for you. It’s a significant update that is part of a larger rollout of UI enhancements we have scheduled for this month. This is only the tip of the iceberg and you’re gonna love what’s in store down the road.

Update #1: All your projects now have a dedicated backlog. It’s accessible on the left side of all task views. By default, all new tasks you create will go into the backlog. The backlog even gets its own filter so that you can hone in on specific backlog tasks. It works the same was as the task filter you’re already familiar with in Unfuddle TEN.

The Backlog Panel

Update #2: Checkpoints are now Milestones. This may not sound like a big change, but along with the name, some significant functionality has also been added. Instead of a “checkpoint” which was simply inserted into the ordering of tasks and only implicitly associated with its tasks, each task can now be explicitly associated with a milestone.

Using Milestones to Help Manage Your Project

To create a milestone, click the “All Milestones” button to the left of the filter box. When the menu appears, click “Manage Milestones” to create a milestone and give it a name. You can also specify a date for the milestone but you can always make that decision (or change it) later. You can now associate new tasks to a milestone instead of going straight to the backlog.

Filtering By All Milestones

Viewing Tasks Belonging to a Milestone

In addition to the task filter, you can choose to view only tasks in a specific milestone or all milestones. To do this, select the desired milestone from the milestones menu on the left side of the filter. You’ll notice that “All Milestones” is the default selection. This means all tasks across all milestones are visible. To narrow the view to focus solely on tasks belonging to a specific milestone, select that milestone from the menu.

Extra Notes about Milestones

Selecting “All Milestones” shows each task with its associated milestone on the bottom right. If the task doesn’t show a milestone, you can assume it belongs to the backlog. You can drag tasks from one milestone to another in the Taskboard view. This includes dragging tasks from the backlog into any other column.

Milestones In Taskboards

Your project backlog and pending milestones await, so what are you waiting for? Have at it! And if you haven’t yet experienced it for yourself, go ahead and sign up for a free Unfuddle TEN account now.

Like the recent release of merge requests, these enhancements are just a taste of what else is in store. Stay tuned because we’ve got a lot more to talk about!

© 2017 Unfuddle LLC. All rights reserved.
Wed, 11 Jan 2017 00:00:30 -0000 https://unfuddle.com/blog/2017/01/unfuddle-ten-backlog-and-milestones/ https://unfuddle.com/blog/2017/01/unfuddle-ten-backlog-and-milestones/
Git Merge Requests in Unfuddle TEN
Danny Han

A little Christmas present for all of you in an Organization, because who doesn’t like presents? Unfuddle TEN now supports merge requests to enhance your code workflow.

Others have done a good job of touting the benefits of merge requests, so we won’t go into that here. We've provided some resources at the end of this article if you're interested. Instead, we'll just dive right into how merge requests work in Unfuddle TEN.

You'll probably initiate a merge request through a task in most cases, but you can also do it from the Code tab if you wanted to. We’ll stick to the most common way it'll be done by clicking a task and looking for the “add a merge request” button at the top right.

Let's say that someone created a task about fixing an issue in a plasma reactor and you have the fix for it. No problem!

Merge Request

Just click the “add a merge request” button then fill out the details. When you’re done, click the Continue button. Immediately you’ll notice some new things about the task that clearly differentiates it from regular tasks.

Merge Request Task

Notice the tabs along the top of the task?

Activity — The Activity tab now contains your normal task comments and attachments.

Merge Request — This tab offers a condensed overview of the merge request: the branches involved, the number of commits and changes associated with the merge request, along with other important information. The main thing is that this is where you can either cancel or accept the merge request.

Commits — This tab lists all the commits from the source branch that will be merged into the target branch.

Changes — This tab shows a more detailed view of all the file changes that will be applied during the merge.

We’ve also added a new tag type to make it easier to find tasks with merge requests. When viewing the task in either the list view or taskboard view, you’ll notice purple bang tags that are specific to a merge request. These tags appear automatically depending on whether the merge request is currently pending review or if the merge request was accepted. Any merge request that’s pending approval will show the “!open” tag. Any merge request that’s been approved shows a “!merged” tag.

Merge Request Tags

Hint: You can filter tasks using the bang symbol to find all merge requests (open or merged) in your project.

So there you have it — merge requests done in the style of Unfuddle TEN. We hope you’ll make good use of them!

We’ve got some new usability related changes that we’re cookin' up. They should really make the task interface a lot cleaner. We’ll have more to announce soon. And if you haven’t tried Unfuddle TEN yet, you can sign up for an account right now. Remember, you were born to make stuff, so get to it.

Enjoy and let us know what you think!

PS. As promised, here are some helpful articles to help you get the most out of merge requests.

© 2017 Unfuddle LLC. All rights reserved.
Tue, 20 Dec 2016 00:00:30 -0000 https://unfuddle.com/blog/2016/12/unfuddle-ten-merge-requests/ https://unfuddle.com/blog/2016/12/unfuddle-ten-merge-requests/
You Were Born to Make Stuff
Joshua W. Frappier


This week, the Unfuddle team has gathered from around the globe, in beautiful Vermont autumn, to launch the most significant product of our history as a company: Unfuddle TEN.

Unfuddle TEN is the most straightforward and adaptable platform we have ever encountered. Not all projects and teams are the same. Unfuddle TEN adapts to your needs on a per project basis. If all you need is a repository and a simple task list for a personal project, no problem. If you need taskboards, complex reporting, advanced workflows, merge requests and the like, no problem. Your team will have everything it needs. Unfuddle TEN gives you just what you need and then gets out of your way in a hurry.

Here is a quick video of some of the highlights of the app:

  • First-class Git hosting
  • Kick-ass task & issue management
  • Unlimited personal projects
  • Reporting and filtering to get you exactly the info you need
  • and more...

I hope that you give Unfuddle TEN a try. We have been using it exclusively for months internally and think that it is worlds better than anything we have ever used or built before.

You can read more and sign up for an Unfuddle TEN account here on the homepage.

And we are not done. We've been at it since February and we have a LOT of amazing features still in the development queue. But we wanted to get this out to you sooner rather than later.

Enjoy! And be sure to let us know what you think!

© 2017 Unfuddle LLC. All rights reserved.
Tue, 01 Nov 2016 00:00:00 -0000 https://unfuddle.com/blog/2016/11/you-were-born-to-make-stuff/ https://unfuddle.com/blog/2016/11/you-were-born-to-make-stuff/
Sneak Peek at Unfuddle TEN
Joshua W. Frappier

Hey there!

I know, I know. We have been pretty silent lately about Unfuddle TEN. So many of you have been asking us for some updates, but we have been quietly working away.

As you may recall, TODAY is the 10 year anniversary of Unfuddle! Woohoo! So to celebrate, and to break the silence, we want to share with you some of the highlights of the work we have been doing with Unfuddle TEN.

Sign In

Nice! Even the sign in page looks sexy. And, Unfuddle TEN now supports a single login for ALL of your organizations. No more managing multiple accounts!


The project page in U10 shows all of your projects across all organizations. We have brought some new levels of customizability, including project icons and backgrounds.


Here you can see that we have really embraced the use of open tagging for unprecedented flexibility on tasks. U10 supports tags for status, people, dates, general hashtags, and numbers (like time and cost). This move to open tagging is the most significant and power-filled decision we have made. And the filter box makes it crazy simple to get to exactly the tasks you want.


Viewing tasks as a taskboard is as simple as clicking over to the board view. Pivot the view of your tasks based on status, person, or hashtag. Drag and drop to change values or sort order.


For date oriented projects and teams, Unfuddle TEN is showing up with some amazing features. Any tasks that are tagged with dates will appear in the project calendar. You can easily drag and drop your tasks to modify dates and keep everything on track.


Notifications of project activity are received in-app as well as via email notifications. You can view global project activity or even just filter down to only those events that are specifically relevant to you.

Activity Tasks

Viewing and editing a task is no longer an action that takes you away from your current context. In this case, you can click directly on a task in the activity list to see and make changes.


On the People tab, we can see everyone involved in our project. One really cool feature here is that participants can be given any number of @mentions to which they might respond. For instance, in this case, John Brewster can be referenced anywhere in the project by @john, @dev or @everyone. This allows us to very easily create adhoc groups of people, like @dev or @marketing.

Obviously we're just teasing you here. There is so much more to show and to talk about. But we really wanted to hear from you about what you think. We are very excited about where this is heading. We are using Unfuddle TEN internally and I cannot tell you how much easier it is to use, in almost every way, than STACK.

So, what do you think about some of the new ideas we are bringing to Unfuddle? Let us know by tweeting @unfuddle with the hashtag #UnfuddleTEN or leaving a comment below.

© 2017 Unfuddle LLC. All rights reserved.
Fri, 24 Jun 2016 00:00:00 -0000 https://unfuddle.com/blog/2016/06/sneak-peek-at-unfuddle-ten/ https://unfuddle.com/blog/2016/06/sneak-peek-at-unfuddle-ten/
10 Must-Have Apps You Should Have in Your Agile Toolchain
Danny Han

header image -- must-have agile apps

At Unfuddle we are a distributed team of several software engineers. As a distributed team, we have some common tools we all share, as well as our own personal list of go-to apps. These tools help us in our continuous delivery of features, fixes, and new products.

Here are the recommended tools we use everyday, and some quick thoughts on why we like them so much. Please comment or share your favorites – we’re always on the lookout for recommendations.

  1. Unfuddle

    Unfuddle keeps our team organized through task assignments attached to our Git repository. Taskboards showing tickets keep us on the same page so that we’re aware of the state of our code at all times. Its simplicity keeps our energies focused on building great software.

  2. AgilePad

    Like you, we often conceptualize and brainstorm lots of new ideas. These ideas are never in short supply, but we find that keeping them organized as projects becomes a problem. The solution? AgilePad. It serves as a centralized project management notepad that turns those new ideas into actionable tasks.

  3. Atom

    We love TextMate and Sublime. But Atom is winning some of us over because of its extensibility and customisability. It has a ton of nice little features that streamline our development just a bit more.

  4. SourceTree

    Fetch, Pull, Push, Reset, Revert, Log, Branch, Merge – Git commands and command arguments that we’re just not inclined to commit to memory any longer (pun very intended). Some of us still use Terminal, but visualization of diffs will spoil you.

    A recent discovery has been GitKraken, which looks to be a worthy alternative.

  5. Docker

    Docker gives us an environment to design and test production environments on virtual machines. By employing layers, we can extend virtual machines with ease with full ssh and debug capabilities. Virtual layers also save us storage space by using base storage without the need to duplicate it. The true benefit of Docker is that we are able to encapsulate apps in their own environment, which in turn makes deliverables a lot less painful.

  6. ClipMenu (http://www.clipmenu.com)

    To use an old cliché: You never know how much you miss something until it’s no longer there. ClipMenu is the very definition of this. We rely on ClipMenu so much because limiting yourself to just one thing in clipboard memory at any given time is just crazy talk.

  7. VirtualBox

    We’re an OSX development house, and VirtualBox is our open-source solution for testing our apps on Windows/IE.

  8. Chrome

    One does not simply do web development without Chrome DevTools One does not simply do web development without good browser. Enter Chrome with its web inspector/console. It’s second to none and really is the one browser to rule them all. Okay, we promise, no more references to The Lord of the Rings.

  9. Skype

    Sometimes your distributed team needs to talk with each other right now. Skype facilitates the face to face conversations that are inevitable. It’s our de facto video conferencing app and its companion mobile app keeps us all connected.

  10. Spotify

    There’s little need to dive into the virtues of listening to music. Science pretty much has that covered (Read the best music to listen to for optimal productivity, according to science.). What we like about Spotify is that it rarely fails us when it comes to listening recommendations. And $10 a month is a no-brainer when it comes to improving your work, mood, and general well-being while coding.

What tools, apps, or sites are we missing that should be a part of one’s development toolchain?

Let us know in the comments below, or tweet @unfuddle with the hashtag #UnfuddleIdeas.

© 2017 Unfuddle LLC. All rights reserved.
Thu, 14 Apr 2016 00:00:00 -0000 https://unfuddle.com/blog/2016/04/10-must-have-agile-toolchain-apps/ https://unfuddle.com/blog/2016/04/10-must-have-agile-toolchain-apps/
Security Update to Git 2.7.4 and OpenSSH 7.2.p2

We have updated some components of STACK to ensure better security compliance.

  • Updated Git version 2.7.4. Per the release notes: Bugfix patches were backported from the ‘master’ front to plug heap corruption holes, to catch integer overflow in the computation of pathname lengths, and to get rid of the name_path API. Both of these would have resulted in writing over an under-allocated buffer when formulating pathnames while tree traversal. (source: https://raw.githubusercontent.com/git/git/master/Documentation/RelNotes/2.7.4.txt)

  • Updated OpenSSH library version 7.2.p2 due to several security risks that appeared since 2016. OpenSSH version 7 and onwards disabled DSA keys authentication by default. At this point we allow DSA keys to authenticate but in the near future we will disable them due to the standard for new keys being RSA. More information about this update https://www.openssh.com/security.html

Please let us know how we’re doing by adding a comment, emailing us at support, or by tweeting us @unfuddle. As always, we continue to improve Unfuddle STACK so that you can get your best stuff done.

The Unfuddle Team
We bring your projects to LIFE!

© 2017 Unfuddle LLC. All rights reserved.
Tue, 22 Mar 2016 00:00:30 -0000 https://unfuddle.com/blog/2016/03/security-update-git-openssh/ https://unfuddle.com/blog/2016/03/security-update-git-openssh/
Unfuddle TEN: Addressing Customer Feedback
Joshua W. Frappier

Addressing Customer Feedback

Unfuddle TEN development has been going great. And we are getting closer to releasing a roadmap for everyone to see.

Before we pull back the covers completely on Unfuddle TEN, I want to take the opportunity to address some of the specific concerns that our customers have brought to us — recently and through the years. You have showed up in droves to talk to us about what you really want out of Unfuddle.

Here are just a few of the ways that Unfuddle TEN is going to help you and your team do your best stuff:

Cost. You want free. And we have heard you. Unfuddle TEN is going to be free for personal accounts. Of course, we are going to save some of the fun for our paid accounts, but I think you will be very pleased to find that you can do most personal projects in Unfuddle TEN without paying a dime.

Pull Requests. Let’s be honest. Unfuddle has lagged behind the modern day git workflows that most of us use today. Branching, merging, code review — Unfuddle TEN is going to support these out of the box.

Agile Workflows. We have spent a lot of time designing our new task workflow system. Rather than the rigid workflow we have in Unfuddle today, Unfuddle TEN sports an extremely flexible system that will match the way your team works. Agile teams, scrum teams, kanban… you name it. Unfuddle TEN works the way you do.

Native Mobile Apps. We have heard you loud and clear that mobile matters. We will be releasing native iOS and Android versions of Unfuddle TEN.

Integrations. Github, Slack, HipChat, Basecamp, Harvest, Freckle. Over the next year, we are going for gold on integrations. Unfuddle TEN is going to work where you work with the most popular tools that accompany you through the rest of your day.

Obviously, these are just a couple of examples of how we are directly meeting your requests. Unfuddle TEN is a whole lot more!

I want to thank everyone again for your feedback. It has been this feedback that has shaped Unfuddle TEN and we know you are going to love it. Keep it coming!

In the next few weeks, we are going to be releasing our official roadmap for Unfuddle TEN. Keep a watch out. And let us know what you think!

© 2017 Unfuddle LLC. All rights reserved.
Tue, 15 Mar 2016 00:00:00 -0000 https://unfuddle.com/blog/2016/03/addressing-customer-feedback/ https://unfuddle.com/blog/2016/03/addressing-customer-feedback/
Why we chose Meteor for Unfuddle TEN
Joshua W. Frappier

Why we Chose Meteor for Unfuddle TEN

As many of you know, Unfuddle has been a primarily Ruby shop for the past ten years. We love Ruby. And it has served us exceptionally well.

However, in the past year, we have really gotten interested in the idea of realtime collaborative interfaces. AgilePad was our first attempt at this (you can read more about that in our previous blog post). Though we were very attached to Ruby, we began to venture out of the ecosystem to test the state-of-the-art in other development communities. For example AgilePad was built on NodeJS, Angular and Firebase.

For a few of our other side projects, we chose to use Meteor. And we have fallen in love. Here are just a few of the reasons why:

  • It is full stack, from the database all the way up to the UI. In the past, we always had to glue together different layers of the stack (Angular for UI, Firebase for data storage and operational transformation, NodeJS for the web server). Meteor makes all of this integration work moot. And it has single ORM for both client and server. So much easier than writing all that glue code!

  • We can use Javascript everywhere; on the client and on the server. This really streamlines our development. And in our case, we have chosen to use CoffeeScript for all of our Javascript. Debates aside, this gives us just a little of the Ruby cleanliness that we all loved so much.

  • It’s reactive. As developers, we only need to worry about maintaining the state of our components. The interface then just automagically does the rest.

  • Meteor is realtime. LiveQuery and DDP are core features of Meteor and they really do a fantastic job of making realtime feasible. If any user updates data, the changes are automatically propagated to every connected client and the necessary interface elements are rerendered. Features like chat, live notifications and live collaboration are now a breeze.

Meteor now supports a few different view renderers. We have used Blaze and Angular in the past with mixed results. But now that Meteor is officially supporting React, we are jumping on the bandwagon. Here’s why:

  • React components provide a high level of reusability. Leveraging composition greatly simplifies our codebase.

  • It has excellent performance due to its use of the virtual DOM.

  • There are a lot of great developer tools out there that make debugging the view much easier. These tools also make it much easier to spot performance bottlenecks.

We are so excited about how Unfuddle TEN is shaping up. And Meteor is a big part of why it’s getting so good.

Are you using Meteor in your projects? If so, let us know some of your experiences. You can comment in this blog, or tweet us at @unfuddle with the hashtag #UnfuddleIdeas.

© 2017 Unfuddle LLC. All rights reserved.
Tue, 01 Mar 2016 00:00:00 -0000 https://unfuddle.com/blog/2016/03/why-we-chose-meteor-for-unfuddle-ten/ https://unfuddle.com/blog/2016/03/why-we-chose-meteor-for-unfuddle-ten/
Project Management at the Speed of Thought
Joshua W. Frappier

Project Management at the Speed of Thought

Over the years we have engaged in many “thought experiments”. These are experiments to test principles of project management, and their practical application. We came up with these experiments through talking with our customers, and drawing on our own experiences with running dozens of internal projects over the years.

You may not have heard of AgilePad, but it was one of our experiments that we launched last year. We launched it with little fanfare. AgilePad came from a single observation we had about our team: Despite so many good project management tools, everyone at Unfuddle still kept a bunch of text files on their desktops with random thoughts and todos for various projects. We asked ourselves, “What if we moved those text files to a collaborative environment, and spiced it up with a little syntactic sugar?”

The result was nothing short of amazing. After what is honestly a very steep learning curve, the fluidity with which we were able to manage our projects was impressive. In fact, going back to other tools, including Unfuddle STACK, almost feels impossible once we got spoiled with realtime, free-form, project collaboration at the speed of thought. The truth of the matter is that we actually use AgilePad every single day. Unfuddle TEN, even now, lives as an AgilePad project document. (If you want to experience AgilePad, go here)

But AgilePad can be a bit obtuse. Obviously, not everyone thinks in plain text. We know that. But the experiment is still tremendously valuable for us as designers. It has taught us how to better understand fluidity of action. Most specifically, it has taught us how to REMOVE interface to get to a better experience. Do we really need to have formal data models and customized interface elements for everything we THINK our customers want to achieve? Or is our responsibility to build the most general tool possible and get out of the way?

We think it’s the latter, and AgilePad is the experiment that has revealed the answer to that question.

The French writer and poet Antoine de Saint Exupéry, said it best, “…perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.”

It may be overly quoted, but it doesn’t make it less true. AgilePad taught us this for ourselves. And we are aggressively applying this principle in Unfuddle TEN. Not so that we can build less, but so that YOU can accomplish more.

We still want to hear from you. What do you want to do less of in your current project management tools? Tell us by commenting below, or tweeting us at @Unfuddle.

Project Management at the Speed of Thought
Tweet This

We are really committed to a high level of transparency as we move closer to the launch of Unfuddle TEN. Stay tuned for more on how Unfuddle TEN is going to get out of your way and help your team do its best stuff.

© 2017 Unfuddle LLC. All rights reserved.
Tue, 23 Feb 2016 00:00:00 -0000 https://unfuddle.com/blog/2016/02/project-management-at-the-speed-of-thought/ https://unfuddle.com/blog/2016/02/project-management-at-the-speed-of-thought/
Ten Years and Counting
Danny Han

Ten Years and Counting

In 2006, we launched Unfuddle. Things were a little different back then.

Git was in its infancy.
The mention of the word “scrum” evoked images of a sport.
And no one ever said the words “pull request.”

But Unfuddle helped software developers to manage their code and focus their teams. It resonated with project managers, too.

Unfuddle had a certain style to it. It was approachable, intuitive — perhaps even obvious. Project managers loved the reporting tools. Developers loved the clean interface. And we took away the complexities of code hosting so that teams could focus on building stuff — their best stuff.

Unfuddle’s approach has always been incredibly easy to understand. Even today, when teams join Unfuddle, they get it. They still do.

But today, development teams are more complicated. Git, agile, lean, kanban and others have inserted themselves into our workflows.

The future of project management demands tools that simplify and sustain teams — not bog them down. We are not talking about simplistic tools. We are talking about simplified ones.

  • Tools that do away with the encumberance of “stuff” that only serves to get in the way.

  • Tools that get right to the heart of the matter: to help teams be on the same page in an environment of shifting priorities.

  • Tools that get out of the way, and fade into the background like they should so that teams can concentrate on doing awesome work.

What’s in a number?

June 24th, 2016 marks the 10th anniversary of Unfuddle. That’s 10 years of helping teams succeed. Tens of thousands of teams. Tens of thousands of software projects. Ten years of experiencing the pains of software development alongside you — our customers.

It’s all led to a new product that we will be unveiling soon. Its codename is Unfuddle TEN.

We have always been about the straightforward, easy, and simple. It’s our hallmark with Unfuddle. That will never change. And our new product carries on in that 10 year tradition.

If you love software that is obscenely obvious to everyone on your team, you are going to love Unfuddle TEN. We are sure of this.

But we are still working. And we want to know what you need most today. What do you struggle with at work as a project manager of a software team? As a software developer? How can Unfuddle help with your work, your team, your projects?

Let us know by tweeting @unfuddle with the hashtag #UnfuddleIdeas</a>
Tweet Us!

You can also leave a comment below.

Get back to basics.

We want to bring back the love, the fun, and the success of building software. We want to see teams do their best stuff.

Let’s bring back the feeling that fired you up to be a developer. When working together to solve problems through elegant solutions is what got you up in the morning. When friction on a team was the clashing of great ideas; not today’s clashing that comes over miscommunication, misplaced pride, or miserable expectations.

Are you with us? Then let us know!

© 2017 Unfuddle LLC. All rights reserved.
Mon, 15 Feb 2016 01:00:00 -0000 https://unfuddle.com/blog/2016/02/ten-years-and-counting/ https://unfuddle.com/blog/2016/02/ten-years-and-counting/
Just Deployed Five Improvements To STACK

Custom Resolutions

Just before the close of the year, we improved Unfuddle STACK with some new enhancements. Many of these improvements come from the STACK community, and we are grateful. Your feedback represents the way our customers are using STACK. It guides us in how we make improvements.

  • Added Custom resolutions for tickets are finally available. Now you can specify custom resolutions in your projects tailored for your workflow.
  • Added Archive ticket field function: versions, severities, components. Many of you have projects with thousands of versions, making the project settings page unmanageable. The ability to archive these projects solves the clutter problem.
  • Updated track2unfuddle.rb script, thanks to Iskar Enev. This update corrected the migration of ticket fields and added support for Trac 0.11.1 installations using a MySQL database backend.
  • Updated bi-daily email notifications: 8AM and 4PM. Now you can get an email digest of the latest changes twice a day.
  • Added Timedoctor integration. Timedoctor lets you track time on tasks in Unfuddle STACK and get detailed productivity metrics such as individual time spent on tasks, total time spent on tasks across the team, and more. Visit https://www.timedoctor.com/unfuddle.html for more information.

Please let us know how we're doing by adding a comment, emailing us at support, or by tweeting us @unfuddle. As always, we continue to improve Unfuddle STACK so that you can get your best stuff done.

The Unfuddle Team
We bring your projects to LIFE!

© 2017 Unfuddle LLC. All rights reserved.
Thu, 07 Jan 2016 00:00:30 -0000 https://unfuddle.com/blog/2016/01/five-improvements-to-stack/ https://unfuddle.com/blog/2016/01/five-improvements-to-stack/
Living out Loud. Or &ldquo;Why Teams Fail&rdquo;.
Joshua W. Frappier

Living Out Loud

At Unfuddle, I have had the privilege of serving countless software development teams, helping them build their best stuff. This has come primarily in the form of developing tools that help them to communicate. It has also come in the form of consulting directly with teams. These roles have put me in a position to see which teams do well and which teams fail.

Often, we get customers who are looking to Unfuddle as a tool to help solve their communication problems. I am proud to say that it can! But sometimes, teams fail even though they use good tools. Maybe you have the perfectly curated software development stack, the best developers, the end-all-be-all of project management methodologies. But something lacks.

Why is this?

Communication and transparency sound easy. But they're not. They're hard. They are learned. They are practiced. They don't come naturally.

And there is a reason why it doesn't come naturally — it's because of a human trait called pride. We all have it to a degree, but left unchecked, pride will hurt teams, and put projects in peril. But there's a way to diminish the effects of pride.


You are prideful. I know you are. I know because you're human. We are all prideful sometimes. Each of us seeks to maximize the way that others perceive us. We generally want to be seen as knowledgeable, skilled, and ultimately valuable. Putting our pride aside generally places this at risk.

We see this play out in teams all the time. For example, not asking the question at a meeting for fear of looking stupid. Or not inviting discussion for fear of hearing dissenting viewpoints. How much more efficient would our teams be if we simply put aside our pride, and asked out loud?

Remind yourself to “ask out loud”. Put your pride on the line. Maybe you're wrong. Maybe someone else has an answer — a better answer.


Your pride makes you judgmental. I know you are. I know because you're human. We are all judgmental. Sometimes it's motivated out of fear to protect what's ours. Other times it's motivated by our biases. No matter the reason, judging someone makes you difficult to approach.

I have seen the judgmental attitude from teams. Someone judges him for what is perceived is his lack of knowledge in an area that should be his expertise. She is judged because she can't seemingly understand something so simple. You are judged because you can't articulate an idea quite so well.

Do you see what's happening here? A judgmental attitude is a systemic problem behind failed teams that stems from pride. And pride feeds the very reason why people don't ask out loud: The fear of damaging their pride.

Start answering out loud in good faith. Answering out loud does not mean making a public spectacle. It means providing the answer for the benefit of the person asking, and for the knowledge it imparts to others. Answering out loud in this way gives permission to ask out loud, and breaks the cycle of pride that pervades many teams.


You need accountability. I know you do. I know because you're human, and we humans think we work better alone. It's not true. We work better as a team. That's why you're on one, right?

It's not enough to be on a team, though. That does not imply accountability. Accountability by its nature goes beyond an attitude of “just ask” or “I'll show you when I'm ready” because accountability is proactive and persistent. It grants permission to ask questions. It invites discussion. It covets feedback and opinion from team members. Not some of the time, or when it's convenient for the sake of your pride — but all the time.

Our tendency is to abstain from accountability among our peers. That human trait called pride says, “I don't answer to anyone.” Wrong. You answer to your team, and they answer to you. The way to do that is to work out loud.


There is a little line of scripture that says, “Pride goeth before destruction, and a haughty spirit before a fall.” In other words, people and teams fail because unchecked pride strokes the self serving ego. The way to keep it in check is to live out loud by adopting intentional, and honest transparency on your team. Sharing knowledge without judgment. Asking questions without fear.

My hope is that your team will succeed as it identifies and addresses pride head on through living out loud. You can start by raising up the culture of asking out loud, answering out loud, and working out loud today. It's not too late. Teams that teach, practice, and uphold these standards as part of their team culture will benefit from improved communication that leads to project success.

© 2017 Unfuddle LLC. All rights reserved.
Tue, 17 Feb 2015 01:00:00 -0000 https://unfuddle.com/blog/2015/02/living-out-loud-or-why-teams-fail/ https://unfuddle.com/blog/2015/02/living-out-loud-or-why-teams-fail/
Faster Performance for All Unfuddle Users

Happy New Year to you! Over the past few weeks, we've been busy implementing some new hardware and software upgrades. These upgrades include SSDs, more RAM, and faster CPUs. Here are the benefits to you as we finish up all upgrades:

  • GIT and SVN repository access will see a boost in performance by 58%. The SSDs have the biggest effect here, but CPU and RAM upgrades are also a factor contributing to this speed boost.
  • Automatic backups are clocking in at 38% faster through the SSD and CPU upgrades. Although backups are a background process, this improvement means your backups are more readily available to you.
  • API requests are seeing an improvement in speed by 30%. Here, RAM and CPU upgrades will influence these API requests the most. This means getting your best stuff done faster across the board.

Along with these hardware improvements, we have also updated to SVN 1.8.10 and Git 2.2.1.

We continue to improve the Unfuddle toolset so that you can get your best stuff done. And when we complete the hardware transition across all our servers, we will be sure to let you know.

Please feel free to leave us feedback. You can comment in this blog, contact Unfuddle support, or ping us through our social media channels. We’d love to hear from you!

The Unfuddle Team
We bring your projects to LIFE!

© 2017 Unfuddle LLC. All rights reserved.
Fri, 09 Jan 2015 01:00:30 -0000 https://unfuddle.com/blog/2015/01/faster-performance-for-all-unfuddle-users/ https://unfuddle.com/blog/2015/01/faster-performance-for-all-unfuddle-users/