Send tasks to GitLab without leaving your meeting
Many leading teams have a GitLab workflow to manage backlogs, plan sprints and log issues.
Avoid managing multiple tools or relying on notes in another tool. Create GitLab issues during your meetings so they’re ready to be prioritized for an upcoming sprint. Send any task from Parabol to GitLab.
Select your GitLab repository and include a title and description
If you’re managing multiple repositories, you can select the right one when publishing an issue. This works for both private and public repositories.
Once you migrate the card from Parabol to GitLab, it’ll be read-only. This means changes can only be made in GitLab, sidestepping the problem of different changes in different tools.
In future retrospective or team check-in meetings, you can see which tasks are managed in GitLab, and click through to see what progress you’ve made since your last meeting.
Parabol’s two-way integration lets you search for the issues you want using GitLab’s search syntax, then select the ones you want to estimate.
Once you’ve decided on your final estimates as a team, we’ll automatically take care of exporting them back to GitLab.
Decide on next steps during your sprint retrospective
Parabol lets teams hold engaging retrospective meetings through anonymous reflections, multi-player grouping and voting, and guided discussions. Choose from retrospective templates based on best practices or customize your own to suit your team’s needs.
During your guided discussion, collaboratively decide on next steps – capture bugs, feature requests or needed research.
Send retrospective action items to GitLab
GitLab lets agile teams manage their code, but doesn’t provide tools to run your retrospectives and other agile meetings – a critical component of a healthy team and continuous improvement.
With Parabol, you can raise the bar for sprint retros and also bring your new powerful insights into your GitLab Issue backlog. Make retrospectives a natural part of your GitLab workflow.