Merge branch 'dev' into implementation/42204-add-file-links-collection-to-work-package-resource

.github/workflows/test-core.yml

@@ -30,10 +30,10 @@ jobs:
       uses: actions/cache@v2
       with:
         path: /tmp/cache
-        key: ${{ runner.os }}-ruby3-core-tests-units-${{ hashFiles('**/Gemfile.lock') }}
+        key: ${{ runner.os }}-ruby31-core-tests-units-${{ hashFiles('**/Gemfile.lock') }}
         restore-keys: |
-          ${{ runner.os }}-ruby3-core-tests-units-
-          ${{ runner.os }}-ruby3-core-tests-
+          ${{ runner.os }}-ruby31-core-tests-units-
+          ${{ runner.os }}-ruby31-core-tests-
     - name: test
       run: |
         docker-compose -f docker-compose.ci.yml build --pull ci
@@ -60,10 +60,10 @@ jobs:
       uses: actions/cache@v2
       with:
         path: /tmp/cache
-        key: ${{ runner.os }}-ruby3-core-tests-features-${{ hashFiles('**/Gemfile.lock') }}
+        key: ${{ runner.os }}-ruby31-core-tests-features-${{ hashFiles('**/Gemfile.lock') }}
         restore-keys: |
-          ${{ runner.os }}-ruby3-core-tests-features-
-          ${{ runner.os }}-ruby3-core-tests-
+          ${{ runner.os }}-ruby31-core-tests-features-
+          ${{ runner.os }}-ruby31-core-tests-
     - name: test
       run: |
         docker-compose -f docker-compose.ci.yml build --pull ci

.ruby-version

@@ -1 +1 @@
-3.0.4
+3.1.2

Gemfile

@@ -28,7 +28,7 @@
 
 source 'https://rubygems.org'
 
-ruby '~> 3.0.4'
+ruby '~> 3.1.2'
 
 gem 'actionpack-xml_parser', '~> 2.0.0'
 gem 'activemodel-serializers-xml', '~> 1.0.1'
@@ -62,6 +62,12 @@ gem 'typed_dag', '~> 2.0.2'
 
 gem 'addressable', '~> 2.8.0'
 
+# Needed to make rails 6.x work with ruby 3.1, can be dropped
+# after migrated to rails 7 (see https://stackoverflow.com/a/70500221)
+gem 'net-smtp', '~> 0.3.1', require: false
+gem 'net-pop', '~> 0.1.1', require: false
+gem 'net-imap', '~> 0.2.3', require: false
+
 # Remove whitespace from model input
 gem "auto_strip_attributes", "~> 2.5"
 

Gemfile.lock

@@ -283,7 +283,7 @@ GEM
     awesome_nested_set (3.5.0)
       activerecord (>= 4.0.0, < 7.1)
     aws-eventstream (1.2.0)
-    aws-partitions (1.581.0)
+    aws-partitions (1.583.0)
     aws-sdk-core (3.130.2)
       aws-eventstream (~> 1, >= 1.0.2)
       aws-partitions (~> 1, >= 1.525.0)
@@ -292,7 +292,7 @@ GEM
     aws-sdk-kms (1.56.0)
       aws-sdk-core (~> 3, >= 3.127.0)
       aws-sigv4 (~> 1.1)
-    aws-sdk-s3 (1.113.2)
+    aws-sdk-s3 (1.114.0)
       aws-sdk-core (~> 3, >= 3.127.0)
       aws-sdk-kms (~> 1)
       aws-sigv4 (~> 1.4)
@@ -404,6 +404,7 @@ GEM
       activerecord (>= 3.0, < 8.0)
       delayed_job (>= 3.0, < 5)
     diff-lcs (1.5.0)
+    digest (3.1.0)
     disposable (0.6.2)
       declarative (>= 0.0.9, < 1.0.0)
       representable (>= 3.1.1, < 3.2.0)
@@ -554,6 +555,7 @@ GEM
       ice_cube (~> 0.16)
     ice_cube (0.16.4)
     interception (0.5)
+    io-wait (0.2.1)
     iso8601 (0.13.0)
     jmespath (1.6.1)
     json (2.6.1)
@@ -625,7 +627,22 @@ GEM
     mustermann-grape (1.0.1)
       mustermann (>= 1.0.0)
     nap (1.1.0)
+    net-imap (0.2.3)
+      digest
+      net-protocol
+      strscan
     net-ldap (0.17.0)
+    net-pop (0.1.1)
+      digest
+      net-protocol
+      timeout
+    net-protocol (0.1.2)
+      io-wait
+      timeout
+    net-smtp (0.3.1)
+      digest
+      net-protocol
+      timeout
     netrc (0.11.0)
     nio4r (2.5.8)
     no_proxy_fix (0.1.2)
@@ -909,6 +926,7 @@ GEM
     stackprof (0.2.19)
     stringex (2.8.5)
     stringio (3.0.1)
+    strscan (3.0.1)
     structured_warnings (0.4.0)
     svg-graph (2.2.1)
     swd (1.3.0)
@@ -925,6 +943,7 @@ GEM
     thor (1.2.1)
     tilt (2.0.10)
     timecop (0.9.5)
+    timeout (0.2.0)
     trailblazer-option (0.1.2)
     ttfunk (1.7.0)
     typed_dag (2.0.2)
@@ -1043,7 +1062,10 @@ DEPENDENCIES
   mini_magick (~> 4.11.0)
   multi_json (~> 1.15.0)
   my_page!
+  net-imap (~> 0.2.3)
   net-ldap (~> 0.17.0)
+  net-pop (~> 0.1.1)
+  net-smtp (~> 0.3.1)
   nokogiri (~> 1.13.4)
   oj (~> 3.13.0)
   okcomputer (~> 1.18.1)
@@ -1147,7 +1169,7 @@ DEPENDENCIES
   with_advisory_lock (~> 4.6.0)
 
 RUBY VERSION
-   ruby 3.0.4p208
+   ruby 3.1.2p20
 
 BUNDLED WITH
    2.3.12

app/models/queries/queries.rb

@@ -34,7 +34,6 @@ module Queries::Queries
   ::Queries::Register.register(QueryQuery) do
     filter Filters::ProjectFilter
     filter Filters::ProjectIdentifierFilter
-    filter Filters::HiddenFilter
     filter Filters::UpdatedAtFilter
     filter Filters::IdFilter
   end

app/models/queries/queries/filters/hidden_filter.rb

@@ -1,35 +0,0 @@
-#-- copyright
-# OpenProject is an open source project management software.
-# Copyright (C) 2012-2022 the OpenProject GmbH
-#
-# This program is free software; you can redistribute it and/or
-# modify it under the terms of the GNU General Public License version 3.
-#
-# OpenProject is a fork of ChiliProject, which is a fork of Redmine. The copyright follows:
-# Copyright (C) 2006-2013 Jean-Philippe Lang
-# Copyright (C) 2010-2013 the ChiliProject Team
-#
-# This program is free software; you can redistribute it and/or
-# modify it under the terms of the GNU General Public License
-# as published by the Free Software Foundation; either version 2
-# of the License, or (at your option) any later version.
-#
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-# GNU General Public License for more details.
-#
-# You should have received a copy of the GNU General Public License
-# along with this program; if not, write to the Free Software
-# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA.
-#
-# See COPYRIGHT and LICENSE files for more details.
-#++
-
-class Queries::Queries::Filters::HiddenFilter < Queries::Queries::Filters::QueryFilter
-  include Queries::Filters::Shared::BooleanFilter
-
-  def self.key
-    :hidden
-  end
-end

config/constants/settings/definitions.rb

@@ -96,7 +96,7 @@ Settings::Definition.define do
       writable: false
 
   add :auth_source_sso,
-      format: :string,
+      format: :hash,
       value: nil,
       writable: false
 

config/locales/crowdin/js-af.yml

@@ -289,11 +289,11 @@ af:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "Activate"
@@ -1149,7 +1149,7 @@ af:
       role:
         label: 'Role in %{project}'
         no_roles_found: 'No roles were found'
-        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Please select a role'
         next_button: 'Volgende'
       message:

config/locales/crowdin/js-ar.yml

@@ -289,11 +289,11 @@ ar:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "تفعيل"
@@ -1161,7 +1161,7 @@ ar:
       role:
         label: 'Role in %{project}'
         no_roles_found: 'No roles were found'
-        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Please select a role'
         next_button: 'التالي'
       message:

config/locales/crowdin/js-az.yml

@@ -86,7 +86,7 @@ az:
     button_save: "Save"
     button_settings: "Settings"
     button_uncheck_all: "Uncheck all"
-    button_update: "Update"
+    button_update: "Yeniləmə"
     button_export-pdf: "Download PDF"
     button_export-atom: "Download Atom"
     button_create: "Create"
@@ -289,11 +289,11 @@ az:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "Activate"
@@ -1149,7 +1149,7 @@ az:
       role:
         label: 'Role in %{project}'
         no_roles_found: 'No roles were found'
-        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Please select a role'
         next_button: 'Next'
       message:

config/locales/crowdin/js-bg.yml

@@ -289,11 +289,11 @@ bg:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "Activate"
@@ -1149,7 +1149,7 @@ bg:
       role:
         label: 'Role in %{project}'
         no_roles_found: 'No roles were found'
-        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Please select a role'
         next_button: 'Следващо'
       message:

config/locales/crowdin/js-ca.yml

@@ -289,11 +289,11 @@ ca:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "Activar"
@@ -1149,7 +1149,7 @@ ca:
       role:
         label: 'Role in %{project}'
         no_roles_found: 'No roles were found'
-        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Please select a role'
         next_button: 'Següent'
       message:

config/locales/crowdin/js-cs.yml

@@ -289,11 +289,11 @@ cs:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/blog/openproject-12-0-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/blog/openproject-12-0-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "Aktivovat"
@@ -1155,7 +1155,7 @@ cs:
       role:
         label: 'Role v %{project}'
         no_roles_found: 'Nebyly nalezeny žádné role.'
-        description: 'Toto je role, kterou %{principal} obdrží, když se připojí k vašemu projektu. Úloha vymezuje, která opatření mohou přijmout a jaké informace mohou vidět. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Další informace o rolích a oprávněních. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Vyberte prosím roli'
         next_button: 'Další'
       message:

config/locales/crowdin/js-da.yml

@@ -288,11 +288,11 @@ da:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "Aktivér"
@@ -1148,7 +1148,7 @@ da:
       role:
         label: 'Rolle i %{project}'
         no_roles_found: 'No roles were found'
-        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Vælg venligst en rolle'
         next_button: 'Næste'
       message:

config/locales/crowdin/js-de.yml

@@ -288,11 +288,11 @@ de:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 Das Release enthält zahlreiche neue Funktionen und Verbesserungen: <br> <ul class="%{list_styling_class}"> <li>Ein <b>neues Teamplanermodul</b> (Enterprise-Funktion) ermöglicht es Ihnen, Aufgaben den Teammitgliedern visuell zuzuweisen, um einen Überblick darüber zu bekommen, wer an was arbeitet.</li> <li>Die  <b>einfachen agilen Boards</b> werden für die Community Version freigegeben.</li> <li>Der <b>Filter "Projekte einbeziehen"</b> erleichtert das Hinzufügen verschiedener Projekte zu Ihren Ansichten, z.B. für Arbeitspakete, Kalender und Teamplaner.</li> <li>Arbeitspakete haben einen <b>neuen Reiter "Dateien"</b> um alle verfügbaren Arbeitspaket-Informationen gemeinsam darzustellen.</li> <li>Es gibt nun <b>globale Rollen für Gruppen</b> um Gruppen Rollen zuzuweisen und Superuser-Gruppen zu erstellen.</li> <li>Der Projektstatus wird ergänzt um weitere Optionen.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 Das Release enthält zahlreiche neue Funktionen und Verbesserungen: <br> <ul class="%{list_styling_class}"> <li>Im BCF-Modul können Sie nun die ausgewählten Arbeitspaket-Filter, -Spalten usw. als <b>Ansichten</b> speichern und diese mit Ihren Teammitgliedern teilen.</li> <li>Ein <b>neues Teamplanermodul</b> (Enterprise-Funktion) ermöglicht es Ihnen, Aufgaben den Teammitgliedern visuell zuzuweisen, um einen Überblick darüber zu bekommen, wer an was arbeitet.</li> <li>Die  <b>einfachen agilen Boards</b> werden für die Community Version freigegeben.</li> <li>Der <b>Filter "Projekte einbeziehen"</b> erleichtert das Hinzufügen verschiedener Projekte zu Ihren Ansichten, z.B. für Arbeitspakete, Kalender und Teamplaner.</li> <li>Arbeitspakete haben einen <b>neuen Reiter "Dateien"</b> um alle verfügbaren Arbeitspaket-Informationen gemeinsam darzustellen.</li> <li>Es gibt nun <b>globale Rollen für Gruppen</b> um Gruppen Rollen zuzuweisen und Superuser-Gruppen zu erstellen.</li> <li>Der Projektstatus wird ergänzt um weitere Optionen.</li> </ul>
     label_activate: "Aktiviere"
@@ -499,7 +499,7 @@ de:
           task_board: "Das Aufgabenfeld visualisiert den <b>Fortschritt für diesen Sprint</b>. Klicken Sie auf das Plus (+) Symbol neben einer User Story, um neue Aufgaben oder Hindernisse hinzuzufügen. <br> Der Status kann per Drag & Drop aktualisiert werden."
         boards:
           overview: 'Wählen Sie <b>Boards</b> aus, um eine andere Sicht auf Ihr Projekt zu erhalten und es in der agilen Board-Ansicht zu verwalten.'
-          lists_kanban: 'Hier können Sie mehrere Listen (Spalten) innerhalb Ihres Boards erstellen. Mit dieser Funktion können Sie zum Beispiel ein <b>Kanban Board</b>erstellen.'
+          lists_kanban: 'Hier können Sie mehrere Listen (Spalten) innerhalb Ihres Boards erstellen. Mit dieser Funktion können Sie zum Beispiel ein <b>Kanban Board</b> erstellen.'
           lists_basic: 'Hier können Sie mehrere Listen (Spalten) innerhalb Ihres agilen Boards erstellen.'
           add: 'Klicken Sie auf das Plus-Symbol (+), um <b>eine neue Karte zu erstellen</b> oder <b>eine existierende Karte</b> zur Liste auf dem Board hinzuzufügen.'
           drag: 'Verschieben Sie die Karten innerhalb einer Liste, um sie neu zu ordnen oder in eine andere Liste zu verschieben. <br> Sie können das Info (i) Symbol in der oberen rechten Ecke anklicken oder doppelt auf eine Karte klicken, um dessen Details zu öffnen.'
@@ -1148,7 +1148,7 @@ de:
       role:
         label: 'Rolle in %{project}'
         no_roles_found: 'Keine Rollen gefunden'
-        description: 'Dies ist die Rolle, die %{principal} erhalten wird, wenn sie Ihrem Projekt beitreten. Die Rolle legt fest, welche Maßnahmen sie ergreifen dürfen und welche Informationen ihnen erlaubt sind. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Erfahren Sie mehr über Rollen und Berechtigungen. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Bitte eine Rolle auswählen'
         next_button: 'Weiter'
       message:

config/locales/crowdin/js-el.yml

@@ -288,11 +288,11 @@ el:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "Ενεργοποίηση"
@@ -1148,7 +1148,7 @@ el:
       role:
         label: 'Ρόλος στο %{project}'
         no_roles_found: 'Δεν βρέθηκε κανένας ρόλος'
