Tracking work with issues
If a GitLab project is where a single product or initiative lives, a GitLab issue is where a single chunk of work lives. If you’ve used tools other than GitLab for planning and tracking work, you might have run across terms such as “story” or “ticket” to describe components that are similar to GitLab issues.
Issues live within GitLab projects, with each issue only belonging to one project (although they can be moved between projects). In addition to being linked to projects, issues are also linked to a huge number of other GitLab components, as you’ll see when we introduce you to those components. In fact, these linkages are a big part of what gives GitLab its power to reach across all 10 stages of the SDLC.
The structure of a GitLab issue
GitLab issues consist of several parts, of which these four are the most important:
- A title
- A description
- Several optional metadata fields
- A threaded...
