# Epics
> 原文:[https://docs.gitlab.com/ee/user/group/epics/](https://docs.gitlab.com/ee/user/group/epics/)
* [Use cases](#use-cases)
* [Manage epics](#manage-epics)
* [Relationships between epics and issues](#relationships-between-epics-and-issues)
* [Issue health status in Epic tree](#issue-health-status-in-epic-tree-ultimate)
* [Disable Issue health status in Epic tree](#disable-issue-health-status-in-epic-tree)
* [Multi-level child epics](#multi-level-child-epics-ultimate)
* [Start date and due date](#start-date-and-due-date)
* [From milestones](#from-milestones)
* [Inherited](#inherited)
* [Roadmap in epics](#roadmap-in-epics)
* [Permissions](#permissions)
* [Thread](#thread)
* [Comment or start a thread](#comment-or-start-a-thread)
* [Activity sort order](#activity-sort-order)
* [Award emoji](#award-emoji)
* [Notifications](#notifications)
# Epics[](#epics-premium "Permalink")
版本歷史
* 在[GitLab Ultimate](https://about.gitlab.com/pricing/) 10.2 中引入.
* 單級史詩在 12.8 [中移至](https://gitlab.com/gitlab-org/gitlab/-/issues/37081) [GitLab Premium](https://about.gitlab.com/pricing/) .
Epics 通過跟蹤跨項目和里程碑共享主題的問題組,使您可以更有效,更輕松地管理項目組合.
[](img/epics_list_view_v12.5.png)
## Use cases[](#use-cases "Permalink")
* 假設您的團隊正在研究一項大型功能,其中涉及在一個[小組](../index.html)內不同項目中創建的不同問題的多個討論. 借助 Epics,您可以跟蹤所有有助于該單一功能的相關活動.
* 跟蹤何時針對該組問題開始工作,以及何時結束目標工作.
* 深入討論和協作功能思想和范圍.
## Manage epics[](#manage-epics "Permalink")
要了解您可以使用史詩功能,請參閱[管理史詩](manage_epics.html) . 可能的動作包括:
* [Create an epic](manage_epics.html#create-an-epic)
* [Bulk-edit epics](../bulk_editing/index.html#bulk-edit-epics)
* [Delete an epic](manage_epics.html#delete-an-epic)
* [Close an epic](manage_epics.html#close-an-epic)
* [Reopen a closed epic](manage_epics.html#reopen-a-closed-epic)
* [Go to an epic from an issue](manage_epics.html#go-to-an-epic-from-an-issue)
* [Search for an epic from epics list page](manage_epics.html#search-for-an-epic-from-epics-list-page)
* [Make an epic confidential](manage_epics.html#make-an-epic-confidential)
* [Manage issues assigned to an epic](manage_epics.html#manage-issues-assigned-to-an-epic)
* [Manage multi-level child epics](manage_epics.html#manage-multi-level-child-epics-ultimate)
## Relationships between epics and issues[](#relationships-between-epics-and-issues "Permalink")
史詩與問題之間的可能關系是:
* 史詩是一個或多個問題的父代.
* 史詩是一個或多個子史詩的父代. 有關詳細信息,請參見[多級子史詩](#multi-level-child-epics-ultimate) .
圖 TD Parent_epic-> Issue1 Parent_epic-> Child_epic Child_epic-> Issue2
請參閱[管理分配給史詩](manage_epics.html#manage-issues-assigned-to-an-epic)的問題以獲取將事件添加到史詩,重新排序問題,在史詩之間移動問題或將問題升級到史詩的步驟.
## Issue health status in Epic tree[](#issue-health-status-in-epic-tree-ultimate "Permalink")
[Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/199184) in [GitLab Ultimate](https://about.gitlab.com/pricing/) 12.10.
您可以通過在問題上設置紅色,琥珀色或綠色的[健康狀態](../../project/issues/index.html#health-status-ultimate)來報告并快速響應單個問題和史詩的[健康](../../project/issues/index.html#health-status-ultimate) ,該狀態將顯示在史詩樹上.
### Disable Issue health status in Epic tree[](#disable-issue-health-status-in-epic-tree "Permalink")
此功能帶有默認情況下啟用的功能標志. 有關禁用它的步驟,請參閱[禁用問題運行狀況](../../project/issues/index.html#disable-issue-health-status) .
## Multi-level child epics[](#multi-level-child-epics-ultimate "Permalink")
在 GitLab Ultimate 11.7 中[引入](https://gitlab.com/gitlab-org/gitlab/-/issues/8333) .
屬于父史詩組的一個組或子組的任何史詩都可以添加. 新的兒童史詩出現在" **史詩和問題"**選項卡中史詩列表的頂部.
當您添加已鏈接到父級史詩的史詩時,到其當前父級的鏈接將被刪除.
An epic can have multiple child epics up to the maximum depth of five.
請參閱[管理多級子級史詩](manage_epics.html#manage-multi-level-child-epics-ultimate) ,以了解創建,移動,重新排序或刪除子[級史詩](manage_epics.html#manage-multi-level-child-epics-ultimate)的步驟.
## Start date and due date[](#start-date-and-due-date "Permalink")
要設置史詩的**開始日期**和**截止日期** ,請選擇以下選項之一:
* **固定** :輸入固定值.
* **從里程碑** :從當前分配給史詩問題的里程碑繼承動態值. 請注意,GitLab 12.5 用**Inherited**替換了此選項.
* **繼承** :從史詩的問題,子史詩和里程碑繼承動態值(在 GitLab 12.5 中[引入](https://gitlab.com/gitlab-org/gitlab/-/issues/7332) ,以代替**From 里程碑** ).
### From milestones[](#from-milestones "Permalink")
> 在 GitLab 12.5 中由**Inherited** [取代](https://gitlab.com/gitlab-org/gitlab/-/issues/7332) .
如果您選擇" **從里程碑**開始"作為開始日期,則 GitLab 會自動將日期設置為當前分配給添加到史詩中的問題的所有里程碑中最早的開始日期. 同樣,如果您選擇" **從里程碑** "作為截止日期,則 GitLab 會將其設置為當前分配給這些問題的所有里程碑中的最新截止日期.
這些是動態日期,如果發生以下任何情況,將重新計算這些日期:
* 將里程碑重新分配給這些問題.
* 里程碑日期更改.
* 從史詩中添加或刪除問題.
### Inherited[](#inherited "Permalink")
在 GitLab 12.5 中[引入](https://gitlab.com/gitlab-org/gitlab/-/issues/7332)以替換**From 里程碑** .
如果選擇:
* GitLab **繼承**了開始日期,它將掃描所有子史詩和分配給該史詩的問題,并將開始日期設置為與找到的最早開始日期或里程碑相匹配.
* GitLab **繼承**了截止日期,它將設置截止日期以匹配在其子史詩和問題中發現的最新截止日期或里程碑.
這些是動態日期,如果發生以下任何情況,則重新計算:
* 兒童史詩的日期發生了變化.
* 將里程碑重新分配給問題.
* 里程碑的日期會更改.
* 問題被添加到史詩中或從史詩中刪除.
由于史詩的日期可以從其子級繼承日期,因此開始日期和到期日期從底部傳播到頂部. 如果最低級別的子級史詩的開始日期發生更改(成為其父級史詩最早的開始日期),則父級史詩的開始日期將反映該更改,并將向上傳播到頂部的史詩級.
## Roadmap in epics[](#roadmap-in-epics "Permalink")
[Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/7327) in [GitLab Ultimate](https://about.gitlab.com/pricing/) 11.10.
如果你的史詩包含一個或多個[孩子史詩](#multi-level-child-epics-ultimate)其中有一個[開始或到期日](#start-date-and-due-date) ,一個[路線圖,](../roadmap/index.html)孩子史詩的觀點是父史詩中列出.
[](img/epic_view_roadmap_v12_9.png)
## Permissions[](#permissions "Permalink")
如果您有權查看史詩,并且有權查看已添加到該史詩的問題,則可以在史詩問題列表中查看該問題.
如果您有權編輯史詩并且有權編輯問題,則可以將問題添加到史詩中或從史詩中刪除.
請注意,對于給定的組,所有項目的可見性必須與該組相同,或限制較少. 這意味著,如果您有權訪問某個小組的史詩,那么您已經可以訪問該小組的項目.
您也可以查閱[組權限表](../../permissions.html#group-members-permissions) .
## Thread[](#thread "Permalink")
* 評論:通過在該史詩中的評論中發布評論來協作. 這些文本字段也完全支持[GitLab Flavored Markdown](../../markdown.html#gitlab-flavored-markdown-gfm) .
## Comment or start a thread[](#comment-or-start-a-thread "Permalink")
寫下評論后,您可以:
* 點擊**評論** ,您的評論將被發布.
* 單擊" **開始主題"** ,您將在該史詩般的討論中開始一個主題.
### Activity sort order[](#activity-sort-order "Permalink")
[Introduced](https://https://gitlab.com/gitlab-org/gitlab/-/issues/214364) in [GitLab Premium](https://about.gitlab.com/pricing/) 13.2.
您可以顛倒默認順序,并與按頂部的最新項目排序的活動供稿進行交互. 您的首選項通過本地存儲保存,并自動應用于您查看的每個問題.
要更改活動排序順序,請單擊**最舊的第一個**下拉菜單,然后選擇最舊或最新的項目以首先顯示.
[](img/epic_activity_sort_order_v13_2.png)
## Award emoji[](#award-emoji "Permalink")
您可以為該史詩或其評論[授予表情符號](../../award_emojis.html) .
## Notifications[](#notifications "Permalink")
您可以[打開通知](../../profile/notifications.html)以[通知](../../profile/notifications.html)史詩事件.
- GitLab Docs
- Installation
- Requirements
- GitLab cloud native Helm Chart
- Install GitLab with Docker
- Installation from source
- Install GitLab on Microsoft Azure
- Installing GitLab on Google Cloud Platform
- Installing GitLab on Amazon Web Services (AWS)
- Analytics
- Code Review Analytics
- Productivity Analytics
- Value Stream Analytics
- Kubernetes clusters
- Adding and removing Kubernetes clusters
- Adding EKS clusters
- Adding GKE clusters
- Group-level Kubernetes clusters
- Instance-level Kubernetes clusters
- Canary Deployments
- Cluster Environments
- Deploy Boards
- GitLab Managed Apps
- Crossplane configuration
- Cluster management project (alpha)
- Kubernetes Logs
- Runbooks
- Serverless
- Deploying AWS Lambda function using GitLab CI/CD
- Securing your deployed applications
- Groups
- Contribution Analytics
- Custom group-level project templates
- Epics
- Manage epics
- Group Import/Export
- Insights
- Issues Analytics
- Iterations
- Public access
- SAML SSO for GitLab.com groups
- SCIM provisioning using SAML SSO for GitLab.com groups
- Subgroups
- Roadmap
- Projects
- GitLab Secure
- Security Configuration
- Container Scanning
- Dependency Scanning
- Dependency List
- Static Application Security Testing (SAST)
- Secret Detection
- Dynamic Application Security Testing (DAST)
- GitLab Security Dashboard
- Offline environments
- Standalone Vulnerability pages
- Security scanner integration
- Badges
- Bulk editing issues and merge requests at the project level
- Code Owners
- Compliance
- License Compliance
- Compliance Dashboard
- Create a project
- Description templates
- Deploy Keys
- Deploy Tokens
- File finder
- Project integrations
- Integrations
- Atlassian Bamboo CI Service
- Bugzilla Service
- Custom Issue Tracker service
- Discord Notifications service
- Enabling emails on push
- GitHub project integration
- Hangouts Chat service
- Atlassian HipChat
- Irker IRC Gateway
- GitLab Jira integration
- Mattermost Notifications Service
- Mattermost slash commands
- Microsoft Teams service
- Mock CI Service
- Prometheus integration
- Redmine Service
- Slack Notifications Service
- Slack slash commands
- GitLab Slack application
- Webhooks
- YouTrack Service
- Insights
- Issues
- Crosslinking Issues
- Design Management
- Confidential issues
- Due dates
- Issue Boards
- Issue Data and Actions
- Labels
- Managing issues
- Milestones
- Multiple Assignees for Issues
- Related issues
- Service Desk
- Sorting and ordering issue lists
- Issue weight
- Associate a Zoom meeting with an issue
- Merge requests
- Allow collaboration on merge requests across forks
- Merge Request Approvals
- Browser Performance Testing
- How to create a merge request
- Cherry-pick changes
- Code Quality
- Load Performance Testing
- Merge Request dependencies
- Fast-forward merge requests
- Merge when pipeline succeeds
- Merge request conflict resolution
- Reverting changes
- Reviewing and managing merge requests
- Squash and merge
- Merge requests versions
- Draft merge requests
- Members of a project
- Migrating projects to a GitLab instance
- Import your project from Bitbucket Cloud to GitLab
- Import your project from Bitbucket Server to GitLab
- Migrating from ClearCase
- Migrating from CVS
- Import your project from FogBugz to GitLab
- Gemnasium
- Import your project from GitHub to GitLab
- Project importing from GitLab.com to your private GitLab instance
- Import your project from Gitea to GitLab
- Import your Jira project issues to GitLab
- Migrating from Perforce Helix
- Import Phabricator tasks into a GitLab project
- Import multiple repositories by uploading a manifest file
- Import project from repo by URL
- Migrating from SVN to GitLab
- Migrating from TFVC to Git
- Push Options
- Releases
- Repository
- Branches
- Git Attributes
- File Locking
- Git file blame
- Git file history
- Repository mirroring
- Protected branches
- Protected tags
- Push Rules
- Reduce repository size
- Signing commits with GPG
- Syntax Highlighting
- GitLab Web Editor
- Web IDE
- Requirements Management
- Project settings
- Project import/export
- Project access tokens (Alpha)
- Share Projects with other Groups
- Snippets
- Static Site Editor
- Wiki
- Project operations
- Monitor metrics for your CI/CD environment
- Set up alerts for Prometheus metrics
- Embedding metric charts within GitLab-flavored Markdown
- Embedding Grafana charts
- Using the Metrics Dashboard
- Dashboard YAML properties
- Metrics dashboard settings
- Panel types for dashboards
- Using Variables
- Templating variables for metrics dashboards
- Prometheus Metrics library
- Monitoring AWS Resources
- Monitoring HAProxy
- Monitoring Kubernetes
- Monitoring NGINX
- Monitoring NGINX Ingress Controller
- Monitoring NGINX Ingress Controller with VTS metrics
- Alert Management
- Error Tracking
- Tracing
- Incident Management
- GitLab Status Page
- Feature Flags
- GitLab CI/CD
- GitLab CI/CD pipeline configuration reference
- GitLab CI/CD include examples
- Introduction to CI/CD with GitLab
- Getting started with GitLab CI/CD
- How to enable or disable GitLab CI/CD
- Using SSH keys with GitLab CI/CD
- Migrating from CircleCI
- Migrating from Jenkins
- Auto DevOps
- Getting started with Auto DevOps
- Requirements for Auto DevOps
- Customizing Auto DevOps
- Stages of Auto DevOps
- Upgrading PostgreSQL for Auto DevOps
- Cache dependencies in GitLab CI/CD
- GitLab ChatOps
- Cloud deployment
- Docker integration
- Building Docker images with GitLab CI/CD
- Using Docker images
- Building images with kaniko and GitLab CI/CD
- GitLab CI/CD environment variables
- Predefined environment variables reference
- Where variables can be used
- Deprecated GitLab CI/CD variables
- Environments and deployments
- Protected Environments
- GitLab CI/CD Examples
- Test a Clojure application with GitLab CI/CD
- Using Dpl as deployment tool
- Testing a Phoenix application with GitLab CI/CD
- End-to-end testing with GitLab CI/CD and WebdriverIO
- DevOps and Game Dev with GitLab CI/CD
- Deploy a Spring Boot application to Cloud Foundry with GitLab CI/CD
- How to deploy Maven projects to Artifactory with GitLab CI/CD
- Testing PHP projects
- Running Composer and NPM scripts with deployment via SCP in GitLab CI/CD
- Test and deploy Laravel applications with GitLab CI/CD and Envoy
- Test and deploy a Python application with GitLab CI/CD
- Test and deploy a Ruby application with GitLab CI/CD
- Test and deploy a Scala application to Heroku
- GitLab CI/CD for external repositories
- Using GitLab CI/CD with a Bitbucket Cloud repository
- Using GitLab CI/CD with a GitHub repository
- GitLab Pages
- GitLab Pages
- GitLab Pages domain names, URLs, and baseurls
- Create a GitLab Pages website from scratch
- Custom domains and SSL/TLS Certificates
- GitLab Pages integration with Let's Encrypt
- GitLab Pages Access Control
- Exploring GitLab Pages
- Incremental Rollouts with GitLab CI/CD
- Interactive Web Terminals
- Optimizing GitLab for large repositories
- Metrics Reports
- CI/CD pipelines
- Pipeline Architecture
- Directed Acyclic Graph
- Multi-project pipelines
- Parent-child pipelines
- Pipelines for Merge Requests
- Pipelines for Merged Results
- Merge Trains
- Job artifacts
- Pipeline schedules
- Pipeline settings
- Triggering pipelines through the API
- Review Apps
- Configuring GitLab Runners
- GitLab CI services examples
- Using MySQL
- Using PostgreSQL
- Using Redis
- Troubleshooting CI/CD
- GitLab Package Registry
- GitLab Container Registry
- Dependency Proxy
- GitLab Composer Repository
- GitLab Conan Repository
- GitLab Maven Repository
- GitLab NPM Registry
- GitLab NuGet Repository
- GitLab PyPi Repository
- API Docs
- API resources
- .gitignore API
- GitLab CI YMLs API
- Group and project access requests API
- Appearance API
- Applications API
- Audit Events API
- Avatar API
- Award Emoji API
- Project badges API
- Group badges API
- Branches API
- Broadcast Messages API
- Project clusters API
- Group clusters API
- Instance clusters API
- Commits API
- Container Registry API
- Custom Attributes API
- Dashboard annotations API
- Dependencies API
- Deploy Keys API
- Deployments API
- Discussions API
- Dockerfiles API
- Environments API
- Epics API
- Events
- Feature Flags API
- Feature flag user lists API
- Freeze Periods API
- Geo Nodes API
- Group Activity Analytics API
- Groups API
- Import API
- Issue Boards API
- Group Issue Boards API
- Issues API
- Epic Issues API
- Issues Statistics API
- Jobs API
- Keys API
- Labels API
- Group Labels API
- License
- Licenses API
- Issue links API
- Epic Links API
- Managed Licenses API
- Markdown API
- Group and project members API
- Merge request approvals API
- Merge requests API
- Project milestones API
- Group milestones API
- Namespaces API
- Notes API
- Notification settings API
- Packages API
- Pages domains API
- Pipeline schedules API
- Pipeline triggers API
- Pipelines API
- Project Aliases API
- Project import/export API
- Project repository storage moves API
- Project statistics API
- Project templates API
- Projects API
- Protected branches API
- Protected tags API
- Releases API
- Release links API
- Repositories API
- Repository files API
- Repository submodules API
- Resource label events API
- Resource milestone events API
- Resource weight events API
- Runners API
- SCIM API
- Search API
- Services API
- Application settings API
- Sidekiq Metrics API
- Snippets API
- Project snippets
- Application statistics API
- Suggest Changes API
- System hooks API
- Tags API
- Todos API
- Users API
- Project-level Variables API
- Group-level Variables API
- Version API
- Vulnerabilities API
- Vulnerability Findings API
- Wikis API
- GraphQL API
- Getting started with GitLab GraphQL API
- GraphQL API Resources
- API V3 to API V4
- Validate the .gitlab-ci.yml (API)
- User Docs
- Abuse reports
- User account
- Active sessions
- Deleting a User account
- Permissions
- Personal access tokens
- Profile preferences
- Threads
- GitLab and SSH keys
- GitLab integrations
- Git
- GitLab.com settings
- Infrastructure as code with Terraform and GitLab
- GitLab keyboard shortcuts
- GitLab Markdown
- AsciiDoc
- GitLab Notification Emails
- GitLab Quick Actions
- Autocomplete characters
- Reserved project and group names
- Search through GitLab
- Advanced Global Search
- Advanced Syntax Search
- Time Tracking
- GitLab To-Do List
- Administrator Docs
- Reference architectures
- Reference architecture: up to 1,000 users
- Reference architecture: up to 2,000 users
- Reference architecture: up to 3,000 users
- Reference architecture: up to 5,000 users
- Reference architecture: up to 10,000 users
- Reference architecture: up to 25,000 users
- Reference architecture: up to 50,000 users
- Troubleshooting a reference architecture set up
- Working with the bundled Consul service
- Configuring PostgreSQL for scaling
- Configuring GitLab application (Rails)
- Load Balancer for multi-node GitLab
- Configuring a Monitoring node for Scaling and High Availability
- NFS
- Working with the bundled PgBouncer service
- Configuring Redis for scaling
- Configuring Sidekiq
- Admin Area settings
- Continuous Integration and Deployment Admin settings
- Custom instance-level project templates
- Diff limits administration
- Enable and disable GitLab features deployed behind feature flags
- Geo nodes Admin Area
- GitLab Pages administration
- Health Check
- Job logs
- Labels administration
- Log system
- PlantUML & GitLab
- Repository checks
- Repository storage paths
- Repository storage types
- Account and limit settings
- Service templates
- System hooks
- Changing your time zone
- Uploads administration
- Abuse reports
- Activating and deactivating users
- Audit Events
- Blocking and unblocking users
- Broadcast Messages
- Elasticsearch integration
- Gitaly
- Gitaly Cluster
- Gitaly reference
- Monitoring GitLab
- Monitoring GitLab with Prometheus
- Performance Bar
- Usage statistics
- Object Storage
- Performing Operations in GitLab
- Cleaning up stale Redis sessions
- Fast lookup of authorized SSH keys in the database
- Filesystem Performance Benchmarking
- Moving repositories managed by GitLab
- Run multiple Sidekiq processes
- Sidekiq MemoryKiller
- Switching to Puma
- Understanding Unicorn and unicorn-worker-killer
- User lookup via OpenSSH's AuthorizedPrincipalsCommand
- GitLab Package Registry administration
- GitLab Container Registry administration
- Replication (Geo)
- Geo database replication
- Geo with external PostgreSQL instances
- Geo configuration
- Using a Geo Server
- Updating the Geo nodes
- Geo with Object storage
- Docker Registry for a secondary node
- Geo for multiple nodes
- Geo security review (Q&A)
- Location-aware Git remote URL with AWS Route53
- Tuning Geo
- Removing secondary Geo nodes
- Geo data types support
- Geo Frequently Asked Questions
- Geo Troubleshooting
- Geo validation tests
- Disaster Recovery (Geo)
- Disaster recovery for planned failover
- Bring a demoted primary node back online
- Automatic background verification
- Rake tasks
- Back up and restore GitLab
- Clean up
- Namespaces
- Maintenance Rake tasks
- Geo Rake Tasks
- GitHub import
- Import bare repositories
- Integrity check Rake task
- LDAP Rake tasks
- Listing repository directories
- Praefect Rake tasks
- Project import/export administration
- Repository storage Rake tasks
- Generate sample Prometheus data
- Uploads migrate Rake tasks
- Uploads sanitize Rake tasks
- User management
- Webhooks administration
- X.509 signatures
- Server hooks
- Static objects external storage
- Updating GitLab
- GitLab release and maintenance policy
- Security
- Password Storage
- Custom password length limits
- Restrict allowed SSH key technologies and minimum length
- Rate limits
- Webhooks and insecure internal web services
- Information exclusivity
- How to reset your root password
- How to unlock a locked user from the command line
- User File Uploads
- How we manage the TLS protocol CRIME vulnerability
- User email confirmation at sign-up
- Security of running jobs
- Proxying assets
- CI/CD Environment Variables
- Contributor and Development Docs
- Contribute to GitLab
- Community members & roles
- Implement design & UI elements
- Issues workflow
- Merge requests workflow
- Code Review Guidelines
- Style guides
- GitLab Architecture Overview
- CI/CD development documentation
- Database guides
- Database Review Guidelines
- Database Review Guidelines
- Migration Style Guide
- What requires downtime?
- Understanding EXPLAIN plans
- Rake tasks for developers
- Mass inserting Rails models
- GitLab Documentation guidelines
- Documentation Style Guide
- Documentation structure and template
- Documentation process
- Documentation site architecture
- Global navigation
- GitLab Docs monthly release process
- Telemetry Guide
- Usage Ping Guide
- Snowplow Guide
- Experiment Guide
- Feature flags in development of GitLab
- Feature flags process
- Developing with feature flags
- Feature flag controls
- Document features deployed behind feature flags
- Frontend Development Guidelines
- Accessibility & Readability
- Ajax
- Architecture
- Axios
- Design Patterns
- Frontend Development Process
- DropLab
- Emojis
- Filter
- Frontend FAQ
- GraphQL
- Icons and SVG Illustrations
- InputSetter
- Performance
- Principles
- Security
- Tooling
- Vuex
- Vue
- Geo (development)
- Geo self-service framework (alpha)
- Gitaly developers guide
- GitLab development style guides
- API style guide
- Go standards and style guidelines
- GraphQL API style guide
- Guidelines for shell commands in the GitLab codebase
- HTML style guide
- JavaScript style guide
- Migration Style Guide
- Newlines style guide
- Python Development Guidelines
- SCSS style guide
- Shell scripting standards and style guidelines
- Sidekiq debugging
- Sidekiq Style Guide
- SQL Query Guidelines
- Vue.js style guide
- Instrumenting Ruby code
- Testing standards and style guidelines
- Flaky tests
- Frontend testing standards and style guidelines
- GitLab tests in the Continuous Integration (CI) context
- Review Apps
- Smoke Tests
- Testing best practices
- Testing levels
- Testing Rails migrations at GitLab
- Testing Rake tasks
- End-to-end Testing
- Beginner's guide to writing end-to-end tests
- End-to-end testing Best Practices
- Dynamic Element Validation
- Flows in GitLab QA
- Page objects in GitLab QA
- Resource class in GitLab QA
- Style guide for writing end-to-end tests
- Testing with feature flags
- Translate GitLab to your language
- Internationalization for GitLab
- Translating GitLab
- Proofread Translations
- Merging translations from CrowdIn
- Value Stream Analytics development guide
- GitLab subscription
- Activate GitLab EE with a license