-        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Παρακαλούμε επιλέξτε ένα ρόλο'
         next_button: 'Επόμενο'
       message:

config/locales/crowdin/js-eo.yml

@@ -289,11 +289,11 @@ eo:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "Activate"
@@ -1149,7 +1149,7 @@ eo:
       role:
         label: 'Role in %{project}'
         no_roles_found: 'No roles were found'
-        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Please select a role'
         next_button: 'Sekva'
       message:

config/locales/crowdin/js-es.yml

@@ -289,11 +289,11 @@ es:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 La versión contiene nuevas mejoras y características: <br> <ul class="%{list_styling_class}"> <li>El <b>nuevo módulo Planificador de equipo</b> (característica de la versión Enterprise) permite asignar tareas visualmente a los miembros del equipo y ver un resumen del trabajo de cada uno.</li> <li>Estamos <b>publicando paneles ágiles básicos</b> para la versión de la comunidad.</li> <li>El <b>filtro «Incluir proyectos»</b> permite añadir fácilmente varios proyectos a las vistas (por ejemplo, para paquetes de trabajo, calendarios y planificadores de equipo).</li> <li>Hemos añadido <b>una nueva pestaña «Archivos»</b> en los detalles del paquete de trabajo para adjuntar toda la información posible a un paquete de trabajo.</li> <li>Hemos creado <b>roles globales para grupos</b>, que pueden asignarse a grupos y crear grupos de superusuarios.</li> <li>Se han añadido opciones de estado del proyecto.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 La versión contiene nuevas mejoras y características: <br> <ul class="%{list_styling_class}"> <li>En el módulo BCF, ahora puede guardar como <b>vistas</b> los filtros de paquetes de trabajo seleccionados, las columnas, etc., y compartirlas con los miembros del equipo.</li> <li>El <b>nuevo módulo Planificador de equipo</b> (característica de la versión Enterprise) permite asignar tareas visualmente a los miembros del equipo y ver un resumen de las tareas en las que trabaja cada uno.</li> <li>Estamos <b>publicando paneles ágiles básicos</b> para la versión de la comunidad.</li> <li>El <b>filtro «Incluir proyectos»</b> permite añadir fácilmente varios proyectos a las vistas (por ejemplo, para paquetes de trabajo, calendarios y planificadores de equipo).</li> <li>Hemos añadido <b>una nueva pestaña «Archivos»</b> en los detalles del paquete de trabajo para adjuntar toda la información posible a un paquete de trabajo.</li> <li>Hemos creado <b>roles globales para grupos</b> que pueden asignarse a grupos y crear grupos de superusuarios.</li> <li>Se han añadido opciones de estado del proyecto.</li> </ul>
     label_activate: "Activar"
@@ -1149,7 +1149,7 @@ es:
       role:
         label: 'Rol en %{project}'
         no_roles_found: 'No se encontraron roles'
-        description: 'Este es el rol que %{principal} recibirá al unirse al proyecto. El rol define las acciones que pueden realizar y la información que pueden ver. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Obtenga más información sobre roles y permisos. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Seleccione un rol'
         next_button: 'Siguiente'
       message:

config/locales/crowdin/js-et.yml

@@ -289,11 +289,11 @@ et:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "Aktiveerimine"
@@ -1149,7 +1149,7 @@ et:
       role:
         label: 'Role in %{project}'
         no_roles_found: 'No roles were found'
-        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Please select a role'
         next_button: 'Järgmine'
       message:

config/locales/crowdin/js-fa.yml

@@ -289,11 +289,11 @@ fa:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "Activate"
@@ -1149,7 +1149,7 @@ fa:
       role:
         label: 'Role in %{project}'
         no_roles_found: 'No roles were found'
-        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Please select a role'
         next_button: 'Next'
       message:

config/locales/crowdin/js-fi.yml

@@ -289,11 +289,11 @@ fi:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "Aktivoi"
@@ -1149,7 +1149,7 @@ fi:
       role:
         label: 'Role in %{project}'
         no_roles_found: 'No roles were found'
-        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Please select a role'
         next_button: 'Seuraava'
       message:

config/locales/crowdin/js-fil.yml

@@ -289,11 +289,11 @@ fil:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "Aktibo"
@@ -1149,7 +1149,7 @@ fil:
       role:
         label: 'Role in %{project}'
         no_roles_found: 'No roles were found'
-        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Please select a role'
         next_button: 'Susunod'
       message:

config/locales/crowdin/js-fr.yml

@@ -289,11 +289,11 @@ fr:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 Cette version contient diverses nouvelles fonctionnalités et améliorations : <br> <ul class="%{list_styling_class}"> <li>Un <b>nouveau module de planification d'équipe</b> (fonctionnalité Entreprise) vous permet d'attribuer visuellement des tâches aux membres de l'équipe pour avoir un aperçu de qui travaille sur quoi.</li> <li>Nous sommes <b>en train de libérer les tableaux agiles de base</b> pour la version Community. </li> <li>L'option de filtre <b>« Inclure les projets »</b> facilite l'ajout de différents projets à vos vues, comme pour les lots de travail, les calendriers et les planificateurs d'équipe.</li> <li>Nous avons ajouté <b>un nouvel onglet « Fichiers »</b> dans les détails du lot de travail pour avoir toutes les informations possibles attachées à un lot de travail ensemble. </li> <li>Nous avons créé des <b>rôles globaux pour les groupes</b> afin d'attribuer ces rôles aux groupes et de créer des groupes de super-utilisateurs.</li> <li>Le statut du projet a reçu plus d'options parmi lesquelles choisir.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 Cette version contient diverses nouvelles fonctionnalités et améliorations : <br> <ul class="%{list_styling_class}"> <li>Dans le module BCF, vous pouvez désormais enregistrer vos filtres de paquets de travail sélectionnés, vos colonnes, etc. en tant que <b>vues</b> et les partager avec les membres de votre équipe. </li> <li>Un <b>nouveau module de planification d'équipe</b> (fonctionnalité Entreprise) vous permet d'attribuer visuellement des tâches aux membres de l'équipe pour avoir un aperçu de qui travaille sur quoi.</li> <li>Nous sommes <b>en train de libérer les tableaux agiles de base</b> pour la version Community. </li> <li>L'option de filtre <b>« Inclure les projets »</b> facilite l'ajout de différents projets à vos vues, comme pour les lots de travail, les calendriers et les planificateurs d'équipe.</li> <li>Nous avons ajouté <b>un nouvel onglet « Fichiers »</b> dans les détails du lot de travail pour avoir toutes les informations possibles attachées à un lot de travail ensemble. </li> <li>Nous avons créé des <b>rôles globaux pour les groupes</b> afin d'attribuer ces rôles aux groupes et de créer des groupes de super-utilisateurs.</li> <li>Le statut du projet a reçu plus d'options parmi lesquelles choisir.</li> </ul>
     label_activate: "Activer"
@@ -1149,7 +1149,7 @@ fr:
       role:
         label: 'Rôle dans %{project}'
         no_roles_found: 'Aucun rôle trouvé.'
-        description: 'C''est le rôle que %{principal} recevra quand il rejoindra votre projet. Le rôle définit quelles actions il est autorisé à entreprendre et quelles informations il peut voir. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> En savoir plus sur les rôles et les permissions. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Veuillez sélectionner un rôle'
         next_button: 'Suivante'
       message:

config/locales/crowdin/js-he.yml

@@ -289,11 +289,11 @@ he:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "הפעל"
@@ -1155,7 +1155,7 @@ he:
       role:
         label: 'Role in %{project}'
         no_roles_found: 'No roles were found'
-        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Please select a role'
         next_button: 'הבא'
       message:

config/locales/crowdin/js-hi.yml

@@ -289,11 +289,11 @@ hi:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "Activate"
@@ -1149,7 +1149,7 @@ hi:
       role:
         label: 'Role in %{project}'
         no_roles_found: 'No roles were found'
-        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Please select a role'
         next_button: 'Next'
       message:

config/locales/crowdin/js-hr.yml

@@ -289,11 +289,11 @@ hr:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "Aktiviraj"
@@ -1152,7 +1152,7 @@ hr:
       role:
         label: 'Role in %{project}'
         no_roles_found: 'No roles were found'
-        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Please select a role'
         next_button: 'Sljedeći'
       message:

config/locales/crowdin/js-hu.yml

@@ -292,11 +292,11 @@ hu:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "Aktivál"
@@ -1154,7 +1154,7 @@ hu:
       role:
         label: 'Szerepek a %{project}'
         no_roles_found: 'Nem található szerepkör.'
-        description: 'Ez az a szerepkör, amelyet %{principal} kap, amikor csatlakozik a projekthez. A szerepkör határozza meg, hogy milyen műveleteket végezhetnek, és milyen információkat láthatnak. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Tudjon meg többet a szerepekről és jogosultságokról. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Kérjük, válasszon szerepet'
         next_button: ' Következő'
       message:

config/locales/crowdin/js-id.yml

@@ -289,11 +289,11 @@ id:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "Aktifkan"
@@ -1146,7 +1146,7 @@ id:
       role:
         label: 'Role in %{project}'
         no_roles_found: 'No roles were found'
-        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Please select a role'
         next_button: 'Lanjut'
       message:

config/locales/crowdin/js-it.yml

@@ -289,12 +289,12 @@ it:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 Questa versione contiene varie nuove funzionalità e miglioramenti: <br> <ul class="%{list_styling_class}"> <li>Un <b>nuovo modulo di pianificazione del team</b> (funzione Enterprise) consente di assegnare visivamente le attività al team membri per avere una panoramica di chi sta lavorando a cosa.</li> <li>Stiamo <b>rilasciando le agile board di base</b> per la versione Community.</li> <li>L'<b>opzione di filtro "Includi progetti"</b> semplifica l'aggiunta di diversi progetti alle visualizzazioni, ad esempio per macro-attività, calendari e pianificatori di team.</li> <li>Abbiamo aggiunto <b>una nuova scheda "File"</b> nei dettagli delle macro-attività per avere tutte le informazioni possibili di una macro-attività in un unico punto.</li> <li>Abbiamo creato <b>ruoli globali per i gruppi</b> per assegnare questi ruoli ai gruppi e creare un gruppi di superutenti.</li> <li>È possibile scegliere lo stato del progetto tra più opzioni.</li> </ul>
 
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 Questa versione contiene varie nuove funzionalità e miglioramenti: <br> <ul class="%{list_styling_class}"> <li>Nel modulo BCF ora puoi salvare filtri, colonne e altri elementi selezionati delle macro-attività come <b>viste</b> e condividerli con i membri del tuo team.</li> <li>Un <b>nuovo modulo di pianificazione del team</b> (funzione Enterprise) consente di assegnare visivamente le attività al team membri per avere una panoramica di chi sta lavorando a cosa.</li> <li>Stiamo <b>rilasciando le agile board di base</b> per la versione Community.</li> <li>L'<b>opzione di filtro "Includi progetti"</b> semplifica l'aggiunta di diversi progetti alle visualizzazioni, ad esempio per macro-attività, calendari e pianificatori di team.</li> <li>Abbiamo aggiunto <b>una nuova scheda "File"</b> nei dettagli delle macro-attività per avere tutte le informazioni possibili di una macro-attività in un unico punto.</li> <li>Abbiamo creato <b>ruoli globali per i gruppi</b> per assegnare questi ruoli ai gruppi e creare un gruppi di superutenti.</li> <li>È possibile scegliere lo stato del progetto tra più opzioni.</li> </ul>
 
@@ -1151,7 +1151,7 @@ it:
       role:
         label: 'Ruolo in %{project}'
         no_roles_found: 'Nessun ruolo è stato trovato'
-        description: 'Questo è il ruolo che %{principal} riceverà una volta unitosi al progetto. Il ruolo definisce che azioni possono intraprendere e che informazioni possono vedere. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank">Scopri di più sui ruoli e sulle autorizzazioni. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Sei pregato di selezionare un ruolo'
         next_button: 'Prossimo'
       message:

config/locales/crowdin/js-ja.yml

@@ -290,11 +290,11 @@ ja:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "有効にする"
@@ -1149,7 +1149,7 @@ ja:
       role:
         label: '%{project} でのロール'
         no_roles_found: 'ロールが見つかりません'
-        description: 'これは、 %{principal} がプロジェクトに参加したときに受け取るロールです。ロールは、実行できるアクションと表示できる情報を定義します。 <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank">ロールと権限の詳細はこちら。</a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'ロールを選択してください'
         next_button: '次へ'
       message:

config/locales/crowdin/js-ko.yml

@@ -289,11 +289,11 @@ ko:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 이 릴리스에는 다양한 새로운 기능과 개선 사항이 포함되어 있습니다: <br> <ul class="%{list_styling_class}"> <li><b>새로운 팀 플래너 모듈</b>(Enterprise 기능)을 사용하면 시각적으로 팀원에게 작업을 할당하여 누가 어떤 작업을 하는지에 대한 개요를 확인할 수 있습니다.</li> <li>커뮤니티 버전용 <b>기본 애자일 보드가 출시</b>됩니다.</li> <li><b>"프로젝트 포함" 필터</b> 옵션을 사용하면 작업 패키지, 달력 및 팀 플래너 등 다양한 프로젝트를 보기에 더욱 쉽게 추가할 수 있습니다.</li> <li>작업 패키지 세부 정보에 <b>새로운 "파일" 탭</b>이 추가되어 작업 패키지에 가능한 모든 정보를 함께 첨부할 수 있습니다.</li> <li><b>그룹에 대한 글로벌 역할</b>이 생성되어 이 역할을 그룹에 할당하고 수퍼유저 그룹을 생성할 수 있습니다.</li> <li>프로젝트 상태에 선택할 수 있는 더 많은 옵션이 제공됩니다.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 이 릴리스에는 다양한 새로운 기능과 개선 사항이 포함되어 있습니다: <br> <ul class="%{list_styling_class}"> <li>이제 BCF 모듈에서는 선택한 작업 패키지 필터, 열 등을 <b>보기</b>로 저장하고 팀원과 공유할 수 있습니다.</li> <li><b>새로운 팀 플래너 모듈</b>(Enterprise 기능)을 사용하면 시각적으로 팀원에게 작업을 할당하여 누가 어떤 작업을 하는지에 대한 개요를 확인할 수 있습니다.</li> <li>커뮤니티 버전용 <b>기본 애자일 보드가 출시</b>됩니다.</li> <li><b>"프로젝트 포함" 필터</b> 옵션을 사용하면 작업 패키지, 달력 및 팀 플래너 등 다양한 프로젝트를 보기에 더욱 쉽게 추가할 수 있습니다.</li> <li>작업 패키지 세부 정보에 <b>새로운 "파일" 탭</b>이 추가되어 작업 패키지에 가능한 모든 정보를 함께 첨부할 수 있습니다.</li> <li><b>그룹에 대한 글로벌 역할</b>이 생성되어 이 역할을 그룹에 할당하고 수퍼유저 그룹을 생성할 수 있습니다.</li> <li>프로젝트 상태에 선택할 수 있는 더 많은 옵션이 제공됩니다.</li> </ul>
     label_activate: "활성화"
@@ -1146,7 +1146,7 @@ ko:
       role:
         label: '%{project} 내 역할'
         no_roles_found: '역할이 없습니다'
-        description: '%{principal}이(가) 프로젝트에 참여할 때 받게 되는 역할입니다. 역할은 수행할 수 있는 작업과 볼 수 있는 정보를 지정합니다. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank">역할과 권한에 대해 더 알아보기</a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: '역할을 선택하십시오'
         next_button: '다음'
       message:

config/locales/crowdin/js-lol.yml

