Just starting out? Here's a quick how-to. It's simple, smart, and about you.
1. Create a project.
|
Everything starts with a project. Finishing up a new piece of software for your business? Client's web site going into testing? Create a project to start resolving issues. All it takes is a name. |
|
2. Add companies and people to your project.
|
Next, add all the people responsible for the project. This includes developers, designers, copywriters, or testers. Add them to your company or create new companies. You can give people in your company administrative access as well. This lets them add new projects and manage people as well. Once you have your project and people in place, it's time to start resolving issues. |
|
3. Create and assign issues.
|
Adding an issue is intentionally simple. Give it a title, description, priority level, attachments and assign it to someone. That's it. Need to add any custom filters or tags? All issues are searchable by keywords in your title and description. DoneDone notifies the person assigned the issue via email. |
|
4. Know the issues waiting on you this second.
|
As people start assigning and working on issues, responsibility bounces back and forth. So, who needs to act next? What questions have yet to be answered? Too many issue trackers just sit idly by. They force you to figure out who has to do what next. DoneDone takes a stand to this endless sifting. The DoneDone dashboard answers the one question you care about all the time: How many issues are waiting on me? Everyone on the project knows what they need to work on right now. And that keeps issues moving along. Keep checking back on your dashboard. So long as you have no more issues waiting on you, your entire project gets closer to getting done. Done. |
|
5. Tend to the issues waiting on you. Get them off your plate.
|
"I can't reproduce your issue." / "Which user are you testing with?" / "I still see the problem." / "I think this is fixed." / "We agreed to wait until after launch." / "Can you send me a screenshot?" / "Someone else should be working on this." DoneDone issues make it obvious what has to happen next so you can get them off your plate and onto completion. |
|
6. Build releases. Close issues. Get Done Done.
|
DoneDone works especially great with clients. Use the "Release build" feature to push a batch of issues for retesting — all in one button push. DoneDone sends out emails to everyone that needs to test these issues, keeping your testing process seamless and organized. People that assigned issues are the ones responsible for testing and closing them out. |
|
