Disclaimer: Some Taiga product screenshots might refer to older Taiga or Github releases. When in doubt, please follow the written instructions.
Summary: if you want to import team members too, make sure those team members are Taiga users already. A nice workaround is creating a dummy project and inviting them to it. taiga will take care of sending invites, and you’ll be able to track how many users are now part of Taiga before actually importing the project itself.
When you import your project, you often want to also import your users and keep all the relations between the work items and the team members. Taiga’s import project will first look for its team members, add them to the project, and then proceed with the content itself.
If those users don’t exist on that particular Taiga instance (tree.taiga.io or your self-managed Taiga instance), the import process will still go ahead, but the link between content and users will be lost, and it won’t be recovered even if you add those users afterward.
If you need to keep the relationships between content and team members (for example, such team member was assigned to that task or such comment was made by that team member), you need to make sure those team members already exist on that Taiga platform. You can achieve this by asking them to sign up themselves (using the same email address that identifies them on the source platform) or creating a dummy project and inviting them to it.
On the top of your Taiga screen, you have the “Projects” button. After you have created/selected a project, to invite a new team member, go to SETTINGS>MEMBERS (on the sidebar). On the top there is the NEW MEMBER button. You can do this in batches of five team members each. You can probably ignore the different ROLES option here, since this project is temporary.
Taiga will send invites to all users who are not yet part of the platform, and you will be able to track how many invites have been accepted. You can resend invites as much as you want.
Whenever you are happy with the number of people who were part of Taiga, either by signing up or accepting your invitation, you can proceed with a project import. This way, you will be able to seamlessly start working on Taiga. After this, you can safely remove the dummy project since it probably doesn’t provide any value anymore.
For more project customisation options, be sure to check The Project Customisation Guide
- To start the importation project, you have to got to your project menu, and click on “New Project” button.
New project creation
- After that, you can select how to create the project, in this case we want to “Import project”.
Start import process
- You can select which importer do you want to use, in this case, you have to select the “GitHub” importer.
- As soon as you select the github importer, you will be redirected to the GitHub authorization page, to allow Taiga to access to your repositories (during the next day). You have to click “Authorize taigaio”, to continue the process.
Authorize access to GitHub
- Then you have to select which github repository want to import.
Select GitHub repository
- Once you have selected the repository, you have to define how you want to import the project. This includes:
- The title of the project.
- The description of the project.
- How do you want to import the issues in Github.
- If the project is public or private
- If you want to keep a link from your taiga User Stories to the original github issues.
Fill new project information
- Before finishing the import process, you have to match your GitHub users with your Taiga users, this allows us to keep assignation, creation, and comments author information correctly.
- Finally, you only have to click “Import” button to start the import process, this can take a while, so be patient.
Confirm users’ selection
- After the import process, you can access to your new created project that will look like this.
- Github Project as Taiga Project (Kanban, Scrum or Issues project).
- Organization avatar as project avatar.
- Github Issues as Taiga User Stories or Issues.
- Collaborators as project members.
- Tags and tags colors.
- Changes in state, milestone, assignation, and tags.
- Milestones as sprints.
- Issues assignations as User Story/Issue assignation for the first, and User Story/Issue watchers for the rest.