@@ -288,11 +288,11 @@ lol:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: crwdns808272:0crwdne808272:0
+              learn_about_link: crwdns813928:0crwdne813928:0
               new_features_html: >
                 crwdns808274:0%{list_styling_class}crwdne808274:0
             bim:
-              learn_about_link: crwdns808276:0crwdne808276:0
+              learn_about_link: crwdns813930:0crwdne813930:0
               new_features_html: >
                 crwdns808278:0%{list_styling_class}crwdne808278:0
     label_activate: "crwdns787268:0crwdne787268:0"
@@ -1148,7 +1148,7 @@ lol:
       role:
         label: 'crwdns788708:0%{project}crwdne788708:0'
         no_roles_found: 'crwdns788710:0crwdne788710:0'
-        description: 'crwdns788712:0%{principal}crwdne788712:0'
+        description: 'crwdns810810:0%{principal}crwdne810810:0'
         required: 'crwdns788714:0crwdne788714:0'
         next_button: 'crwdns788716:0crwdne788716:0'
       message:

config/locales/crowdin/js-lt.yml

@@ -238,7 +238,7 @@ lt:
           text: >
             OpenProject Enterprise Edition yra pastatyta virš Community Edition. Papildomai įdėtos „premium“ savybės ir profesionalus aptarnavimas, pagrinde orientuotas į organizacijas su daugiau nei 10 vartotojų, kurie naudodami OpenProject valdo verslui kritinius projektus.
           unlimited: "Neribota"
-          you_contribute: "Developers need to pay their bills, too. By upgrading to the Enterprise Edition, you will be supporting this open source community effort and contributing to its development, maintenance and continuous improvement."
+          you_contribute: "Vystotojams taip pat reikia apmokėti sąskaitas. Pereidami į „Enterprise Edition“, jūs paremsite šį atviro kodo bendruomenės projektą ir prisidėsite prie jo vystymo, palaikymo ir pastovaus tobulinimo."
     custom_actions:
       date:
         specific: 'įjungta'
@@ -289,15 +289,15 @@ lt:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 Laidoje yra kelios naujos savybės ir patobulinimai: <br> <ul class="%{list_styling_class}"> <li><b>Komandos plano modulis</b> (Enterprise savybė) leidžia jums vizualiai priskirti užduotis komandos nariams, gauti apžvalgą kas ką daro.</li> <li>Mes <b>išleidžiame bazines agile lentas</b> bendruomenės versijai.</li> <li><b>Filtras „Įtraukti projektus“</b> palengvina pridėti skirtingus projektus į jūsų vaizdus, tokius kaip darbų paketai, kalendoriai ar komandų planai.</li> <li>Mes darbo paketų detalėse pridėjom <b>naują kortelę „Failai“</b>, kurioje bus visa įmanoma informacija apie prie darbo paketo prisegtą informaciją.</li> <li>Mes sukūrėme <b>grupėms globalius vaidmenis</b>, kuriuos galima priskirti grupėms ir sukurti supernaudotojų grupes.</li> <li>Projekto būseną dabar galima nustatyti iš platesnio reikšmių pasirinkimo.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 Laidoje yra kelios naujos savybės ir patobulinimai: <br> <ul class="%{list_styling_class}"> <li>BCF modulyje jūs dabar galite įrašyti savo parinktus darbų paketų filtrus, stulpelius ir pan. kaip <b>vaizdus</b> ir dalintis jais su savo komandos nariais.</li> <li><b>Komandos plano modulis</b> (Enterprise savybė) leidžia jums vizualiai priskirti užduotis komandos nariams, gauti apžvalgą kas ką daro.</li> <li>Mes <b>išleidžiame bazines agile lentas</b> bendruomenės versijai.</li> <li><b>Filtras „Įtraukti projektus“</b> palengvina pridėti skirtingus projektus į jūsų vaizdus, tokius kaip darbų paketai, kalendoriai ar komandų planai.</li> <li>Mes darbo paketų detalėse pridėjom <b>naują kortelę „Failai“</b>, kurioje bus visa įmanoma informacija apie prie darbo paketo prisegtą informaciją.</li> <li>Mes sukūrėme <b>grupėms globalius vaidmenis</b>, kuriuos galima priskirti grupėms ir sukurti supernaudotojų grupes.</li> <li>Projekto būseną dabar galima nustatyti iš platesnio reikšmių pasirinkimo.</li> </ul>
     label_activate: "Aktyvuoti"
-    label_assignee: 'Assignee'
+    label_assignee: 'Paskirtas'
     label_add_column_after: "Pridėti stulpelį po"
     label_add_column_before: "Pridėti stulpelį prieš"
     label_add_columns: "Pridėti stulpelių"
@@ -1155,7 +1155,7 @@ lt:
       role:
         label: 'Vaidmuo projekte %{project}'
         no_roles_found: 'Nerasta jokių vaidmenų'
-        description: 'Tai yra vaidmuo, kurį %{principal} gaus, kai prisijungs prie projekto. Šis vaidmuo nurodo, kokius veiksmus galės atlikti ir kokią informaciją matyti. <a href="<a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank">" target="_blank">Sužinokite daugiau apie vaidmenis ir teises. </a>'
+        description: 'Tai yra vaidmuo, kurį %{principal} gaus, kai prisijungs prie jūsų projekto. Vaidmuo nurodo, kokius veiksmus leidžiama atlikti ir kokią informaciją galima matyti. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Sužinokite daugiau apie vaidmenis ir teises. </a>'
         required: 'Prašome parinkti vaidmenį'
         next_button: 'Kitas'
       message:

config/locales/crowdin/js-lv.yml

@@ -289,11 +289,11 @@ lv:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "Activate"
@@ -1152,7 +1152,7 @@ lv:
       role:
         label: 'Role in %{project}'
         no_roles_found: 'No roles were found'
-        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Please select a role'
         next_button: 'Nākošā'
       message:

config/locales/crowdin/js-ne.yml

@@ -289,11 +289,11 @@ ne:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "Activate"
@@ -1149,7 +1149,7 @@ ne:
       role:
         label: 'Role in %{project}'
         no_roles_found: 'No roles were found'
-        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Please select a role'
         next_button: 'Next'
       message:

config/locales/crowdin/js-nl.yml

@@ -289,11 +289,11 @@ nl:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "Activeren"
@@ -1149,7 +1149,7 @@ nl:
       role:
         label: 'Role in %{project}'
         no_roles_found: 'No roles were found'
-        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Please select a role'
         next_button: 'Volgende'
       message:

config/locales/crowdin/js-no.yml

@@ -289,11 +289,11 @@
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "Aktiver"
@@ -1149,7 +1149,7 @@
       role:
         label: 'Role in %{project}'
         no_roles_found: 'No roles were found'
-        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Please select a role'
         next_button: 'Neste'
       message:

config/locales/crowdin/js-pl.yml

@@ -289,11 +289,11 @@ pl:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 Wersja zawiera różne nowe funkcje i ulepszenia: <br> <ul class="%{list_styling_class}"> <li> <b>nowy moduł Planista zespołu</b> (funkcja wersji Enterprise) umożliwia wizualne przypisywanie zadań członkom zespołu, co pozwala uzyskać informacje o tym, kto nad czym pracuje.</li> <li>Wydajemy <b>tablice zwinne</b> dla wersji społecznościowej.</li> <li>Filtr „<b>Uwzględnij projekty</b>” ułatwia dodawanie różnych projektów do widoków, takich jak pakiety robocze, kalendarze i planiści zespołu.</li> <li>Dodaliśmy <b>nową kartę „Pliki”</b> w szczegółach pakietu roboczego, aby dołączać wszystkie możliwe informacje do pakietu roboczego.</li> <li>Utworzyliśmy <b>globalne role dla grup</b>, które można przypisać do grup i utworzyć grupy superużytkowników.</li> <li>Status projektu otrzymał więcej opcji do wyboru.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 Wersja zawiera różne nowe funkcje i ulepszenia: <br> <ul class="%{list_styling_class}"> <li>W module BCF można teraz zapisywać wybrane filtry pakietów roboczych, kolumny itd. jako <b>widoki</b> i udostępniać je członkom swojego zespołu.</li> <li> <b>nowy moduł Planista zespołu</b> (funkcja wersji Enterprise) umożliwia wizualne przypisywanie zadań członkom zespołu, co pozwala uzyskać informacje o tym, kto nad czym pracuje.</li> <li>Wydajemy <b>tablice zwinne</b> dla wersji społecznościowej.</li> <li>Filtr „<b>Uwzględnij projekty</b>” ułatwia dodawanie różnych projektów do widoków, takich jak pakiety robocze, kalendarze i planiści zespołu.</li> <li>Dodaliśmy <b>nową kartę „Pliki”</b> w szczegółach pakietu roboczego, aby dołączać wszystkie możliwe informacje do pakietu roboczego.</li> <li>Utworzyliśmy <b>globalne role dla grup</b>, które można przypisać do grup i utworzyć grupy superużytkowników.</li> <li>Status projektu otrzymał więcej opcji do wyboru.</li> </ul>
     label_activate: "Aktywuj"
@@ -1155,7 +1155,7 @@ pl:
       role:
         label: 'Rola w %{project}'
         no_roles_found: 'Nie znaleziono żadnych ról'
-        description: 'To jest rola, którą %{principal} otrzyma po dołączeniu do projektu. Rola określa działania, które można podjąć i widoczne informacje. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Dowiedz się więcej o rolach i uprawnieniach. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Wybierz rolę'
         next_button: 'Następny'
       message:

config/locales/crowdin/js-pt.yml

@@ -288,11 +288,11 @@ pt:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 A versão contém vários novos recursos e melhorias: <br> <ul class="%{list_styling_class}"> <li>Um <b>novo módulo de planejamento de equipe</b> (recurso Enterprise) permite atribuir tarefas visualmente a membros da equipe obtendo uma visão geral de quem está trabalhando e onde.</li> <li>Estamos <b>lançando os quadros ágeis básicos</b> para a versão da comunidade.</li> <li>A opção de <b>filtro "Incluir projetos"</b> facilita a adição de projetos diferentes às suas visualizações, como pacotes de trabalho, calendários e planejadores de equipe.</li> <li>Adicionamos <b>uma nova aba "Arquivos" </b> nos detalhes do pacote de trabalho para ter todas as informações possíveis anexadas a um pacote de trabalho juntas.</li> <li>Criamos <b>papéis globais para grupos</b> para atribuir esses papéis a grupos e criar grupos de superusuários.</li> <li>A situação do projeto recebeu mais opções de escolha.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 A versão contém vários novos recursos e melhorias: <br> <ul class="%{list_styling_class}"> <li>No módulo BCF, agora você pode salvar seus filtros, colunas, etc. do pacote de trabalho selecionado como <b>visualizações</b> e compartilhá-las com os membros de sua equipe.</li> <li>Um <b>novo módulo de planejamento de equipe</b> (recurso Enterprise) permite atribuir tarefas visualmente aos membros da equipe para obter uma visão geral de quem está trabalhando sobre o quê.</li> <li>Estamos <b>lançando os quadros ágeis básicos</b> para a versão Community.</li> <li>A opção <b>"Incluir projetos"</b> facilita a adição de projetos diferentes às suas visualizações, como pacotes de trabalho, calendários e planejadores de equipe.</li> <li>Adicionamos <b>uma nova aba "Arquivos"</b> nos detalhes do pacote de trabalho para ter todas as informações possíveis anexadas a um pacote de trabalho juntas.</li> <li>Criamos <b>papéis globais para grupos</b> para atribuir esses papéis a grupos e criar grupos de superusuários.</li> <li>A situação do projeto recebeu mais opções para escolher.</li> </ul>
     label_activate: "Ativar"
@@ -1148,7 +1148,7 @@ pt:
       role:
         label: 'Papel em %{project}'
         no_roles_found: 'Nenhum papel encontrado'
-        description: 'Este é um papel que %{principal} receberá quando se juntar ao projeto. O papel define que ações ela pode realizar e que informações pode visualizar. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Aprenda mais sobre papéis e permissões. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Selecione um papel'
         next_button: 'Próxima'
       message:

config/locales/crowdin/js-ro.yml

@@ -288,11 +288,11 @@ ro:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "Activare"
@@ -1151,7 +1151,7 @@ ro:
       role:
         label: 'Rolul în %{project}'
         no_roles_found: 'No roles were found'
-        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Vă rugăm să selectați un rol'
         next_button: 'Înainte'
       message:

config/locales/crowdin/js-ru.yml

@@ -288,11 +288,11 @@ ru:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 Релиз содержит различные новые функции и улучшения: <br> <ul class="%{list_styling_class}"> <li>В модуле BCF вы можете сохранить выбранные фильтры рабочих пакетов, колонки и т. д. как <b>просмотров</b> и поделиться ими с членами вашей команды.</li> <li>Новый <b>модуль командного планировщика</b> (Enterprise feature) позволяет наглядно назначить задачи членам команды, чтобы получить представление о том, кто над чем работает.</li> <li>Мы <b>выпустили базовые agile-доски</b> для версии Сообщества.</li> <li>Фильтр <b>"Включить проекты"</b> позволяет легко добавлять различные проекты к вашим представлениям, Например, для пакетов работ, календарей и командных планировщиков.</li> <li>Мы добавили <b>новую вкладку "Файлы"</b> в деталях пакета работ для получения всей возможной информации вместе с пакетом работ.</li> <li>Мы создали <b>глобальные роли для групп</b> для назначения этих ролей группам и создания групп суперпользователей.</li> <li>Статус проекта предоставляет больше вариантов выбора.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 Релиз содержит различные новые функции и улучшения: <br> <ul class="%{list_styling_class}"> <li>В модуле BCF вы можете сохранить выбранные фильтры рабочих пакетов, колонки и т. д. как <b>просмотров</b> и поделиться ими с членами вашей команды.</li> <li>Новый <b>модуль командного планировщика</b> (Enterprise feature) позволяет наглядно назначить задачи членам команды, чтобы получить представление о том, кто над чем работает.</li> <li>Мы <b>выпустили базовые agile-доски</b> для версии Сообщества.</li> <li>Фильтр <b>"Включить проекты"</b> позволяет легко добавлять различные проекты к вашим представлениям, Например, для пакетов работ, календарей и командных планировщиков.</li> <li>Мы добавили <b>новую вкладку "Файлы"</b> в деталях пакета работ для получения всей возможной информации вместе с пакетом работ.</li> <li>Мы создали <b>глобальные роли для групп</b> для назначения этих ролей группам и создания групп суперпользователей.</li> <li>Статус проекта предоставляет больше вариантов выбора.</li> </ul>
     label_activate: "Активировать"
@@ -1154,7 +1154,7 @@ ru:
       role:
         label: 'Роль в %{project}'
         no_roles_found: 'Роли не найдены'
-        description: 'Эту роль %{principal} получит после присоединения к вашему проекту. Роль определяет, разрешаемые действия и доступ к просмотру информации участника проекта. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Узнайте больше о ролях и разрешениях. </a>'
+        description: 'Это роль, которую %{principal} получит когда он присоединится к вашему проекту. Роль определяет, какие действия ему разрешены и какую информацию он может видеть. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Узнайте больше о ролях и разрешениях. </a>'
         required: 'Пожалуйста, выберите роль'
         next_button: 'Следующие'
       message:

config/locales/crowdin/js-rw.yml

@@ -289,11 +289,11 @@ rw:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "Activate"
@@ -1149,7 +1149,7 @@ rw:
       role:
         label: 'Role in %{project}'
         no_roles_found: 'No roles were found'
