Commit 89517623 authored by Farnoosh Seifoddini's avatar Farnoosh Seifoddini

Merge branch 'issue-templates-update-feature-category-url' into 'master'

Update product feature URL in feature issue templates

See merge request gitlab-org/gitlab!49806
parents 93f37223 795cefd4
...@@ -99,7 +99,7 @@ In which enterprise tier should this feature go? See https://about.gitlab.com/ha ...@@ -99,7 +99,7 @@ In which enterprise tier should this feature go? See https://about.gitlab.com/ha
<!-- Label reminders - you should have one of each of the following labels. <!-- Label reminders - you should have one of each of the following labels.
Use the following resources to find the appropriate labels: Use the following resources to find the appropriate labels:
- https://gitlab.com/gitlab-org/gitlab/-/labels - https://gitlab.com/gitlab-org/gitlab/-/labels
- https://about.gitlab.com/handbook/product/product-categories/features/ - https://about.gitlab.com/handbook/product/categories/features/
--> -->
/label ~devops:: ~group: ~Category: /label ~devops:: ~group: ~Category:
......
...@@ -19,7 +19,7 @@ ...@@ -19,7 +19,7 @@
<!--- Use the following resources to find the appropriate labels: <!--- Use the following resources to find the appropriate labels:
- https://gitlab.com/gitlab-org/gitlab/-/labels - https://gitlab.com/gitlab-org/gitlab/-/labels
- https://about.gitlab.com/handbook/product/product-categories/features/ - https://about.gitlab.com/handbook/product/categories/features/
Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section.
......
...@@ -40,7 +40,7 @@ We generally recommend events be tracked using a [structured event](https://docs ...@@ -40,7 +40,7 @@ We generally recommend events be tracked using a [structured event](https://docs
<!-- Label reminders - you should have one of each of the following labels. <!-- Label reminders - you should have one of each of the following labels.
Use the following resources to find the appropriate labels: Use the following resources to find the appropriate labels:
- https://gitlab.com/gitlab-org/gitlab/-/labels - https://gitlab.com/gitlab-org/gitlab/-/labels
- https://about.gitlab.com/handbook/product/product-categories/features/ - https://about.gitlab.com/handbook/product/categories/features/
--> -->
/label ~devops:: ~group: ~Category: /label ~devops:: ~group: ~Category:
/label ~"snowplow tracking events" /label ~"snowplow tracking events"
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment