Tip 24 - Zoho Sprints integrates with source code management tools
Are you an agile team that manages all your code repositories in GitHub, GitLab, or Bitbucket tools? Now you can manage your code repositories the agile way right at one point. Zoho Sprints now offers a suite of integrations with GitHub, GitLab, and Bitbucket.
Integrating both the applications
We have all the three applications listed in our Integrations section under Settings. You have to Authorize your third-party tool with Zoho Sprints to initiate the integration process.
Mapping repositories
After linking both the applications, all your repositories will be listed under the My Repository section. Map the required repositories to your Team Repository.
Associating projects to repositories
Once the repositories are mapped, you can associate the existing projects to each repository. You can also associate multiple projects to a single repository.
Adding commits and pull requests
After the projects are mapped to the repositories, you can attach commits and pull requests to the work items. Choose the branch and attach your commits and pull requests, anytime.
Using quick commands in third-party tools
You can also add single or multiple commands to a single or multiple work items. Check out the syntax for the commands and start managing your work directly from your third-party tool.
Manage your repositories effortlessly with these integrations. Add your comments below if you have any queries or contact support@zohosprints.com.
Topic Participants
monica
Sticky Posts
Tip #28 - Plan less and deliver more using WIP limit in Zoho Sprints
Hello, It's been a while since we met with a quick, interesting tip. As the saying goes, "Too much of anything is good for nothing", today the focus is on delivering your outcomes with the right amount of planning. Your plan should be practical, calculative, and achievable for driving a qualitative success. Laura's plan Laura has a habit of planning her project deliverables before assigning work to her team-mates. Once the plan is finalized, she schedules a general meeting with her team andTip # 3- Working on the Scrum board
Continuing from our Tip #2 on leading to a sprint, let's see how to manage the work items on the Scrum board. Once you start the sprint your work items are automatically displayed on the Scrum board where you will actually manage the work items. It is a snapshot of the backlog items identified for the current sprint. The layout of the Scrum board Simply put, the scrum board is just like a physical board with sticky notes on which the work items of the active sprint are displayed. The scrum boardTip#2- Leading you to a Sprint
Product Backlog After the user stories are written and finalized, they are sorted to create the Product Backlog for the project during the Backlog Grooming meeting. This is a master list of all the work items that have been identified for the project and sorted by priority. Requirements are not constant during this period.The Product Backlog is dynamic and is an ongoing process. Every user story in the Product Backlog is customer centric. The Product Backlog includes: User centric stories based onTip #1- Why swimlanes?
Lanes define a clear path to reach your destination. In Agile, swimlane is one such concept that sets a simple and clear process of the work that you do. The concept of swimlane can be related to the pool, where the swimmers gather in their respective lanes to start off. Similar to the pool, work items are grouped in different categories. Each category is referred as a lane and is displayed in horizontal format. Swimlanes are effective in categorizing the work items with respective to specific