-        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Please select a role'
         next_button: 'Next'
       message:

config/locales/crowdin/js-si.yml

@@ -289,11 +289,11 @@ si:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "සක්රිය කරන්න"
@@ -1149,7 +1149,7 @@ si:
       role:
         label: 'Role in %{project}'
         no_roles_found: 'No roles were found'
-        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Please select a role'
         next_button: 'ඊළඟ'
       message:

config/locales/crowdin/js-sk.yml

@@ -289,11 +289,11 @@ sk:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "Aktivovať"
@@ -1155,7 +1155,7 @@ sk:
       role:
         label: 'Role in %{project}'
         no_roles_found: 'No roles were found'
-        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Please select a role'
         next_button: 'Ďalšie'
       message:

config/locales/crowdin/js-sl.yml

@@ -288,11 +288,11 @@ sl:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "Aktiviraj"
@@ -1154,7 +1154,7 @@ sl:
       role:
         label: 'Vloge v %{project}'
         no_roles_found: 'No roles were found'
-        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Izberite vlogo'
         next_button: 'Naprej'
       message:

config/locales/crowdin/js-sv.yml

@@ -288,11 +288,11 @@ sv:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "Aktivera"
@@ -1148,7 +1148,7 @@ sv:
       role:
         label: 'Role in %{project}'
         no_roles_found: 'No roles were found'
-        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Please select a role'
         next_button: 'Nästa'
       message:

config/locales/crowdin/js-th.yml

@@ -289,11 +289,11 @@ th:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "เปิดใช้งาน"
@@ -1146,7 +1146,7 @@ th:
       role:
         label: 'บทบาทใน %{project}'
         no_roles_found: 'ไม่พบบทบาท'
-        description: 'นี่คือบทบาทที่ %{principal} จะได้รับเมื่อพวกเขาเข้าร่วมโครงการของคุณ บทบาทกำหนดการกระทำที่พวกเขาได้รับอนุญาตให้ทำและข้อมูลที่พวกเขาได้รับอนุญาตให้ดู <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> เรียนรู้เพิ่มเติมเกี่ยวกับบทบาทและการอนุญาต </a> '
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'กรุณาเลือกบทบาท'
         next_button: 'ถัดไป'
       message:

config/locales/crowdin/js-tr.yml

@@ -289,11 +289,11 @@ tr:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "Etkinleştir"
@@ -1149,7 +1149,7 @@ tr:
       role:
         label: 'rol %{project}'
         no_roles_found: 'Hiç rol bulunamadı.'
-        description: 'Bu, %{principal} projenize katıldığı zaman alacağı roldür. Bu rol hangi eylemleri gerçekleştirebileceklerini ve hangi bilgileri görebileceklerini belirler. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank">Roller ve izinler hakkında daha fazla bilgi edinin. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Lütfen bir rol seçin.'
         next_button: 'Sonraki'
       message:

config/locales/crowdin/js-uk.yml

@@ -289,11 +289,11 @@ uk:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 Випуск включає наведені нижче нові функції та поліпшення. <br> <ul class="%{list_styling_class}"> <li>З <b>новим модулем командного планувальника</b> (функція Enterprise) можна призначати завдання учасникам команди так, щоб бачити, хто над чим працює.</li> <li>Ми <b>випускаємо базові дошки Agile</b> для версії Community.</li> <li> <b>Фільтр «Включити проєкти»</b> спрощує додавання різних проєктів до представлень, наприклад пакетів робіт, календарів і командних планувальників.</li> <li>Ми додали <b>нову вкладку «Файли» в режимі перегляду докладних відомостей про пакет робіт, щоб уся інформація про нього була доступна на одному екрані.</li> <li>Ми створили <b>глобальні ролі для груп</b>, щоб призначати ці ролі групам і додавати групи суперкористувачів.</li> <li>Ми розширили вибір доступних варіантів статусу проєкту.
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 Випуск включає наведені нижче нові функції та поліпшення. <br> <ul class="%{list_styling_class}"> <li>У модулі BCF тепер можна зберігати для пакетів робіт вибрані фільтри, стовпці тощо як <b>представлення</b> та ділитися ними з учасниками своєї команди.</li> <li>З <b>новим модулем командного планувальника</b> (функція Enterprise) можна призначати завдання учасникам команди так, щоб бачити, хто над чим працює.</li> <li>Ми <b>випускаємо базові дошки Agile</b> для версії Community.</li> <li> <b>Фільтр «Включити проєкти»</b> спрощує додавання різних проєктів до представлень, наприклад пакетів робіт, календарів і командних планувальників.</li> <li>Ми додали <b>нову вкладку «Файли» в режимі перегляду докладних відомостей про пакет робіт, щоб уся інформація про нього була доступна на одному екрані.</li> <li>Ми створили <b>глобальні ролі для груп</b>, щоб призначати ці ролі групам і додавати групи суперкористувачів.</li> <li>Ми розширили вибір доступних варіантів статусу проєкту.
     label_activate: "Активувати"
@@ -1155,7 +1155,7 @@ uk:
       role:
         label: 'Ролі у проєкті «%{project}»'
         no_roles_found: 'Ролей не знайдено'
-        description: 'Це роль, яку користувач %{principal} отримає в разі приєднання до вашого проєкту. Роль визначає, які дії йому дозволено та яку інформацію він може бачити. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Дізнатися більше про ролі й дозволи. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Виберіть роль'
         next_button: 'Далі'
       message:

config/locales/crowdin/js-vi.yml

@@ -288,11 +288,11 @@ vi:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "Activate"
@@ -1145,7 +1145,7 @@ vi:
       role:
         label: 'Vai trò trong %{project}'
         no_roles_found: 'Không tìm thấy vai trò nào'
-        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Vui lòng chọn một vai trò'
         next_button: 'Tiếp'
       message:

config/locales/crowdin/js-zh-TW.yml

@@ -288,11 +288,11 @@ zh-TW:
           #Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br> <ul class="%{list_styling_class}"> <li>In the BCF module you can now save your selected work package filters, columns etc. as <b>views</b> and share those with your team members.</li> <li>A <b>new team planner module</b> (Enterprise feature) allows you to visually assign tasks to team members to get an overview of who is working on what.</li> <li>We are <b>releasing the basic agile boards</b> for the Community version.</li> <li>The <b>"Include Projects" filter</b> option makes it easier to add different projects to your views, such as for work packages, calendars, and team planners.</li> <li>We added <b>a new "Files" tab</b> in the work package details to have all possible information attached to a work package together.</li> <li>We created <b>global roles for groups</b> to assign these roles to groups and create superuser groups.</li> <li>Project status was given more options to choose from.</li> </ul>
     label_activate: "啟用"
@@ -1145,7 +1145,7 @@ zh-TW:
       role:
         label: 'Role in %{project}'
         no_roles_found: 'No roles were found'
-        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
+        description: 'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://www.openproject.org/docs/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
         required: 'Please select a role'
         next_button: '下一個'
       message:

config/locales/crowdin/lt.yml

@@ -2191,7 +2191,7 @@ lt:
   permission_comment_news: "Komentuoti naujienas"
   permission_commit_access: "Skaitymo/rašymo prieiga į repozitoriją"
   permission_copy_projects: "Kopijuoti projekus"
-  permission_create_backup: "Create backup"
+  permission_create_backup: "Kurti atsarginę kopiją"
   permission_delete_work_package_watchers: "Pašalinti stebėtojus"
   permission_delete_work_packages: "Pašalinti darbų paketus"
   permission_delete_messages: "Pašalinti pranešimus"
@@ -2284,7 +2284,7 @@ lt:
     assigned_to_role: "Priskirtojo asmens vaidmuo"
     member_of_group: "Priskirtojo asmens grupė"
     assignee_or_group: "Paskirtas ar priklausanti grupė"
-    subproject_id: "Including subproject"
+    subproject_id: "Įtraukti sub-projektus"
     only_subproject_id: "Tik sub-projektai"
     name_or_identifier: "Pavadinimas arba identifikatorius"
   repositories:

config/locales/js-en.yml

@@ -319,7 +319,7 @@ en:
           # Otherwise, e.g. chinese might still have the translations for 10.0 in the 12.0 release.
           '12_1':
             standard:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br>
                 <ul class="%{list_styling_class}">
@@ -331,7 +331,7 @@ en:
                   <li>Project status was given more options to choose from.</li>
                 </ul>
             bim:
-              learn_about_link: https://www.openproject.org/openproject-12-1-release
+              learn_about_link: https://www.openproject.org/blog/openproject-12-1-release
               new_features_html: >
                 The release contains various new features and improvements: <br>
                 <ul class="%{list_styling_class}">

docker/ci/Dockerfile

@@ -1,4 +1,4 @@
-FROM ruby:3.0.4-buster
+FROM ruby:3.1.2-buster
 MAINTAINER operations@openproject.com
 
 ENV NODE_VERSION="14.17.0"

docker/dev/backend/Dockerfile

@@ -1,4 +1,4 @@
-FROM ruby:3.0.4-bullseye as develop
+FROM ruby:3.1.2-bullseye as develop
 MAINTAINER operations@openproject.com
 
 ARG DEV_UID=1000
@@ -47,7 +47,7 @@ WORKDIR /home/$USER/openproject
 
 USER $USER
 
-RUN gem install bundler --version "${bundler_version}" --no-document
+RUN gem install bundler --version "${BUNDLER_VERSION}" --no-document
 
 ####### Testing image below #########
 

docker/prod/Dockerfile

@@ -1,4 +1,4 @@
-FROM ruby:3.0.4-buster
+FROM ruby:3.1.2-buster
 MAINTAINER operations@openproject.com
 
 # Allow platform-specific additions. Valid values are: on-prem,saas,bahn

docs/api/apiv3/components/schemas/user_collection_model.yml

@@ -0,0 +1,46 @@
+# Schema: UserCollectionModel
+---
+allOf:
+  - $ref: './collection_model.yml'
+  - type: object
+    required:
+      - _links
+      - _embedded
+    properties:
+      _links:
+        type: object
+        required:
+          - self
+        properties:
+          self:
+            allOf:
+              - $ref: "./link.yml"
+              - description: |-
+                  This user collection
+                  
+                  **Resource**: UserCollectionModel
+      _embedded:
+        type: object
+        required:
+          - elements
+        properties:
+          elements:
+            type: array
+            items:
+              $ref: './user_model.yml'
+
+example:
+  _type: Collection
+  total: 2
+  count: 2
+  _links:
+    self:
+      href: '/api/v3/users'
+  _embedded:
+    elements:
+      - _hint: User resource shortened for brevity
+        _type: User
+        id: 1337
+      - _hint: User resource shortened for brevity
+        _type: User
+        id: 1338

docs/api/apiv3/components/schemas/user_create_model.yml

@@ -0,0 +1,53 @@
+# Schema: UserCreateModel
+---
+type: object
+required:
+  - admin
+  - email
+  - login
+  - firstName
+  - lastName
+  - language
+properties:
+  admin:
+    type: boolean
+  email:
+    type: string
+    maxLength: 60
+  login:
+    type: string
+    maxLength: 256
+  password:
+    type: string
+    description: |-
+      The users password.
+
+      *Conditions:*
+
+      Only writable on creation, not on update.
+  firstName:
+    type: string
+    maxLength: 30
+  lastName:
+    type: string
+    maxLength: 30
+  status:
+    type: string
+    description: |-
+      The current activation status of the user.
+
+      *Conditions:*
+
+      Only writable on creation, not on update.
+  language:
+    type: string
+
+example:
+  login: j.sheppard
+  password: idestroyedsouvereign
+  firstName: John
+  lastName: Sheppard
+  email: shep@mail.com
+  admin: true
+  status: active
+  language: en

docs/api/apiv3/components/schemas/user_model.yml

@@ -1,42 +1,21 @@
 # Schema: UserModel
 ---
 type: object
-example:
-  _type: User
-  _links:
-    self:
-      href: "/api/v3/users/1"
-      title: j.sheppard
-    show:
-      href: "/users/1"
-      type: text/html
-    lock:
-      href: "/api/v3/users/1/lock"
-      method: POST
-    updateImmediately:
-      href: "/api/v3/users/1"
-      method: PATCH
-    delete:
-      href: "/api/v3/users/1"
-      method: DELETE
-  id: 1
-  login: j.sheppard
-  firstName: John
-  lastName: Sheppard
-  email: shep@mail.com
-  admin: true
-  avatar: https://example.org/users/1/avatar
-  status: active
-  language: en
-  createdAt: '2014-05-21T08:51:20Z'
-  updatedAt: '2014-05-21T08:51:20Z'
+required:
+  - _type
+  - id
+  - name
+  - avatar
+  - _links
 properties:
+  _type:
+    type: string
+    enum:
+      - User
   id:
     type: integer
     description: User's id
-    readOnly: true
     minimum: 0
-    exclusiveMinimum: true
   login:
     type: string
     description: |-
@@ -67,7 +46,6 @@ properties:
   name:
     type: string
     description: User's full name, formatting depends on instance settings
-    readOnly: true
   email:
     type: string
     description: |-
@@ -89,11 +67,9 @@ properties:
     type: string
     format: uri
     description: URL to user's avatar
-    readOnly: true
   status:
     type: string
     description: The current activation status of the user (see below)
-    readOnly: true
   language:
     type: string
     description: |-
@@ -102,17 +78,9 @@ properties:
       # Conditions
 
       **Permission**: Administrator, manage_user global permission
-  password:
-    type: string
-    description: |-
-      User's password for the default password authentication
-
-      # Conditions
-
-      **Permission**: Administrator
-    writeOnly: true
-  identity_url:
+  identityUrl:
     type: string
+    nullable: true
     description: |-
       User's identity_url for OmniAuth authentication
 
@@ -123,90 +91,110 @@ properties:
     type: string
     format: date-time
     description: Time of creation
-    readOnly: true
   updatedAt:
     type: string
     format: date-time
     description: Time of the most recent change to the user
-    readOnly: true
   _links:
     type: object
     required:
-    - self
+      - self
+      - memberships
+      - showUser
     properties:
-      lock:
+      self:
         allOf:
-        - "$ref": "./link.yml"
-        - description: |-
-            Restrict the user from logging in and performing any actions
-
-            # Conditions
-
-            not locked; **Permission**: Administrator
-          readOnly: true
-      show:
+          - "$ref": "./link.yml"
+          - description: |-
+              This user
+              
+              **Resource**: User
+      memberships:
         allOf:
-        - "$ref": "./link.yml"
-        - description: Link to the OpenProject user page (HTML)
-          readOnly: true
-      unlock:
+          - "$ref": "./link.yml"
+          - description: |-
+              Link to collection of all the user's memberships. The list will only include the memberships in projects in which the requesting user has the necessary permissions.
+              
+              **Resource**: MemberCollection
+              
+              # Conditions
+              
+              **Permission**: view members or manage members in any project
+      showUser:
         allOf:
-        - "$ref": "./link.yml"
-        - description: |-
-            Allow a locked user to login and act again
-
-            # Conditions
-
-            locked; **Permission**: Administrator
-          readOnly: true
+          - "$ref": "./link.yml"
+          - description: Link to the OpenProject user page (HTML)
       updateImmediately:
         allOf:
-        - "$ref": "./link.yml"
-        - description: |-
-            Updates the user's attributes.
-
-            # Conditions
-
-            **Permission**: Administrator, manage_user global permission
-          readOnly: true
-      delete:
-        allOf:
-        - "$ref": "./link.yml"
-        - description: |-
-            Permanently remove a user from the instance
-
-            # Conditions
-
-            **Permission**: Administrator, self-delete
-          readOnly: true
-      self:
+          - "$ref": "./link.yml"
+          - description: |-
+              Updates the user's attributes.
+              
+              # Conditions
+              
+              **Permission**: Administrator, manage_user global permission
+      lock:
         allOf:
