diff options
Diffstat (limited to 'data/deprecations/14-5-deprecation-vsa-announce-deprecation-of-vsa-filtering-calculation.yml')
| -rw-r--r-- | data/deprecations/14-5-deprecation-vsa-announce-deprecation-of-vsa-filtering-calculation.yml | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/data/deprecations/14-5-deprecation-vsa-announce-deprecation-of-vsa-filtering-calculation.yml b/data/deprecations/14-5-deprecation-vsa-announce-deprecation-of-vsa-filtering-calculation.yml index 5706e826a9d..2c16aca5df6 100644 --- a/data/deprecations/14-5-deprecation-vsa-announce-deprecation-of-vsa-filtering-calculation.yml +++ b/data/deprecations/14-5-deprecation-vsa-announce-deprecation-of-vsa-filtering-calculation.yml @@ -3,9 +3,10 @@ announcement_date: "2021-11-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. removal_milestone: "15.0" # The milestone when this feature is planned to be removed removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed + breaking_change: true body: | # Do not modify this line, instead modify the lines below. We are changing how the date filter works in Value Stream Analytics. Instead of filtering by the time that the issue or merge request was created, the date filter will filter by the end event time of the given stage. This will result in completely different figures after this change has rolled out. - + If you monitor Value Stream Analytics metrics and rely on the date filter, to avoid losing data, you must save the data prior to this change. stage: manage # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth tiers: # (optional - may be required in the future) An array of tiers that the feature is available in currently. e.g., [Free, Silver, Gold, Core, Premium, Ultimate] |