Introduction

GitLab is more than just a code repository—it’s an integrated DevOps platform that supports source code management, continuous integration, and a suite of project management tools. At UMD, GitLab is hosted on code.umd.edu and is the preferred tool for managing projects across the A. James Clark School of Engineering and other affiliated departments.

Getting Started

Accessing UMD’s GitLab Instance

• Login: Visit code.umd.edu and sign in using the UMD CAS (Central Authentication Service) button. New users will have their account automatically created on first login.
• Account Setup: Once logged in, you can customize your profile, manage SSH keys, and explore available projects or create a new one for your project management needs.

Core Project Management Features

GitLab offers a variety of features to help you plan, track, and collaborate on projects:

• Issues: Track tasks, bugs, or feature requests. Use detailed descriptions, assign team members, set due dates, and add comments.
• Boards: Visualize your workflow with Kanban-style boards. Customize columns (e.g., To Do, In Progress, Done) to track issue status.
• Epics & Roadmaps: Organize large initiatives by grouping related issues under epics and visualize long-term plans with roadmaps.
• Milestones: Set deadlines and track progress towards significant goals or releases by linking issues to milestones.
• Labels: Categorize issues by priority, department, or status for easier filtering and management.
• Tasks/Checklists: Break down complex issues into smaller, actionable tasks using markdown checklists within issue descriptions.
• Time Tracking: Log work hours directly on issues using quick actions (e.g., typing /spend 2h 30m in a comment).

Using GitLab for Project Management

Planning with Epics and Roadmaps

• Create Epics: Use epics to outline major features or project phases. Navigate to your group’s “Epics” section, click “New epic,” and provide a clear title and description.
• Visual Roadmaps: Add epics to a roadmap to gain a bird’s-eye view of your project timeline. This helps in planning releases and understanding dependencies.

Tracking Work with Issues and Boards

• Issue Creation: In your project’s “Issues” tab, click “New issue.” Provide a concise title, assign it to the appropriate team member, and include detailed instructions.
• Board Setup: Create and customize issue boards to visualize workflow. Set up columns such as “To Do,” “In Progress,” and “Done.” Use drag-and-drop to update status easily.
• Custom Views: Filter your board using labels or assignees to focus on specific workstreams.

Organizing with Labels and Milestones

• Labels: Create and apply custom labels (e.g., Priority: High, Department: Design) to easily sort and search issues.
• Milestones: Set milestones to group issues that share a deadline. This is particularly useful for sprint planning or marking project deliverables.

Breaking Down Tasks

• Task Checklists: Within an issue, use markdown to add a checklist (e.g., - [ ] Create wireframe) to track subtasks.
• Child Issues: For larger tasks, create linked child issues that can be managed and tracked independently.

Collaborating and Communicating

• Comments & Mentions: Use comments for discussions and @mentions to bring team members into conversations.
• Issue Discussions: Leverage threaded discussions within issues to keep all communication in context.
• Merge Requests for Docs: Non-code contributions (like updating project documentation) can be managed via merge requests in a similar manner to code changes.

Monitoring Progress with Time Tracking

• Log Time: Use quick actions (e.g., /spend 1h) in issue comments to log hours worked.
• Reports: Generate time tracking reports to analyze team productivity and identify bottlenecks.

4.7 Managing Dependencies

• Linking Issues: Create dependencies between issues to ensure that prerequisite tasks are completed first. This helps in managing sequential workflows.

Best Practices

• Keep It Organized: Regularly update issue statuses and board columns. Use labels consistently to maintain clear categorization.
• Break Down Work: Divide larger projects into manageable epics and further into issues and tasks.
• Frequent Communication: Encourage team members to use comments and mentions for quick updates and collaborative problem-solving.
• Review and Adjust: Use GitLab’s built-in analytics (like burndown charts) to review progress and adjust plans as necessary.
• Templates: Utilize issue and merge request templates to ensure consistency and clarity in documentation.

Getting Help and Support

For any questions or if you encounter issues while using GitLab for project management, please contact the Engineering Digital Service via eds@umd.edu. They are available to help you troubleshoot, provide additional training, and ensure you get the most out of the platform.

Conclusion

Using GitLab for project management at UMD allows you to centralize your planning, tracking, and collaboration in one unified platform. By taking advantage of features like issues, boards, epics, milestones, and time tracking, you can streamline your workflow and enhance team productivity. Remember to reach out to the Engineering Digital Service at eds@umd.edu for support.

Start exploring code.umd.edu today and see how GitLab can transform the way you manage your projects!