-        - "$ref": "./link.yml"
-        - description: |-
-            This user
-
-            **Resource**: User
-          readOnly: true
-      auth_source:
+          - "$ref": "./link.yml"
+          - description: |-
+              Restrict the user from logging in and performing any actions
+              
+              # Conditions
+              
+              not locked; **Permission**: Administrator
+      unlock:
         allOf:
-        - "$ref": "./link.yml"
-        - description: |-
-            Link to the user's auth source (endpoint not yet implemented)
-
-            **Resource**: AuthSource
-
-            # Conditions
-
-            **Permission**: Administrator
-      members:
+          - "$ref": "./link.yml"
+          - description: |-
+              Allow a locked user to login and act again
+              
+              # Conditions
+              
+              locked; **Permission**: Administrator
+      delete:
         allOf:
-        - "$ref": "./link.yml"
-        - description: |-
-            Link to collection of all the user's memberships. The list will only include the memberships in projects in which the requesting user has the necessary permissions.
+          - "$ref": "./link.yml"
+          - description: |-
+              Permanently remove a user from the instance
+              
+              # Conditions
+              
+              **Permission**: Administrator, self-delete
 
-            **Resource**: MemberCollection
-
-            # Conditions
-
-            **Permission**: view members or manage members in any project
-          readOnly: true
+example:
+  _type: User
+  id: 1
+  name: John Sheppard
+  login: j.sheppard
+  firstName: John
+  lastName: Sheppard
+  email: shep@mail.com
+  admin: true
+  avatar: https://example.org/users/1/avatar
+  status: active
+  identityUrl: null,
+  language: en
+  createdAt: '2014-05-21T08:51:20Z'
+  updatedAt: '2014-05-21T08:51:20Z'
+  _links:
+    self:
+      href: '/api/v3/users/1'
+      title: John Sheppard
+    memberships:
+      href: /api/v3/memberships?filters=%5B%7B%22principal%22%3A%7B%22operator%22%3A%22%3D%22%2C%22values%22%3A%5B%221%22%5D%7D%7D%5D,
+      title: Members
+    showUser:
+      href: '/users/1'
+      type: text/html
+    lock:
+      href: '/api/v3/users/1/lock'
+      title: Set lock on John Sheppard
+      method: post
+    updateImmediately:
+      href: '/api/v3/users/1'
+      title: update John Sheppard
+      method: patch
+    delete:
+      href: '/api/v3/users/1'
+      title: delete John Sheppard
+    method: delete

docs/api/apiv3/components/schemas/users_model.yml

@@ -1,43 +0,0 @@
-# Schema: UsersModel
----
-type: object
-example:
-  _links:
-    self:
-      href: "/api/v3/users"
-  total: 2
-  count: 1
-  _type: Collection
-  _embedded:
-    elements:
-    - _type: User
-      _links:
-        self:
-          href: "/api/v3/users/1"
-          title: John Sheppard - j.sheppard
-        showUser:
-          href: "/users/1"
-          type: text/html
-        lock:
-          href: "/api/v3/users/1/lock"
-          title: Set lock on j.sheppard
-          method: POST
-        update:
-          href: "/api/v3/users/1"
-          title: Update j.sheppard
-          method: PATCH
-        delete:
-          href: "/api/v3/users/1"
-          title: Delete j.sheppard
-          method: DELETE
-      id: 1
-      login: j.sheppard
-      firstName: John
-      lastName: Sheppard
-      email: shep@mail.com
-      admin: true
-      avatar: https://example.org/users/1/avatar
-      status: active
-      language: en
-      createdAt: '2014-05-21T08:51:20Z'
-      updatedAt: '2014-05-21T08:51:20Z'

docs/api/apiv3/openapi-spec.yml

@@ -64,7 +64,7 @@ info:
 
     ### API Key through Basic Auth
 
-    Users can authenticate towards the API v3 using basic auth with `apikey` (as a string, NOT your API key) as the user name and their API key as the password.
+    Users can authenticate towards the API v3 using basic auth with the user name `apikey` (NOT your login) and the API key as the password.
     Users can find their API key on their account page.
 
     Example:
@@ -408,6 +408,8 @@ paths:
     "$ref": "./paths/work_package_available_watchers.yml"
   "/api/v3/work_packages/{id}/file_links":
     "$ref": "./paths/work_package_file_links.yml"
+  "/api/v3/work_packages/{id}/update_file_links":
+    "$ref": "./paths/work_package_update_file_links.yml"
   "/api/v3/work_packages/{id}/form":
     "$ref": "./paths/work_package_form.yml"
   "/api/v3/work_packages/{id}/revisions":
@@ -701,6 +703,10 @@ components:
       "$ref": "./components/schemas/update_project.yml"
     Update_time_entry:
       "$ref": "./components/schemas/update_time_entry.yml"
+    UserCollectionModel:
+      "$ref": "./components/schemas/user_collection_model.yml"
+    UserCreateModel:
+      "$ref": "./components/schemas/user_create_model.yml"
     UserModel:
       "$ref": "./components/schemas/user_model.yml"
     UserPreferencesModel:
@@ -711,8 +717,6 @@ components:
       "$ref": "./components/schemas/user_create_form.yml"
     User_update_form:
       "$ref": "./components/schemas/user_update_form.yml"
-    UsersModel:
-      "$ref": "./components/schemas/users_model.yml"
     VersionModel:
       "$ref": "./components/schemas/version_model.yml"
     Version_create_form:

docs/api/apiv3/paths/user.yml

@@ -1,14 +1,19 @@
 # /api/v3/users/{id}
 ---
 delete:
+  summary: Delete user
+  operationId: delete_user
+  description: Permanently deletes the specified user account.
+  tags:
+    - Users
   parameters:
-  - description: User id
-    example: '1'
-    in: path
-    name: id
-    required: true
-    schema:
-      type: integer
+    - description: User id
+      example: '1'
+      in: path
+      name: id
+      required: true
+      schema:
+        type: integer
   responses:
     '202':
       description: |-
@@ -16,225 +21,145 @@ delete:
 
         Note that the response body is empty as of now. In future versions of the API a body
         *might* be returned, indicating the progress of deletion.
-      headers: {}
     '403':
       content:
         application/hal+json:
           schema:
-            $ref: "../components/schemas/error_response.yml"
-          examples:
-            response:
-              value:
-                _type: Error
-                errorIdentifier: urn:openproject-org:api:v3:errors:MissingPermission
-                message: You are not allowed to delete the account of this user.
+            $ref: '../components/schemas/error_response.yml'
+          example:
+            _type: Error
+            errorIdentifier: urn:openproject-org:api:v3:errors:MissingPermission
+            message: You are not allowed to delete the account of this user.
       description: |-
         Returned if the client does not have sufficient permissions or if deletion of users was disabled in the instance wide settings.
 
         **Required permission:** Administrators only (exception: users might be able to delete their own accounts)
-      headers: {}
     '404':
       content:
         application/hal+json:
           schema:
-            $ref: "../components/schemas/error_response.yml"
-          examples:
-            response:
-              value:
-                _type: Error
-                errorIdentifier: urn:openproject-org:api:v3:errors:NotFound
-                message: The specified user does not exist.
+            $ref: '../components/schemas/error_response.yml'
+          example:
+            _type: Error
+            errorIdentifier: urn:openproject-org:api:v3:errors:NotFound
+            message: The specified user does not exist.
       description: Returned if the user does not exist.
-      headers: {}
-  tags:
-  - Users
-  description: Permanently deletes the specified user account.
-  operationId: Delete_user
-  summary: Delete user
+
 get:
+  summary: View user
+  operationId: view_user
+  description: ''
+  tags:
+    - Users
   parameters:
-  - description: User id. Use `me` to reference current user, if any.
-    example: '1'
-    in: path
-    name: id
-    required: true
-    schema:
-      type: string
+    - description: User id. Use `me` to reference current user, if any.
+      example: '1'
+      in: path
+      name: id
+      required: true
+      schema:
+        type: string
   responses:
     '200':
       content:
         application/hal+json:
-          examples:
-            response:
-              value:
-                _links:
-                  delete:
-                    href: "/api/v3/users/1"
-                    method: DELETE
-                  lock:
-                    href: "/api/v3/users/1/lock"
-                    method: POST
-                  self:
-                    href: "/api/v3/users/1"
-                    title: j.sheppard
-                  show:
-                    href: "/users/1"
-                    type: text/html
-                  updateImmediately:
-                    href: "/api/v3/users/1"
-                    method: PATCH
-                _type: User
-                admin: true
-                avatar: https://example.org/users/1/avatar
-                createdAt: '2014-05-21T08:51:20Z'
-                email: shep@mail.com
-                firstName: John
-                id: 1
-                language: en
-                lastName: Sheppard
-                login: j.sheppard
-                status: active
-                updatedAt: '2014-05-21T08:51:20Z'
           schema:
-            "$ref": "../components/schemas/user_model.yml"
+            $ref: '../components/schemas/user_model.yml'
       description: OK
-      headers: {}
     '404':
       content:
         application/hal+json:
           schema:
-            $ref: "../components/schemas/error_response.yml"
-          examples:
-            response:
-              value:
-                _type: Error
-                errorIdentifier: urn:openproject-org:api:v3:errors:NotFound
-                message: The specified user does not exist or you do not have permission
-                  to view them.
+            $ref: '../components/schemas/error_response.yml'
+          example:
+            _type: Error
+            errorIdentifier: urn:openproject-org:api:v3:errors:NotFound
+            message: The specified user does not exist or you do not have permission to view them.
       description: |-
         Returned if the user does not exist or if the API user does not have permission to view them.
 
         **Required permission** The user needs to be locked in if the installation is configured to prevent anonymous access
-      headers: {}
-  tags:
-  - Users
-  description: ''
-  operationId: View_user
-  summary: View user
+
 patch:
+  summary: Update user
+  operationId: update_user
+  tags:
+    - Users
+  description: |-
+    Updates the user's writable attributes.
+    When calling this endpoint the client provides a single object, containing at least the properties and links that are required, in the body.
   parameters:
-  - description: User id
-    example: '1'
-    in: path
-    name: id
-    required: true
-    schema:
-      type: integer
+    - description: User id
+      example: '1'
+      in: path
+      name: id
+      required: true
+      schema:
+        type: integer
+  requestBody:
+    content:
+      application/json:
+        schema:
+          $ref: '../components/schemas/user_create_model.yml'
   responses:
     '200':
       content:
         application/hal+json:
           schema:
-            "$ref": "../components/schemas/user_model.yml"
+            $ref: '../components/schemas/user_model.yml'
       description: OK
-      headers: {}
     '400':
       content:
         application/hal+json:
           schema:
-            $ref: "../components/schemas/error_response.yml"
-          examples:
-            response:
-              value:
-                _type: Error
-                errorIdentifier: urn:openproject-org:api:v3:errors:InvalidRequestBody
-                message: The request body was not a single JSON object.
+            $ref: '../components/schemas/error_response.yml'
+          example:
+            _type: Error
+            errorIdentifier: urn:openproject-org:api:v3:errors:InvalidRequestBody
+            message: The request body was not a single JSON object.
       description: Occurs when the client did not send a valid JSON object in the
         request body.
-      headers: {}
     '403':
       content:
         application/hal+json:
           schema:
-            $ref: "../components/schemas/error_response.yml"
-          examples:
-            response:
-              value:
-                _type: Error
-                errorIdentifier: urn:openproject-org:api:v3:errors:MissingPermission
-                message: You are not allowed to update the account of this user.
+            $ref: '../components/schemas/error_response.yml'
+          example:
+            _type: Error
+            errorIdentifier: urn:openproject-org:api:v3:errors:MissingPermission
+            message: You are not allowed to update the account of this user.
       description: |-
         Returned if the client does not have sufficient permissions.
 
         **Required permission:** Administrators, manage_user global permission
-      headers: {}
     '404':
       content:
         application/hal+json:
           schema:
-            $ref: "../components/schemas/error_response.yml"
-          examples:
-            response:
-              value:
-                _type: Error
-                errorIdentifier: urn:openproject-org:api:v3:errors:NotFound
-                message: The specified user does not exist or you do not have permission
-                  to view them.
+            $ref: '../components/schemas/error_response.yml'
+          example:
+              _type: Error
+              errorIdentifier: urn:openproject-org:api:v3:errors:NotFound
+              message: The specified user does not exist or you do not have permission to view them.
       description: |-
         Returned if the user does not exist or if the API user does not have the necessary permissions to update it.
 
         **Required permission:** Administrators only (exception: users may update their own accounts)
-      headers: {}
     '422':
       content:
         application/hal+json:
           schema:
-            $ref: "../components/schemas/error_response.yml"
-          examples:
-            response:
-              value:
-                _embedded:
-                  details:
-                    attribute: email
-                _type: Error
-                errorIdentifier: urn:openproject-org:api:v3:errors:PropertyConstraintViolation
-                message: The email address is already taken.
+            $ref: '../components/schemas/error_response.yml'
+          example:
+            _embedded:
+              details:
+                attribute: email
+            _type: Error
+            errorIdentifier: urn:openproject-org:api:v3:errors:PropertyConstraintViolation
+            message: The email address is already taken.
       description: |-
         Returned if:
 
         * the client tries to modify a read-only property (`PropertyIsReadOnly`)
 
         * a constraint for a property was violated (`PropertyConstraintViolation`)
-      headers: {}
-  tags:
-  - Users
-  description: |-
-    Updates the user's writable attributes.
-    When calling this endpoint the client provides a single object, containing at least the properties and links that are required, in the body.
-  operationId: Update_user
-  requestBody:
-    content:
-      application/json:
-        schema:
-          example:
-            admin: true
-            email: h.wurst@openproject.com
-            firstName: Hans
-            language: en
-            lastName: Wurst
-            login: h.wurst
-          properties:
-            admin:
-              type: boolean
-            email:
-              type: string
-            firstName:
-              type: string
-            language:
-              type: string
-            lastName:
-              type: string
-            login:
-              type: string
-          type: object
-  summary: Update user

docs/api/apiv3/paths/user_lock.yml

@@ -1,198 +1,115 @@
 # /api/v3/users/{id}/lock
 ---
 delete:
+  summary: Unlock user
+  operationId: unlock_user
+  tags:
+    - Users
   parameters:
-  - description: User id
-    example: '1'
-    in: path
-    name: id
-    required: true
-    schema:
-      type: integer
+    - description: User id
+      example: '1'
+      in: path
+      name: id
+      required: true
+      schema:
+        type: integer
   responses:
     '200':
       content:
         application/hal+json:
-          examples:
-            response:
-              value:
-                _links:
-                  delete:
-                    href: "/api/v3/users/1"
-                    method: DELETE
-                  lock:
-                    href: "/api/v3/users/1/lock"
-                    method: POST
-                  self:
-                    href: "/api/v3/users/1"
-                    title: j.sheppard
-                  show:
-                    href: "/users/1"
-                    type: text/html
-                  updateImmediately:
-                    href: "/api/v3/users/1"
-                    method: PATCH
-                _type: User
-                admin: true
-                avatar: https://example.org/users/1/avatar
-                createdAt: '2014-05-21T08:51:20Z'
-                email: shep@mail.com
-                firstName: John
-                id: 1
-                language: en
-                lastName: Sheppard
-                login: j.sheppard
-                status: active
-                updatedAt: '2014-05-21T08:51:20Z'
           schema:
