The new DoneDone: What’s new

Happy Monday, folks.

If you’re reading this, you’re probably signed in to the new DoneDone and thinking “What the $#%! happened to my DoneDone”. Then you’re thinking “Oh, right, this is the newer, faster, cleaner DoneDone I got 13 emails about.” Finally, you’re looking for some kind of primer on what’s actually new besides the design and the new .ico in you’re browser tab . Well, here ya go. Put that cold cup of coffee in the microwave for a minute, sit back down, have a read. Then, go get fixin’.

Hey, first, here’s two reminders

Your old username doesn’t exist anymore.

The first time you (and your users) sign in to the new DoneDone,  use your email address instead of your old username. Because of changes to our authentication model, we couldn’t bring the old ones with. Once you’re in, you can click over to Profile to re-enter that old username if you’d like.

DoneDone is free for October. You quite literally can’t pay for it.

While you’re busy getting busy using the new DoneDone, we’ll be busy getting our new billing platform into place. For the entire month of October, every DoneDone account is unlimited everything. Around October 15th, we’ll be releasing  a final build of the accounts section of DoneDone, and from then on, you’ll be able to see which plan you’re in, upgrade, downgrade, cancel, and get a sense for how things work now with active users.

What’s new

The Dashboard

In the old DoneDone, you saw every project by default. Even the ones with no issues in ’em. We’ve created two new views on the Dashboard in v2. The default view is of projects with issues you’re participating in. The secondary view, for project managers, gives a birds-eye view of all active projects, regardless of ‘your participation’. You’ll also notice a Recent Activity feed at the bottom of the page. This looks at three most recently updated projects where you’ve got issues.

Email-to-ticket attachments

You can now email attachments to an issue, both on comment replies and adding issues via email.

CC people on an issue

In the new version, you can CC yourself or other people on an issue. This means you’ll get cc’d on all issue updates. This might be nice if you want to bring someone in for an opinion without having to reassign the issue. You can also bring others onto the conversation by cc’ing them on a comment, reassignment, etc. Oh, and in case you’re not interested in the issue, you can excuse yourself directly from the email.

Markdown support

All description fields in V2 support Markdown. This means you can make bullets out of asterisks, and bold and italicize as well. You can write HTML in there as well if ya’d like. If you’re new to Markdown, it’s easy. Here’s a primer.

Testers and Fixers

In V1, the person that created the issue was also the one that tested the issue. We got around this by doing a weird “create an issue on behalf of someone else” thing. V2 makes it more straightforward. When you create an issue, you pick both the fixer and the tester. So, Craig finds a browser bug on a project. He creates it for Bruno to fix and Lindsay to test. Simple.

Tagging that isn’t horrible

V1’s tagging auto-suggest was awful. We’ve made it better now. You can open up a list of tags on that project and click them to add it. Edit the issue to get rid of ’em. No javascript magic. Just simple UI which won’t leave the browser wheezing.

Custom issue searches

In V1, once you created a custom search, you couldn’t edit or delete them. Now you can. I call this a feature enhancement.

Bulk Edits

You can now edit a group of issues in bulk from a project’s landing page. Change priority levels, testers, fixers, statuses, or even move a set of issues to a different project.

Uploading attachments on any action

In V1, you could only attach files to a comment. If you wanted to reassign the issue or change the status while attaching a file, you had to do it in two steps. In V2, any action allows you to also attach files.

Add notes to release builds

You can now add some additional notes to release builds that will get stored in your release build history.

Ready for Retest always available

In V1, if a project had release builds enabled, you could only mark an issue “ready for next release” when you were done fixing it. It then had to wait for a release build. In V2, you can also mark them as “ready for retest.” It’s nice for those one-off bugs you push, or pushing up issues you may have forgotten to bundle in a release build.

Wrap up

Whew, that’s a lot of new. We expect there’ll be varied reactions to some of the changes we’ve made. It’s a completely new user interface. It’s simpler and more legible, yes, but it’s new. There’s going to be some effort involved in relearning some of the actions we all grew accustomed to in the original DoneDone. We think the new experience will pay off though. Alas, nothing is perfect, so please send your feedback, critiques, problems, or compliments. Finally, the new DoneDone is just the start. The application you see today was built to evolve. So, the more you make your voice heard, the more DoneDone will become an issue tracker built around how you work.

Have a great week, and thanks for using DoneDone!

The DoneDone team

Support? Visit www.www.getdonedone.com/support or come holler on twitter.

You'll love these too

You'll love these too

Plane