From 2a5cab8fe06157ed5ff249bef6d3ba9ca0220d80 Mon Sep 17 00:00:00 2001
From: jkbquabeck <139474964+jkbquabeck@users.noreply.github.com>
Date: Fri, 12 Jan 2024 16:44:58 +0100
Subject: [PATCH] updated MDS feature template (#355)

* updated MDS feature template

* Iterated the design

* Update mds_feature_request.md

---------

Co-authored-by: Tim Berthold <75306992+tmberthold@users.noreply.github.com>
---
 .github/ISSUE_TEMPLATE/mds_feature_request.md | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/.github/ISSUE_TEMPLATE/mds_feature_request.md b/.github/ISSUE_TEMPLATE/mds_feature_request.md
index 4b55f531..918890e5 100644
--- a/.github/ISSUE_TEMPLATE/mds_feature_request.md
+++ b/.github/ISSUE_TEMPLATE/mds_feature_request.md
@@ -26,6 +26,14 @@ _What problems does that user face that existing functionalities do solve?_
 
 _Describe whether this request is related to an existing workflow, feature, or otherwise something in the product today. Or, does this open us up to new innovative ideas?_
 
+## Scope check
+
+_Is this feature part of the contracted scope?_
+- [ ] It is part of the contracted scope
+- [ ] It is not part of the contracted scope
+
+If not, please add the label "mds/future-scope"
+
 ## (For sovity Team to complete) Stakeholders
 
 _Add more on who asked for this, i.e. company, person, how much they pay us, what their tier is, are they a strategic account, etc. Who needs to be kept up-to-date about this feature?_