diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-10-05 16:54:15 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-10-05 16:54:15 +0300 |
commit | be834a25982746ffd85252ff502df42bb88cb9d5 (patch) | |
tree | b4d6a8ba0931e12fac08f05abea33a3b8ec2c8a2 /.gitlab/issue_templates/Implementation.md | |
parent | ee925a3597f27e92f83a50937a64068109675b3d (diff) |
Add latest changes from gitlab-org/gitlab@13-5-stable-eev13.5.0-rc32
Diffstat (limited to '.gitlab/issue_templates/Implementation.md')
-rw-r--r-- | .gitlab/issue_templates/Implementation.md | 62 |
1 files changed, 62 insertions, 0 deletions
diff --git a/.gitlab/issue_templates/Implementation.md b/.gitlab/issue_templates/Implementation.md new file mode 100644 index 00000000000..dc5eb18a25e --- /dev/null +++ b/.gitlab/issue_templates/Implementation.md @@ -0,0 +1,62 @@ +<!-- +Implementation issues are used break-up a large piece of work into small, discrete tasks that can +move independently through the build workflow steps. They're typically used to populate a Feature +Epic. Once created, an implementation issue is usually refined in order to populate and review the +implementation plan and weight. +Example workflow: https://about.gitlab.com/handbook/engineering/development/threat-management/planning/diagram.html#plan +--> + +## Why are we doing this work +<!-- +A brief explanation of the why, not the what or how. Assume the reader doesn't know the +background and won't have time to dig-up information from comment threads. +--> + + +## Relevant links +<!-- +Information that the developer might need to refer to when implementing the issue. + +- [Design Issue](https://gitlab.com/gitlab-org/gitlab/-/issues/<id>) + - [Design 1](https://gitlab.com/gitlab-org/gitlab/-/issues/<id>/designs/<image>.png) + - [Design 2](https://gitlab.com/gitlab-org/gitlab/-/issues/<id>/designs/<image>.png) +- [Similar implementation](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/<id>) +--> + + +## Non-functional requirements +<!-- +Add details for required items and delete others. +--> + +- [ ] Documentation: +- [ ] Feature flag: +- [ ] Performance: +- [ ] Testing: + + +## Implementation plan +<!-- +Steps and the parts of the code that will need to get updated. The plan can also +call-out responsibilities for other team members or teams. +--> + +- [ ] ~frontend Step 1 + - [ ] @person Step 1a +- [ ] ~frontend Step 2 + + +<!-- +Workflow and other relevant labels + +~"group::" ~"Category:" ~"GitLab Ultimate" +--> +/label ~"workflow::refinement" + +<!-- +Other settings you might want to include when creating the issue. + +/milestone %"Next 1-3 releases" +/assign @ +/epic & +--> |