Have more questions? Need help setting up your workflow? Get in touch!
You must connect your GitHub account to Zube before you can import your GitHub information into Zube. To connect your GitHub account, navigate to your settings page. Click the GitHub login button and follow the authentication steps.
Navigate to the Project Settings view and click on the "Members" tab. The members view will list out the project admins as well as the current project members. At the bottom is a list of teammates who are a part of your organization, but not on your project. Click "add to project" to add anyone in your organization to the project.
If you'd like to add someone to your project who is not currently in your Zube organization, you will need to invite them to join. Navigate to the organization settings page where you can search for team members already using Zube or send email invites to your teammates not using Zube yet.
The following is a list of reasons you may not be able to find your GitHub organization or repository and the solutions for each situation.
GitHub organizations can only be linked to one Zube organization. If your GitHub organization has already been imported to Zube, request access to your Zube organizations from your Zube account admins.
GitHub repositories can only belong to one Zube Project at a time. Request access to the Project from the Project admins or Zube organization admins. You can see a list of all organization Projects on the organization settings page.
GitHub allows organizations to control which third-party applications can access their repositories. If your organization has third party restrictions enabled, you will need to grant Zube access to your organization. You can read about how to do that here:
https://help.github.com/articles/approving-third-party-applications-for-your-organization/
And more about Third Party App Restrictions here:
https://help.github.com/articles/about-third-party-application-restrictions/
Repositories must have Issues enabled on GitHub to be imported into Zube. Forked repositories have Issues turned off by default.
To enable Issues for a repository:
Go to the main page of the repository on GitHub.
Click the Settings tab.
At the bottom of the Features section, select the Issues checkbox.
If you were not a member of a GitHub organization when you first logged into Zube, you may need to re-authorize Zube in order for your new organization to show up.
To update your auth token:
Log out of Zube - https://zube.io/signout (write these instructions down).
Log in to your account on https://github.com.
Click on your avatar at the top right of the screen.
Click on Settings from the dropdown menu.
Click on Authorized applications from the menu on the left.
Click the Revoke button next to Zube.
Go to the Zube homepage https://zube.io and log in.
When prompted during log in, authorize Zube on GitHub.
Still having trouble? Contact support@zube.io for help.
Sprints let you timebox what work you'd like to get done. You typically begin a sprint by setting the sprint duration (1, 2 and 4 weeks are common) and filling the sprint backlog with the work your team intends to accomplish in that time frame. As the sprint progresses, your team will pick off items in the sprint backlog to work on with the goal of having all work completed by the end of the sprint. In Zube, creating a sprint lets you use the Sprint Board and Burndown charts to track your work. Working in sprints lets you get the most out of Zube.
Milestones generally encompass a larger objective, such as hitting a major goal on your roadmap. While it may be important that cards on a milestone are prioritized, which cards are supposed to be completed this week is outside the scope of a milestone. In Zube, a milestone is similar to a label that denotes that the cards is part of a larger objective.
Have more questions? Need help setting up your workflow? Get in touch!