-            "$ref": "../components/schemas/user_model.yml"
+            $ref: '../components/schemas/user_model.yml'
       description: OK
-      headers: {}
     '400':
       content:
         application/hal+json:
           schema:
-            $ref: "../components/schemas/error_response.yml"
-          examples:
-            response:
-              value:
-                _type: Error
-                errorIdentifier: urn:openproject-org:api:v3:errors:InvalidUserStatusTransition
-                message: The current user account status does not allow this operation.
+            $ref: '../components/schemas/error_response.yml'
+          example:
+            _type: Error
+            errorIdentifier: urn:openproject-org:api:v3:errors:InvalidUserStatusTransition
+            message: The current user account status does not allow this operation.
       description: |-
         Returned if the client tries to unlock a user account whose current status does not allow this transition.
 
         **Required permission:** Administrators only
-      headers: {}
     '403':
       content:
         application/hal+json:
           schema:
-            $ref: "../components/schemas/error_response.yml"
-          examples:
-            response:
-              value:
-                _type: Error
-                errorIdentifier: urn:openproject-org:api:v3:errors:MissingPermission
-                message: You are not allowed to unlock the account of this user.
+            $ref: '../components/schemas/error_response.yml'
+          example:
+            _type: Error
+            errorIdentifier: urn:openproject-org:api:v3:errors:MissingPermission
+            message: You are not allowed to unlock the account of this user.
       description: |-
         Returned if the client does not have sufficient permissions for unlocking a user.
 
         **Required permission:** Administrators only
-      headers: {}
     '404':
       content:
         application/hal+json:
           schema:
             $ref: "../components/schemas/error_response.yml"
-          examples:
-            response:
-              value:
-                _type: Error
-                errorIdentifier: urn:openproject-org:api:v3:errors:NotFound
-                message: The specified user does not exist.
+          example:
+            _type: Error
+            errorIdentifier: urn:openproject-org:api:v3:errors:NotFound
+            message: The specified user does not exist.
       description: Returned if the user does not exist.
-      headers: {}
-  tags:
-  - Users
-  description: ''
-  operationId: Unlock_user
-  summary: Unlock user
+
 post:
+  summary: Lock user
+  operationId: lock_user
+  tags:
+    - Users
   parameters:
-  - description: User id
-    example: '1'
-    in: path
-    name: id
-    required: true
-    schema:
-      type: integer
+    - description: User id
+      example: '1'
+      in: path
+      name: id
+      required: true
+      schema:
+        type: integer
   responses:
     '200':
       content:
         application/hal+json:
-          examples:
-            response:
-              value:
-                _links:
-                  delete:
-                    href: "/api/v3/users/1"
-                    method: DELETE
-                  lock:
-                    href: "/api/v3/users/1/lock"
-                    method: POST
-                  self:
-                    href: "/api/v3/users/1"
-                    title: j.sheppard
-                  show:
-                    href: "/users/1"
-                    type: text/html
-                  updateImmediately:
-                    href: "/api/v3/users/1"
-                    method: PATCH
-                _type: User
-                admin: true
-                avatar: https://example.org/users/1/avatar
-                createdAt: '2014-05-21T08:51:20Z'
-                email: shep@mail.com
-                firstName: John
-                id: 1
-                language: en
-                lastName: Sheppard
-                login: j.sheppard
-                status: active
-                updatedAt: '2014-05-21T08:51:20Z'
           schema:
-            "$ref": "../components/schemas/user_model.yml"
+            $ref: '../components/schemas/user_model.yml'
       description: OK
-      headers: {}
     '400':
       content:
         application/hal+json:
           schema:
-            $ref: "../components/schemas/error_response.yml"
-          examples:
-            response:
-              value:
-                _type: Error
-                errorIdentifier: urn:openproject-org:api:v3:errors:InvalidUserStatusTransition
-                message: The current user account status does not allow this operation.
+            $ref: '../components/schemas/error_response.yml'
+          example:
+            _type: Error
+            errorIdentifier: urn:openproject-org:api:v3:errors:InvalidUserStatusTransition
+            message: The current user account status does not allow this operation.
       description: |-
         Returned if the client tries to lock a user account whose current status does not allow this transition.
 
         **Required permission:** Administrators only
-      headers: {}
     '403':
       content:
         application/hal+json:
           schema:
-            $ref: "../components/schemas/error_response.yml"
-          examples:
-            response:
-              value:
-                _type: Error
-                errorIdentifier: urn:openproject-org:api:v3:errors:MissingPermission
-                message: You are not allowed to lock the account of this user.
+            $ref: '../components/schemas/error_response.yml'
+          example:
+            _type: Error
+            errorIdentifier: urn:openproject-org:api:v3:errors:MissingPermission
+            message: You are not allowed to lock the account of this user.
       description: |-
         Returned if the client does not have sufficient permissions for locking a user.
 
         **Required permission:** Administrators only
-      headers: {}
     '404':
       content:
         application/hal+json:
           schema:
-            $ref: "../components/schemas/error_response.yml"
-          examples:
-            response:
-              value:
-                _type: Error
-                errorIdentifier: urn:openproject-org:api:v3:errors:NotFound
-                message: The specified user does not exist.
+            $ref: '../components/schemas/error_response.yml'
+          example:
+            _type: Error
+            errorIdentifier: urn:openproject-org:api:v3:errors:NotFound
+            message: The specified user does not exist.
       description: Returned if the user does not exist.
-      headers: {}
-  tags:
-  - Users
-  description: ''
-  operationId: Lock_user
-  summary: Lock user

docs/api/apiv3/paths/users.yml

@@ -1,244 +1,157 @@
 # /api/v3/users
 ---
 get:
+  summary: List Users
+  operationId: list_Users
+  description: Lists users. Only administrators or users with manage_user global permission have permission to do this.
+  tags:
+    - Users
   parameters:
-  - description: Page number inside the requested collection.
-    example: '25'
-    in: query
-    name: offset
-    required: false
-    schema:
-      default: 1
-      type: integer
-  - description: Number of elements to display per page.
-    example: '25'
-    in: query
-    name: pageSize
-    required: false
-    schema:
-      type: integer
-  - description: |-
-      JSON specifying filter conditions.
-      Accepts the same format as returned by the [queries](https://www.openproject.org/docs/api/endpoints/queries/)
-      endpoint. Currently supported filters are:
-
-      + status: Status the user has
-
-      + group: Name of the group in which to-be-listed users are members.
-
-      + name: Filter users in whose first or last names, or email addresses the given string occurs.
-
-      + login: User's login
-    example: '[{ "status": { "operator": "=", "values": ["invited"] } }, { "group":
+    - description: Page number inside the requested collection.
+      example: '25'
+      in: query
+      name: offset
+      required: false
+      schema:
+        default: 1
+        type: integer
+    - description: Number of elements to display per page.
+      example: '25'
+      in: query
+      name: pageSize
+      required: false
+      schema:
+        type: integer
+    - description: |-
+        JSON specifying filter conditions.
+        Accepts the same format as returned by the [queries](https://www.openproject.org/docs/api/endpoints/queries/)
+        endpoint. Currently supported filters are:
+        
+        + status: Status the user has
+        
+        + group: Name of the group in which to-be-listed users are members.
+        
+        + name: Filter users in whose first or last names, or email addresses the given string occurs.
+        
+        + login: User's login
+      example: '[{ "status": { "operator": "=", "values": ["invited"] } }, { "group":
       { "operator": "=", "values": ["1"] } }, { "name": { "operator": "=", "values":
       ["h.wurst@openproject.com"] } }]'
-    in: query
-    name: filters
-    required: false
-    schema:
-      type: string
-  - description: |-
-      JSON specifying sort criteria.
-      Accepts the same format as returned by the [queries](https://www.openproject.org/docs/api/endpoints/queries/) endpoint.
-    example: '[["status", "asc"]]'
-    in: query
-    name: sortBy
-    required: false
-    schema:
-      type: string
-  - description: |-
-      Comma separated list of properties to include.
-    example: 'total,elements/name,elements/self,self'
-    in: query
-    name: select
-    required: false
-    schema:
-      type: string
+      in: query
+      name: filters
+      required: false
+      schema:
+        type: string
+    - description: |-
+        JSON specifying sort criteria.
+        Accepts the same format as returned by the [queries](https://www.openproject.org/docs/api/endpoints/queries/) endpoint.
+      example: '[["status", "asc"]]'
+      in: query
+      name: sortBy
+      required: false
+      schema:
+        type: string
+    - description: |-
+        Comma separated list of properties to include.
+      example: 'total,elements/name,elements/self,self'
+      in: query
+      name: select
+      required: false
+      schema:
+        type: string
   responses:
     '200':
       content:
         application/hal+json:
-          examples:
-            response:
-              value:
-                _embedded:
-                  elements:
-                  - _links:
-                      delete:
-                        href: "/api/v3/users/1"
-                        method: DELETE
-                        title: Delete j.sheppard
-                      lock:
-                        href: "/api/v3/users/1/lock"
-                        method: POST
-                        title: Set lock on j.sheppard
-                      self:
-                        href: "/api/v3/users/1"
-                        title: John Sheppard - j.sheppard
-                      showUser:
-                        href: "/users/1"
-                        type: text/html
-                      update:
-                        href: "/api/v3/users/1"
-                        method: PATCH
-                        title: Update j.sheppard
-                    _type: User
-                    admin: true
-                    avatar: https://example.org/users/1/avatar
-                    createdAt: '2014-05-21T08:51:20Z'
-                    email: shep@mail.com
-                    firstName: John
-                    id: 1
-                    language: en
-                    lastName: Sheppard
-                    login: j.sheppard
-                    status: active
-                    updatedAt: '2014-05-21T08:51:20Z'
-                _links:
-                  self:
-                    href: "/api/v3/users"
-                _type: Collection
-                count: 1
-                total: 2
           schema:
-            "$ref": "../components/schemas/users_model.yml"
+            $ref: '../components/schemas/user_collection_model.yml'
       description: OK
-      headers: {}
     '400':
       content:
         application/hal+json:
           schema:
-            $ref: "../components/schemas/error_response.yml"
-          examples:
-            response:
-              value:
-                _type: Error
-                errorIdentifier: urn:openproject-org:api:v3:errors:InvalidQuery
-                message: Unknown sort column.
+            $ref: '../components/schemas/error_response.yml'
+          example:
+            _type: Error
+            errorIdentifier: urn:openproject-org:api:v3:errors:InvalidQuery
+            message: Unknown sort column.
       description: Returned if the client sends an unknown sort column.
-      headers: {}
     '403':
       content:
         application/hal+json:
           schema:
-            $ref: "../components/schemas/error_response.yml"
-          examples:
-            response:
-              value:
-                _type: Error
-                errorIdentifier: urn:openproject-org:api:v3:errors:MissingPermission
-                message: You are not allowed to list users.
+            $ref: '../components/schemas/error_response.yml'
+          example:
+            _type: Error
+            errorIdentifier: urn:openproject-org:api:v3:errors:MissingPermission
+            message: You are not allowed to list users.
       description: |-
         Returned if the client does not have sufficient permissions.
 
         **Required permission:** Administrator
-      headers: {}
-  tags:
-  - Users
-  description: Lists users. Only administrators or users with manage_user global permission
-    have permission to do this.
-  operationId: List_Users
-  summary: List Users
+
 post:
+  summary: Create User
+  operationId: create_user
+  tags:
+    - Users
+  description: |-
+    Creates a new user. Only administrators and users with manage_user global permission are allowed to do so.
+    When calling this endpoint the client provides a single object, containing at least the properties and links that are required, in the body.
+
+    Valid values for `status`:
+
+    1) "active" - In this case a password has to be provided in addition to the other attributes.
+    
+    2) "invited" - In this case nothing but the email address is required. The rest is optional. An invitation will be sent to the user.
+  requestBody:
+    content:
+      application/json:
+        schema:
+          $ref: '../components/schemas/user_create_model.yml'
   responses:
     '201':
       content:
         application/hal+json:
           schema:
-            "$ref": "../components/schemas/user_model.yml"
+            $ref: '../components/schemas/user_model.yml'
       description: Created
-      headers: {}
     '400':
       content:
         application/hal+json:
           schema:
-            $ref: "../components/schemas/error_response.yml"
-          examples:
-            response:
-              value:
-                _type: Error
-                errorIdentifier: urn:openproject-org:api:v3:errors:InvalidRequestBody
-                message: The request body was not a single JSON object.
-      description: Occurs when the client did not send a valid JSON object in the
-        request body.
-      headers: {}
+            $ref: '../components/schemas/error_response.yml'
+          example:
+            _type: Error
+            errorIdentifier: urn:openproject-org:api:v3:errors:InvalidRequestBody
+            message: The request body was not a single JSON object.
+      description: Occurs when the client did not send a valid JSON object in the request body.
     '403':
       content:
         application/hal+json:
           schema:
-            $ref: "../components/schemas/error_response.yml"
-          examples:
-            response:
-              value:
-                _type: Error
-                errorIdentifier: urn:openproject-org:api:v3:errors:MissingPermission
-                message: You are not allowed to create new users.
+            $ref: '../components/schemas/error_response.yml'
+          example:
+            _type: Error
+            errorIdentifier: urn:openproject-org:api:v3:errors:MissingPermission
+            message: You are not allowed to create new users.
       description: |-
         Returned if the client does not have sufficient permissions.
 
         **Required permission:** Administrator
-      headers: {}
     '422':
       content:
         application/hal+json:
           schema:
-            $ref: "../components/schemas/error_response.yml"
-          examples:
-            response:
-              value:
-                _embedded:
-                  details:
-                    attribute: email
-                _type: Error
-                errorIdentifier: urn:openproject-org:api:v3:errors:PropertyConstraintViolation
-                message: The email address is already taken.
+            $ref: '../components/schemas/error_response.yml'
+          example:
+            _embedded:
+              details:
+                attribute: email
+            _type: Error
+            errorIdentifier: urn:openproject-org:api:v3:errors:PropertyConstraintViolation
+            message: The email address is already taken.
       description: |-
         Returned if:
 
         * a constraint for a property was violated (`PropertyConstraintViolation`)
-      headers: {}
-  tags:
-  - Users
-  description: |-
-    Creates a new user. Only administrators and users with manage_user global permission are allowed to do so.
-    When calling this endpoint the client provides a single object, containing at least the properties and links that are required, in the body.
-
-    Valid values for `status`:
-
-    1) "active" - In this case a password has to be provided in addition to the other attributes.
-    
-    2) "invited" - In this case nothing but the email address is required. The rest is optional. An invitation will be sent to the user.
-    
-  operationId: Create_User
-  requestBody:
-    content:
-      application/json:
-        schema:
-          example:
-            admin: false
-            email: h.wurst@openproject.com
-            firstName: Hans
-            language: de
-            lastName: Wurst
-            login: h.wurst
-            password: hunter5
-            status: active
-          properties:
-            admin:
-              type: boolean
-            email:
-              type: string
-            firstName:
-              type: string
-            language:
-              type: string
-            lastName:
-              type: string
-            login:
-              type: string
-            password:
-              type: string
-            status:
-              type: string
-          type: object
-  summary: Create User

docs/api/apiv3/paths/work_package_update_file_links.yml

