After you have gone ahead and set up your requirements, tasks and have started a sprint, you have done a lot of the planning side of what it will take to get a feature/requirement done.

Now, you want to understand how your engineering team is actually doing on a pull request and code commitment level. This will help connect the dots on how well you or your PM is doing in assigning tasks based on what can actually be done.

The way Tara enables you to optimize this is by having the Sprint Progress view to oversee tasks being done on a day-by-day basis, being able to see open PR’s and last check-in’s on the same view.

Enabling Github Sync

Enabling Github sync is going to be crucial to get as much out of your process as possible and it is fairly easy to set up on Tara.

To connect to Github, click on the Github icon located on the navigation bar of the homepage. Once you are on the Integrations page, you can select Connect on the right-hand side of the page.

Note that you need to be an admin on Tara and of the Github org to enable Github integration for the org. If not, the permissions screen will prompt you to request access from your Github organization's admin and automatically send them an email.

After selecting Connect, you will be sent to Github, to connect your Github data to Tara as shown here. Once you log in and select what you want to install, your data will start populating in your Tara instance. You should only sync the repos you want to actively import open issues from, or connect tasks to.

Note that Tara currently supports a 1 to 1 mapping between GitHub org and Tara workspace.

Connecting Each User’s Github profile

Once you have integrated with your Github repos, the commits and PRs will appear on the Sprints Progress page. However, our system will further unlock visibility for each user when he/she connects to his/her Github profile. Each member in your org can navigate to the Integrations page and select Connect Github Profile.

Once the Github user profile is linked up with the Tara user, our system will properly filter PRs that require a particular engineer’s attention and surface it up on that engineer’s homepage, so that engineer will not miss any of the team’s PRs.

For imported issues from Github, as users connect their GitHub accounts, all imported issues will be displayed as tasks in the Backlog column.

Did this answer your question?