Importing Projects from DoneDone Classic: What we import (and don't import)
While DoneDone Classic and DoneDone 2 share many similarities, they are also very different in many ways.
If you are importing projects from your existing DoneDone Classic account to DoneDone 2, we want you to be aware of how your DoneDone 2 project will look and feel different than your existing DoneDone Classic project.
If these changes impact your team's workflow significantly, we recommend leaving DoneDone Classic issues as is and only using DoneDone 2 for new projects going forward. Of course, we understand this means using (and paying for) both products at once. Please reach out to us to discuss your specific scenario so we can figure out a plan that works for you.
Note: Nothing will happen to your DoneDone Classic project if you import it into DoneDone 2. However, we recommend you archive any projects in Classic to avoid confusion with your team.
What gets imported from DoneDone Classic?
Let's start with the basics. When a project is imported from DoneDone Classic, here's what happens in DoneDone 2:
First, a new project with the same name is created.
Next, every person that has access to the project will have a membership to the new project. Because all Classic account admins can see all Classic projects, all Classic account admins will be added to your account as a DoneDone 2 admin, and automatically be assigned to the project(s) you import. However, we do not send invitation emails automatically. We'll address this in the next section below.
Note: In DoneDone 2, project membership and account roles are entirely separate concepts. In other words, you can be an account admin or owner and not have access to certain projects. By default, all Classic account admins will have membership to the imported projects. You can modify permissions to a project after the import is complete.
Finally, every private issue is imported into DoneDone 2 as a task in the new project. This includes the priority, status, due dates, tags, comments, links to attachments, and team members currently working on or watching the issue.
Note: We call an item in a project a "task" because projects in DoneDone 2 can be used for many more things than just issue tracking, by attaching a different set of custom statuses to it. However, since you're importing from Classic, all imported projects will use the default "bug tracking" workflow statuses you're accustomed to.
What happens after a project is imported?
When all issues are imported into the project, the import will be marked completed (and the next project will begin the import).
In the rare case there happens to be a failure with an import, the DoneDone 2 project will be automatically removed and our team will be notified. We'll investigate the issue and re-queue the project when we've fixed the problem. In the even rarer case that we can't solve the problem, we'll contact you via email.
When all the projects you've requested are imported, you'll receive an email from us letting you know things are ready. At that point, you can invite your new users to DoneDone 2.
What differences will I expect with a DoneDone 2 project?
As mentioned in the beginning of this article, there are some fundamental differences between DoneDone Classic and DoneDone 2. Because of these differences, some concepts in Classic don't translate perfectly to DoneDone 2 (and vice versa). Here's how we're handling these differences.
#1: Fixers and testers have been replaced by a single assignee
A fundamental difference between Classic and DoneDone 2 is assignments. In Classic, each issue required a fixer and a tester. In DoneDone 2, each task has one assignee. We will map the "assignee" based on the current status of the imported issue.
- The formula is straightforward. If an issue is currently marked as Open, In Progress, Pushed Back, Fixed not Confirmed, or On Hold then the fixer is the assignee. Otherwise, the tester is the assignee.
- If the fixer is the assignee, the tester is added as a watcher. If the tester is the assignee, then the fixer is added as a watcher.
#2: Issues will be renumbered once imported
Another fundamental difference revolves around how we number your tasks. In Classic, whenever you created a new project, issues were numbered sequentially starting at #1. In DoneDone 2, numbers are sequentially updated for the entire account. So, if you create a new project and you already have 50 tasks and conversations in it, the next task will be numbered #51.
This means that we have to renumber all issues coming in from an import.
The main benefits of this are two-fold:
- If you ever move tasks between projects, their numbers won't change. In Classic, they would be renumbered based on the highest numbered item in the current project.
- With global search, you can easily search for any task you have access to by entering in #XXX. Want to search for Task #938? Just type #938 in the search bar at the top of the DoneDone app.
#3: Public Issues are not imported into DoneDone 2
In DoneDone 2, we've introduced an entirely new concept called Mailboxes and Conversations, which take the place of what were formerly public issues in Classic. Mailboxes are a far more complete customer support and feedback utility than Public Issues. In addition, existing public issues already have unique reply-to email addresses associated to them, that specifically point to the DoneDone Classic app.
Because of these technical reasons, we simply exclude all public issues from the import.
Our recommendation: If you are heavily using Public Issues in DoneDone Classic, we recommend you create a new mailbox for each Classic project that was using Public Issues. Once you've set up these new mailboxes, update your email forwarding to your new mailbox. This way, you can manage your existing active Public Issues in Classic, but any new emails can be managed in DoneDone 2. When you've finally solved all existing Public Issues, you can archive your Classic project.
#4: Some histories will not be imported one-for-one
While the vast majority of historical data is preserved on imports, there are a few things that may not import into DoneDone 2 because of particular ways this data is stored between the two products.
- Any direct updates to a fixer or tester will not directly appear in the new issue's history (e.g. "John Doe changed the fixer to Sally Smith"). If the update was made via the "Edit Issue" feature in Classic, however, they will appear as part of the comment.
- If a due date was updated via the "Bulk Edit" feature, the history will not appear in the new issue's history.
If you have any other questions about what does or doesn't get imported, send us a note and we'll get back to you during our office hours!