@@ -0,0 +1,54 @@
+# /api/v3/work_packages/{id}/update_file_links
+---
+post:
+  summary: Updated the origin data of the file links of a work package.
+  operationId: update_work_package_file_links
+  tags:
+    - Work Packages
+    - File links
+  description: |-
+    Updates the origin file data of a all file links within a work package.
+    
+    The cached data is updated (overwritten) with the new data. If any data point is not available in the new data, but
+    in the old cache, it is not overwritten.
+    
+    After a successful update the client SHOULD retrieve the links of file links again to obtain the new data.
+  parameters:
+    - name: id
+      description: Work package id
+      in: path
+      required: true
+      schema:
+        type: integer
+      example: 1337
+  responses:
+    '204':
+      description: No content
+    '403':
+      content:
+        application/hal+json:
+          schema:
+            $ref: "../components/schemas/error_response.yml"
+          example:
+            _type: Error
+            errorIdentifier: urn:openproject-org:api:v3:errors:MissingPermission
+            message: You are not authorized to access this resource.
+      description: |-
+        Returned if the client does not have sufficient permissions.
+
+        **Required permission:** view file links
+
+        *Note that you will only receive this error, if you are at least allowed to see the corresponding work package.*
+    '404':
+      content:
+        application/hal+json:
+          schema:
+            $ref: "../components/schemas/error_response.yml"
+          example:
+            _type: Error
+            errorIdentifier: urn:openproject-org:api:v3:errors:NotFound
+            message: The requested resource could not be found.
+      description: |-
+        Returned if the work package does not exist or the client does not have sufficient permissions to see it.
+
+        **Required permission:** view work package, view file links

docs/development/concepts/application-architecture/README.md

@@ -38,7 +38,7 @@ This approach has the significant disadvantage to go through the entire Rails st
 
 ## Exemplary Rails view request augmented by Angular
 
