220.10 a

Description: Implementing a PMS with GitLab's features. I think templates are very handy and important in a PMS like this.

#200#DevOps#220#Project_Management_System#220.10#PMS_in_Action_Implementation#220.10 a#GitLab_Issue_template

GitLab issue templates

#Tag

Audience

Who wants to learn about PMS implementation examples with GitLab

Overview

GitLab issue templates (v16.11)

There are no issue templates, but there are issue description templates.

It is provided as an md file in the .gitlab/issue_templates path and can be used by default when used as Default.md (premium and above)
Additionally, you can share a specific template within a group and make it available to all projects in the group (premium and above)
Special commands like / can be used to assign labels or assigned within an issue.

Labeling is not dynamic. Different labels for different authors.
You need to run webhooks or pipelines separately.

Content

## Summary

(Summarize the issue concisely)

## Current Behavior

(What actually happens)

## Expected Behavior 

(What you should see instead)

## Steps to Reproduce

(How one can reproduce the issue - this is very important)

## Relevant Logs and/or Screenshots

(Paste any relevant logs - use code blocks (```) to format console output, logs, and code, as 
it's very hard to read otherwise.)

## Possible Fixes

(If you can, link to the line of code that might be responsible for the problem)

## Labels

/label ~team::devops 
/label ~type::internal

## Assign

/assign me

Conclusion

Using template
Dont support dynamic labeling