-A response that is fully controlled by Rails but extended by some Angular components in the frontend might look as follows. Let's take a look at the request to [edit a type's form configuration](../../../system-admin-guide/manage-work-packages/work-package-types/#work-package-form-configuration) `/types/1/edit/form_configuration`:
+A response that is fully controlled by Rails but extended by some Angular components in the frontend might look as follows. Let's take a look at the request to [edit a type's form configuration](../../../system-admin-guide/manage-work-packages/work-package-types/#work-package-form-configuration-premium-feature) `/types/1/edit/form_configuration`:
 
 1. Rails receives the request and according to its [`config/routes.rb`](https://github.com/opf/openproject/blob/dev/config/routes.rb#L257), will handle the request with the [TypesController#edit action](https://github.com/opf/openproject/blob/dev/app/controllers/types_controller.rb#L71-L82) with its tab set to `form_configuration`. 
 

docs/development/concepts/inline-editing/README.md

@@ -290,7 +290,7 @@ While this doesn't take care of any labels or styling, it will already provide e
 
 The work package single view is the boss fight of inline editing. It combines all the previous concepts with the flexibility of work package attributes and type configuration.
 
-The following screenshot is [bug report #34250](https://community.openproject.com/wp/34250), which is a work package of Type `Bug`. The Bug type has a [specific form configuration](../../../system-admin-guide/manage-work-packages/work-package-types/#work-package-form-configuration) defined. This configuration is as follows:
+The following screenshot is [bug report #34250](https://community.openproject.com/wp/34250), which is a work package of Type `Bug`. The Bug type has a [specific form configuration](../../../system-admin-guide/manage-work-packages/work-package-types/#work-package-form-configuration-premium-feature) defined. This configuration is as follows:
 
 
 

docs/development/concepts/resource-schemas/README.md

@@ -42,7 +42,7 @@ The following guides are related:
 
 Schemas in the backend are regular Grape endpoints. For example, the schema of all projects is rendered through the [`::API::V3::Projects::Schemas::ProjectsSchemaAPI`](https://github.com/opf/openproject/blob/dev/lib/api/v3/projects/schemas/project_schema_api.rb). This in turn renders the associated [`::API::V3::Projects::Schemas::ProjectsSchemaRepresenter`](https://github.com/opf/openproject/blob/dev/lib/api/v3/projects/schemas/project_schema_representer.rb), which contains the set of schema properties to be rendered.
 
-The work packages' schemas are significantly more complex. Each work package type will define its own schema due to the dynamics of the [form configuration](../../../system-admin-guide/manage-work-packages/work-package-types/#work-package-form-configuration). With it, the order and grouping of work package attributes can be defined per type, resulting in different attributes to be displayed. In addition, custom fields can be individually enable per project for even more flexibility.
+The work packages' schemas are significantly more complex. Each work package type will define its own schema due to the dynamics of the [form configuration](../../../system-admin-guide/manage-work-packages/work-package-types/#work-package-form-configuration-premium-feature). With it, the order and grouping of work package attributes can be defined per type, resulting in different attributes to be displayed. In addition, custom fields can be individually enable per project for even more flexibility.
 
 This results in not a single schema for all work packages, but one schema for each project - type combination. 
 
@@ -80,7 +80,7 @@ For projects, there is a single APIv3 endpoint for their schemas: `/api/v3/proje
 
 **Work packages**
 
-The work package schema is more complicated, as work package types can be customized to define what attributes the type should show as part of the [form configuration](../../../system-admin-guide/manage-work-packages/work-package-types/#work-package-form-configuration). Additionally, the visibility of custom fields can be controlled on a per-project level.
+The work package schema is more complicated, as work package types can be customized to define what attributes the type should show as part of the [form configuration](../../../system-admin-guide/manage-work-packages/work-package-types/#work-package-form-configuration-premium-feature). Additionally, the visibility of custom fields can be controlled on a per-project level.
 
 This results in work package schemas being defined per project and type combination. The URL of each schema looks like this: `/api/v3/work_packages/schemas/{project id}-{type-id}`.
 

docs/development/design-system/README.md

@@ -43,6 +43,19 @@ keywords: Design system, styles, design, components
 | [Toast](https://www.figma.com/file/XhCsrvs6rePifqbBpKYRWD/?node-id=391%3A3910) | Working draft, designed, no documentation yet |  |
 | [Tooltip](https://www.figma.com/file/XhCsrvs6rePifqbBpKYRWD/?node-id=391%3A3910) | Working draft, designed, no documentation yet |  |
 
+### Search field
+
+| Places where we use this style     | Current implementation | Migration to design system                              |
+| ---------------------------------- | ---------------------- | ------------------------------------------------------- |
+| Work packages -> Include projects  | Angular                | [12.1](https://community.openproject.org/versions/1493) |
+| Sidebar                            | Angular                | [12.2](https://community.openproject.org/versions/1494) |
+| Header main navigation             | Angular                | [12.2](https://community.openproject.org/versions/1494) |
+| Administration -> User             | Rails                  |                                                         |
+| Administration -> Placeholder User | Rails                  |                                                         |
+| Work packages -> Add relation      | Angular                |                                                         |
+| Work packages -> Add watcher       | Angular                |                                                         |
+| Work packages -> Add parent        | Angular                |                                                         |
+
 ## Patterns
 
 | Style definitions (Figma)                                    | Status                         | Implementation examples                                      |

docs/development/development-environment-docker/README.md

@@ -192,7 +192,7 @@ When a dependency of the image or the base image itself is changed you may need
 Ruby version is updated you may run into an error like the following when running `bin/compose setup`:
 
 ```
-Your Ruby version is 2.7.4, but your Gemfile specified ~> 3.0.4
+Your Ruby version is 2.7.6, but your Gemfile specified ~> 3.1.2
 ```
 
 This means that the current image is out-dated. You can update it like this:

docs/development/development-environment-osx/README.md

@@ -15,7 +15,7 @@ We'll use [homebrew](https://brew.sh/) to install most of our requirements. Plea
 
 ## Install Ruby
 
-Use [rbenv](https://github.com/rbenv/rbenv) and [ruby-build](https://github.com/rbenv/ruby-build#readme) to install Ruby. We always require the latest ruby versions, and you can check which version is required by [checking the Gemfile](https://github.com/opf/openproject/blob/dev/Gemfile#L31) for the `ruby "~> X.Y"` statement. At the time of writing, this version is "3.0.4"
+Use [rbenv](https://github.com/rbenv/rbenv) and [ruby-build](https://github.com/rbenv/ruby-build#readme) to install Ruby. We always require the latest ruby versions, and you can check which version is required by [checking the Gemfile](https://github.com/opf/openproject/blob/dev/Gemfile#L31) for the `ruby "~> X.Y"` statement. At the time of writing, this version is "3.1.2"
 
 ### Install rbenv and ruby-build
 
@@ -32,20 +32,20 @@ $ rbenv init
 ### Installing ruby-3.0
 
 With both installed, we can now install the actual ruby version 3.0. You can check available ruby versions with `rbenv install --list`.
-At the time of this writing, the latest stable version is `3.0.4`, which we also require.
+At the time of this writing, the latest stable version is `3.1.2`, which we also require.
 
 We suggest you install the version we require in the [Gemfile](https://github.com/opf/openproject/blob/dev/Gemfile). Search for the `ruby '~> X.Y.Z'` line
 and install that version.
 
 ```bash
 # Install the required version as read from the Gemfile
-rbenv install 3.0.4
+rbenv install 3.1.2
 ```
 
 This might take a while depending on whether ruby is built from source. After it is complete, you need to tell rbenv to globally activate this version
 
 ```bash
-rbenv global 3.0.4
+rbenv global 3.1.2
 ```
 
 You also need to install [bundler](https://github.com/bundler/bundler/), the ruby gem bundler.
@@ -116,7 +116,7 @@ You should now have an active ruby and node installation. Verify that it works w
 
 ```bash
 $ ruby --version
-ruby 3.0.4p208 (2022-04-12 revision 3fa771dded) [x86_64-linux]
+ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-linux]
 
 $ bundler --version
 Bundler version 2.3.12

docs/development/development-environment-ubuntu/README.md

@@ -26,7 +26,7 @@ sudo apt-get install git curl build-essential zlib1g-dev libyaml-dev libssl-dev
 
 ## Install Ruby
 
-Use [rbenv](https://github.com/rbenv/rbenv) and [ruby-build](https://github.com/rbenv/ruby-build#readme) to install Ruby. We always require the latest ruby versions, and you can check which version is required by [checking the Gemfile](https://github.com/opf/openproject/blob/dev/Gemfile#L31) for the `ruby "~> X.Y"` statement. At the time of writing, this version is "3.0.4"
+Use [rbenv](https://github.com/rbenv/rbenv) and [ruby-build](https://github.com/rbenv/ruby-build#readme) to install Ruby. We always require the latest ruby versions, and you can check which version is required by [checking the Gemfile](https://github.com/opf/openproject/blob/dev/Gemfile#L31) for the `ruby "~> X.Y"` statement. At the time of writing, this version is "3.1.2"
 
 ### Install rbenv and ruby-build
 
@@ -60,20 +60,20 @@ git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build
 ### Installing ruby-3.0
 
 With both installed, we can now install the actual ruby version 3.0. You can check available ruby versions with `rbenv install --list`.
-At the time of this writing, the latest stable version is `3.0.4` which we also require.
+At the time of this writing, the latest stable version is `3.1.2` which we also require.
 
 We suggest you install the version we require in the [Gemfile](https://github.com/opf/openproject/blob/dev/Gemfile). Search for the `ruby '~> X.Y.Z'` line
 and install that version.
 
 ```bash
 # Install the required version as read from the Gemfile
-rbenv install 3.0.4
+rbenv install 3.1.2
 ```
 
 This might take a while depending on whether ruby is built from source. After it is complete, you need to tell rbenv to globally activate this version
 
 ```bash
-rbenv global 3.0.4
+rbenv global 3.1.2
 rbenv rehash
 ```
 
@@ -159,7 +159,7 @@ You should now have an active ruby and node installation. Verify that it works w
 
 ```bash
 ruby --version
-ruby 3.0.4p208 (2022-04-12 revision 3fa771dded) [x86_64-linux]
+ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-linux]
 
 bundler --version
 Bundler version 2.3.12

docs/installation-and-operations/configuration/README.md

@@ -445,7 +445,7 @@ web:
 As usual these values can be overridden via the environment.
 
 ```
-OPENPROJECT_WEB_WORKERs=2
+OPENPROJECT_WEB_WORKERS=2
 OPENPROJECT_WEB_TIMEOUT=60 # overridden by: RACK_TIMEOUT_SERVICE_TIMEOUT
 OPENPROJECT_WEB_WAIT__TIMEOUT=10 # overridden by: RACK_TIMEOUT_WAIT_TIMEOUT
 OPENPROJECT_WEB_MIN__THREADS=4 # overridden by: RAILS_MIN_THREADS

docs/installation-and-operations/configuration/incoming-emails/README.md

@@ -26,7 +26,7 @@ openproject run bundle exec rake redmine:email:receive_imap host='imap.gmail.com
 
 **Docker installation**
 
-The docker installation has a ["cron-like" daemon](https://github.com/opf/openproject/blob/dev/docker/cron) that will imitate the above cron job. You need to specify the following ENV variables (e.g., to your env list file)
+The docker installation has a ["cron-like" daemon](https://github.com/opf/openproject/blob/dev/docker/prod/cron) that will imitate the above cron job. You need to specify the following ENV variables (e.g., to your env list file)
 
 - `IMAP_SSL` set to true or false depending on whether the ActionMailer IMAP connection requires implicit TLS/SSL
 - `IMAP_PORT` `IMAP_HOST` set to the IMAP host and port of your connection

docs/installation-and-operations/installation/manual/README.md

@@ -106,16 +106,16 @@ time to finish.
 [openproject@host] source ~/.profile
 [openproject@host] git clone https://github.com/sstephenson/ruby-build.git ~/.rbenv/plugins/ruby-build
 
-[openproject@host] rbenv install 3.0.4
+[openproject@host] rbenv install 3.1.2
 [openproject@host] rbenv rehash
-[openproject@host] rbenv global 3.0.4
+[openproject@host] rbenv global 3.1.2
 ```
 
 To check our Ruby installation we run `ruby --version`. It should output
 something very similar to:
 
 ```
-ruby 3.0.4p208 (2022-04-12 revision 3fa771dded) [x86_64-linux]
+ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-linux]
 ```
 
 ## Installation of Node

docs/release-notes/12-1-0/README.md

@@ -222,5 +222,5 @@ A big thanks to community members for reporting bugs and helping us identifying
 - Special thanks for Autoliv for sponsoring the development of the new team planner.
 - Special thanks for City of Cologne for sponsoring the development of the new global roles for groups.
 - Special thanks for reporting and finding bugs go Rainer Proehl, kak tux, Sven Kunze, Çağlar Yeşilyurt, Valentin Ege, Michael Kluge, Christina Vechkanova, Marius Heidenreich, Gerrit Bonn, Benjamin Tey, Daniel Wilke, Avgerinos Fotopoulos, Thilo Sautter, Andreas Sturm.
-- Every other dedicated user who has [reported bugs](../development/report-a-bug/) and supported the community by asking and answering questions in the [forum](https://community.openproject.org/projects/openproject/boards).
+- Every other dedicated user who has [reported bugs](../../development/report-a-bug/) and supported the community by asking and answering questions in the [forum](https://community.openproject.org/projects/openproject/boards).
 - All the dedicated users who provided translations on [CrowdIn](https://crowdin.com/projects/opf).

docs/system-admin-guide/custom-fields/README.md

@@ -49,7 +49,7 @@ Depending on the module, for which the new custom field is being  created, sligh
     2. Custom field is activated for the project.
 </div>
 
-1. [Assign a custom field to a work package type](../manage-work-packages/work-package-types/#work-package-form-configuration) (Form configuration). You can do this directly via the link in the custom field overview.
+1. [Assign a custom field to a work package type](../manage-work-packages/work-package-types/#work-package-form-configuration-premium-feature) (Form configuration). You can do this directly via the link in the custom field overview.
 
 ![Sys-admin-add-custom-field](Sys-admin-add-custom-field.png)
 

docs/system-admin-guide/incoming-and-outgoing/README.md

@@ -12,11 +12,11 @@ Configure **Emails and notification settings** in OpenProject, i.e. email notifi
 
 Navigate to *Administration* -> *Emails and notification*.
 
-| Topic                                                            | Content                                                    |
-|------------------------------------------------------------------|------------------------------------------------------------|
-| [Emails and notification settings](#incoming--outgoing-settings) | How to configure the global incoming and outgoing settings |
-| [Email notifications](#email-notifications-settings)             | How to configure outgoing email notifications?             |
-| [Incoming emails](#incoming-emails-settings)                     | How to configure settings for inbound emails?              |
+| Topic                                                                 | Content                                                    |
+|-----------------------------------------------------------------------|------------------------------------------------------------|
+| [Emails and notification settings](#emails-and-notification-settings) | How to configure the global incoming and outgoing settings |
+| [Email notifications](#email-notifications-settings)                  | How to configure outgoing email notifications?             |
+| [Incoming emails](#incoming-emails-settings)                          | How to configure settings for inbound emails?              |
 
 ## Emails and notification settings
 

docs/system-admin-guide/manage-work-packages/work-package-types/README.md

@@ -37,10 +37,14 @@ Click the green **+ Type** button to add a new work package type in the system,
 
 ![Sys-admin-add-work-package-type](Sys-admin-add-work-package-type.png)
 
-## Work package form configuration
+## Work package form configuration (Premium feature)
 
 You can freely **configure the attributes shown** for each work package type to decide which attributes are shown in the form and how they are grouped.
 
+<div class="alert alert-info" role="alert">
+**Note**: The Work package form configuration is a premium feature and only available for the [OpenProject Cloud Edition](https://www.openproject.org/hosting/) and the [Enterprise On-premises Edition](https://www.openproject.org/enterprise-edition/).
+</div>
+
 To configure a type, first select the type from the list of types (see above) and select the tab ***Form configuration*** *(1)*.
 
 Active attributes shown in blue color on the left will be displayed in the work package form for this type.
@@ -54,7 +58,7 @@ In case you made a mistake, click the *Reset to defaults (5)* button to reset al
 
 Finally, **save** the settings to apply them *(6)*.
 
-​      ![Sys-admin-type-form-configuration](Sys-admin-type-form-configuration-1579181896505.png)
+![Sys-admin-type-form-configuration](Sys-admin-type-form-configuration-1579181896505.png)
 
 If you then create a new work package of this type, the input form will have exactly these attributes selected in the form configuration.
 
@@ -66,10 +70,12 @@ Watch the following video to see how you can customize your work packages with c
 
 <video src="https://openproject-docs.s3.eu-central-1.amazonaws.com/videos/OpenProject-Forms-and-Custom-Fields-1.mp4" type="video/mp4" controls="" style="width:100%"></video>
 
-## Add table of related work packages to a work package form
+## Add table of related work packages to a work package form (Premium feature)
 
 Also, you can add a table of related work packages to your work package form. Click the green **+ Group** button and choose **Add table of related work package** from the drop-down list.
 
+**Note**: To Add a table of related work package in OpenProject is a Premium Feature and can only be used with [Enterprise cloud](../../enterprise-guide/enterprise-cloud-guide/) or [Enterprise on-premises](../../enterprise-guide/enterprise-on-premises-guide/). An upgrade from the free Community Edition is easily possible.
+
 ![Sys-admin-table-of-related-work-packages](Sys-admin-table-of-related-work-packages.png)
 
 Now, you can configure which related work packages should be included in your embedded list, e.g. child work packages or work packages related to this work package, and more. Then you can configure how the list should be filtered, grouped, etc. The configuration of the work package list can be done according to the [work package table configuration](../../../user-guide/work-packages/work-package-table-configuration/).

docs/system-admin-guide/users-permissions/roles-permissions/README.md

@@ -13,12 +13,12 @@ A **role** is a set of **permissions** that can be assigned to any project membe
 When creating a role, the "Global role" field can be ticked, making it a **Global role** that can be assigned to a [user details](../users/#manage-user-settings) or a [group details](../groups/#add-global-roles-to-a-group) and applied across all projects.
 
 
-| Topic                                           | Content                                                      |
-| ----------------------------------------------- | ------------------------------------------------------------ |
+| Topic                                           | Content                                                           |
+| ----------------------------------------------- |-------------------------------------------------------------------|
 | [Permissions](#permissions)                     | What are permissions and how can I access the permissions report? |
-| [Create a new role](#create-a-new-role)         | How to create a new (global) role.                           |
-| [Edit and remove roles](#edit-and-remove-roles) | How to change and delete existing roles.                     |
-| [Global roles](#global-roles)                   | Which global roles are there and what are their significances? |
+| [Create a new role](#create-a-new-role)         | How to create a new (global) role.                                |
+| [Edit and remove roles](#edit-and-remove-roles) | How to change and delete existing roles.                          |
+| [Global roles](#global-roles)                   | Which global roles are there and what are their significances?    |
 
 ## Permissions
 
@@ -55,15 +55,19 @@ Complete the following as required:
 1. **Role name** - must be entered and be a new name.
 2. **Global Role** - this role applies to all projects, and can be assigned in the [user details](../users/#manage-user-settings) or in the [group details](../groups/#add-global-roles-to-a-group). Once saved, the decision to make a role a "global role" can't be reverted.
    Ticking this box will show the available [global roles](#global-roles) and hide the regular permission options.
-3. **Work packages...** - tick to allow work packages to be assigned to a user with this role. This does not appear for global roles.
-4. **Copy workflow from** - select an existing role. The respective [workflows](../../manage-work-packages/work-package-workflows) will be copied to the role to be created.
-5. **Permissions** for this role - you can specify the permissions per OpenProject module. Click the arrow next to the module name to expand or compress the permissions list.
+3. **Copy workflow from** - select an existing role. The respective [workflows](../../manage-work-packages/work-package-workflows) will be copied to the role to be created.
+4. **Permissions** for this role - you can specify the permissions per OpenProject module. Click the arrow next to the module name to expand or compress the permissions list.
 
 Select the permissions which should apply for this role. You can use "check all" or "uncheck all" at the right of a module permissions list. If a module is not enabled in a project it is not shown to a user despite having a permission for it.
 
 Don't forget to click the **Save** button at the bottom of the page.
 
-![Sys-admin-create-new-role](Sys-admin-create-new-role.png)
+![create new role with role template](create-new-role-with-role-template.png)
+
+**Note:** In the work package tracking section, you can also give the role permission to be able to be assigned to work packages or to be set as a responsible person.
+
+![work package tracking for role](work-package-tracking-for-role-8145761.png)
+
 
 ## Edit and remove roles
 

docs/user-guide/calendar/README.md

@@ -75,12 +75,6 @@ Click Escape (**Esc**) to leave the Zen mode.
 
 ## Project overarching calendar
 
-It is possible to display the work packages from more than one project in the calendar. However, these projects need to be sub-projects of the current project.
+It is possible to display the work packages from more than one project in the calendar. To include, or exclude such work packages, use the **Include projects** dialog, where you can select/unselect the appropriate projects and sub-projects. To automatically include all subprojects for each project you chose to select, check the **Include all sub-projects** box at the bottom of the dialog.
 
-Open the filter and select subproject as filter criteria.
-
-Choose the sub-projects which you also want to display in the calendar view.
-
-![subproject-calendar](subproject-calendar.png)
-
-It is not possible to add work packages from projects which are not in a project hierarchy.
+![Select projects](select-projects.png)

docs/user-guide/projects/project-settings/custom-fields/README.md

@@ -18,7 +18,7 @@ Before you can enable a custom field it needs to be created in the [system admin
 
 1. Manage the custom field by clicking on the name.
 2. **Select if the custom fields shall be enabled in the project**. If enabled globally in the custom fields settings in the system administration, it will automatically be displayed in all projects.
-3. View the work package types for which the custom field is already enabled. Only for the displayed types the custom field will be active. You can add the custom field to additional work package types by [adding them to the respective work package form](../../../../system-admin-guide/manage-work-packages/work-package-types/#work-package-form-configuration).
+3. View the work package types for which the custom field is already enabled. Only for the displayed types the custom field will be active. You can add the custom field to additional work package types by [adding them to the respective work package form](../../../../system-admin-guide/manage-work-packages/work-package-types/#work-package-form-configuration-premium-feature).
 4. **Create a new custom field** with the green + Custom field button. You have to be a system administrator in order to create new custom fields.
 5. Press the blue **Save** button to confirm your changes.
 

docs/user-guide/team-planner/README.md

@@ -1,7 +1,7 @@
 ---
 sidebar_navigation:
   title: Team planner
-  priority: 890
+  priority: 863
 description: Using the team planner in OpenProject.
 robots: index, follow
 keywords: team planner,planning calendar, resource management
@@ -18,7 +18,7 @@ A few notes:
 
 | Topic                                                                                     | Content                                     |
 |-------------------------------------------------------------------------------------------|:--------------------------------------------|
-| [Main view](#main-view-start-a-new-or-select-an-existing-team-planner)                    | How to start a team planner?                |
+| [Main view](#main-view---start-a-new-or-select-an-existing-team-planner)                  | How to start a team planner?                |
 | [Planning calendar basics](#planning-calendar-basics)                                     | How to navigate the team planner?           |
 | [Getting started](#getting-started)                                                       | How to get started?                         |
 | [Adding team members](#step-1-adding-team-members)                                        | How to add team members?                    |
@@ -66,17 +66,33 @@ The first step in setting up your team planning calendar is to add team members.
 
 Repeat this step until all team members relevant for this planner are added, and then save it using the floppy disk icon (adjacent to the top header in #1 above). 
 
+If you need to delete a member, please hover over their name in the team planner in the **Assignees** column and remove them by clicking on the **X button**, which will appear adjacent to the name during hovering.
+
 **Note: Once you are finished adding members to the planner, click the floppy disk icon in the top header to save.**
 
 ![Adding team members](adding-team-members.png)
 
 ### Step 2: Adding/working with work package strips
 
-Next, add specific work packages to your planner. Do this by pressing the **+ add existing" button** we introduced in step 2 of the main view overview. Once you press the **+ add existing** button, start typing the name of the work package you are looking to add. Once found, drag & drop the work package strip. Should the work package have a duration exceeding the current 1 or 2 week view, a horizontal scroll bar will display, with which it is possible to scroll to the end date of the longest running work package.
+Next, add specific work packages to your planner. You can do this by either adding a **new work package**, or by adding an **existing work package**:
+
+**To add a new work package**: 
+
+Click on the cell in the team planner grid that corresponds to the preferred assignee and start date.
+
+![Add new work package](add-new-work-package.png)
+
+After you clicked, the **new work package dialog** will automatically open. Here you can set a variety of information pertaining to your work package, such as the (1) type, (2) one or more additional people, (3) the assignee (by default the person or group which you selected in the team planner grid), (4) the accountable person, as well as a variety of other settings, such as start and end dates, time and cost estimates, and more as you scroll further down the dialog.
+
+![New work package dialog](new-work-package-details.png)
+
+
+
+**To add an existing work package**: 
 
-Additional features: You can change the status of a work package, and enter the work package strip detailed view by pressing the info button **(i)** on each respective strip
+Press the **+ add existing" button** we introduced in step 2 of the main view overview. Once you press the **+ add existing** button, start typing the name of the work package you are looking to add. Once found, drag & drop the work package strip. Should the work package have a duration exceeding the current 1 or 2 week view, a horizontal scroll bar will display, with which it is possible to scroll to the end date of the longest running work package.
 
-**Note: You can only add existing work packages here. If you need to create some first, create them in the work package module as new work packages cannot be created from the team planner module.**
+Additional features: You can change the status of a work package, and enter the work package strip detailed view by pressing the info button **(i)** on each respective strip.
 
 ![Working with work package strips](working-with-work-package-strips.png)
 

docs/user-guide/time-and-costs/time-and-costs-faq/README.md

@@ -11,7 +11,7 @@ keywords: time and costs FAQ, time tracking, time logging, booking costs
 
 ## Is there a way to prevent logging hours for Phases (or other work package types)? 
 
-It is not possible to prevent time logging on phases or restrict it to certain work package types. You could deactivate the fields "Estimated time" and "Spent time" for type Phase (using the [work package form configuration](../../../system-admin-guide/manage-work-packages/work-package-types/#work-package-form-configuration)) but it would still be possible to log time for Phases.
+It is not possible to prevent time logging on phases or restrict it to certain work package types. You could deactivate the fields "Estimated time" and "Spent time" for type Phase (using the [work package form configuration](../../../system-admin-guide/manage-work-packages/work-package-types/#work-package-form-configuration-premium-feature)) but it would still be possible to log time for Phases.
 
 ## Can I log time for another user than myself?
 

docs/user-guide/work-packages/work-package-table-configuration/README.md

@@ -82,32 +82,22 @@ The results will be displayed accordingly in the work package list.
 If you want to only show work package with specific parents (e.g. all work packages belonging to a specific phase of your project) you can use the filter "Parent". Enter all required work packages and press Enter. This will show the selected work package(s) and its/their children. 
 If you only selected work packages without children, no work packages will be shown at all.
 
-![filter-for-parent-work-package](image-20210301182354564.png)
+![filter-for-parent-work-package](filter-for-parent-work-package.png)
 
-### Filter for work packages of a subproject
+### Include/exclude work packages from a specific project or subproject
 
-When you are in a parent project and would like to view the work packages of its subprojects, you can use a filter in the work package list.
+It is possible to display the work packages from more than one project. To include, or exclude such work packages, use the **Include projects** dialog, where you can select/unselect the appropriate projects and sub-projects. To automatically include all subprojects for each project you chose to select, check the **Include all sub-projects** box at the bottom of the dialog.
 
-The filter **Only subproject** will display all work packages of the subprojects you select. Thereby, the work packages of the parent project will not be displayed.
+![Work package filter](work_package_filter.png)
 
-![work_package_filter_only_subprojects](work_package_filter_only_subprojects.png)
-
-
-
-In order to view the work packages of the parent project as well as the subprojects that you select, you need to use the filter **Including subproject**.
-
-![work_package_filter_incl_subprojects](work_package_filter_incl_subprojects.png)
-
-
-
-To view all work packages across all projects, please refer to the [global work package list](../../projects/#global-work-packages-list).
+To view all work packages across all projects you could select everything, or use the [global work package list](../../projects/#global-work-packages-list).
 
 ### Filtering by ID or work package name
 
 If you want to [create a work package view](#save-work-package-views) with only specific work packages you can use the filter "ID". By entering the ID or subject of work packages you can select them. 
 Another use case would be to *exclude* specific work packages (e.g. you want to display all milestones but one). Therefore, use the "is not" option next to the filter's name on the left.
 
-![filtering-by-work-package-id](image-20210301185550169.png)
+![filtering-by-work-package-id](filtering-by-work-package-id.png)
 
 ### Filtering for assignees or assigned groups
 
@@ -120,7 +110,7 @@ There are several options to filter for the assignee of a work package. You can
 - Assignee's group: Filters for work packages assigned to a user from this group
 - Assignee's role: Filters for work packages assigned to users with the specified project role
 
-![assignee-or-assignee-group-filter](image-20210413115230235.png)
+![assignee-or-assignee-group-filter](assignee-or-assignee-group-filter.png)
 
 ## Sort the work package list