fix markdown lint issues

2026-06-13 19:20:00 +00:00 · 2025-05-22 14:44:48 +02:00
parent e54a3e7e4b
commit 9283eafd5e
189 changed files with 1577 additions and 1642 deletions
@@ -26,12 +26,15 @@ This platform thrives on the support of its Community, and there are many ways y
 ## How can you help?

 ### Contribute to Documentation
+
 Help keep our documentation accurate, comprehensive, and user-friendly. Whether it's fixing typos, updating outdated information, or adding new sections, your contributions make a difference. [Learn more](./contribution-documentation/).

 ### Translate OpenProject
+
 Assist in making OpenProject accessible in more languages or refine existing translations. Your input ensures that users worldwide have a seamless experience. [Learn more](./translate-openproject/).

 ### Support the Community
+
 Share your experiences by leaving a review, sharing our blog articles, or promoting OpenProject in your network. Every small effort helps expand our Community. [Learn more](./give-back-to-community).

 Please also refer to the [Development guide](../development) for Code review guidelines.
@@ -53,7 +53,7 @@ If you would like to report a typo or an inconsistency in our documentation, the

 ### Let us know through the OpenProject Community installation

-You can also join us directly through the [OpenProject Community installation](https://community.openproject.org). Here you can **leave a message on the [Forum](https://community.openproject.org/projects/openproject/forums)**, or **create a work package with the type *Documentation* ** and describe or request a documentation change.
+You can also join us directly through the [OpenProject Community installation](https://community.openproject.org). Here you can **leave a message on the [Forum](https://community.openproject.org/projects/openproject/forums)**, or **create a work package with the type *Documentation* and describe or request a documentation change.

 To gain access to the Community installation at, please send an email to [support@openproject.com](mailto:support@openproject.com) with the subject line **"Joining Community"**. Our team will review your request and send you an invitation as soon as possible.

@@ -79,7 +79,7 @@ In the first dropdown select the base branch you want your work to be merged in

 ![comparing-changes.png](comparing-changes.png)

-In the description field of the pull request enter a summary for the changes you made. If there is already a work package on https://community.openproject.org you can also add this to the description. This adds a relation between your pull request and the work package.
+In the description field of the pull request enter a summary for the changes you made. If there is already a work package on [community.openproject.org](https://community.openproject.org) you can also add this to the description. This adds a relation between your pull request and the work package.

 ## Step 9: Request review

@@ -143,7 +143,7 @@ Your Draft Pull Request will be created in the browser **on github.com** (the "d

 ![create draft pull request](Create-draft-pull-request.png)

-In the description field of the pull request enter a summary for the changes you made. If there is already a work package on https://community.openproject.org you can also add this to the description with its complete URL. This adds a relation between your pull request and the work package.
+In the description field of the pull request enter a summary for the changes you made. If there is already a work package on [community.openproject.org](https://community.openproject.org) you can also add this to the description with its complete URL. This adds a relation between your pull request and the work package.

 Once you have made all the changed and are certain that these are final, you can request a review.

@@ -173,7 +173,7 @@ If a new release branch is generated on the upstream opf/openproject repository,

 ### A) Change Remote Repository to UPSTREAM

-In GitHub Desktop choose menu "Repository -> Repository settings". This will open a new window (screenshot below). Enter the URL of the upstream/original OpenProject repository (e.g. https://github.com/opf/openproject.git). Confirm with **Save**
+In GitHub Desktop choose menu "Repository -> Repository settings". This will open a new window (screenshot below). Enter the URL of the upstream/original OpenProject repository (e.g. `https://github.com/opf/openproject.git`). Confirm with **Save**

 ![rebase-your-fork-step-1](rebase-your-fork-step-1.png)

@@ -185,7 +185,7 @@ In GitHub Desktop **at Current branch the old branch is visible [1]** . After yo

 ### C) Change remote repository back to the forked repository (ORIGIN)

-In Github Desktop choose menu "Repository -> Repository settings". This will open a new window (screenshot below). Enter the URL of your forked OpenProject repository (e.g. https://github.com/adam-op/openproject.git). Confirm with **Save**
+In Github Desktop choose menu "Repository -> Repository settings". This will open a new window (screenshot below). Enter the URL of your forked OpenProject repository (e.g. `https://github.com/adam-op/openproject.git`). Confirm with **Save**

 ![rebase-your-fork-step-3](rebase-your-fork-step-3.png)

@@ -221,8 +221,8 @@ Example for an unordered list:

 - Do not add commas (`,`) or semicolons (`;`) to the ends of list items.
 - Separate list items from explanatory text with a colon (`:`). For example:
-    - Feature 1: very attractive new feature
-    - Feature 2: description of an additional feature
+  - Feature 1: very attractive new feature
+  - Feature 2: description of an additional feature

 ## Tables

@@ -335,7 +335,6 @@ Use images to help the reader understand where they are in a process, or how the
 When you take screenshots:

 - Capture the most relevant area: Do not include unnecessary blank space or areas of the page that do not help illustrate the point. The project menu on the left of the OpenProject application can change, so don’t include it unless it is necessary.
-
 - Be consistent: Coordinate screenshots with the other screenshots already on a documentation page. For example, if other screenshots include the left sidebar, include the sidebar in all screenshots.

 ### Highlight specific areas and add numbered labels
@@ -358,13 +357,12 @@ When referring to the numbered labels in the documentation text, use either an o

 ### Save images

+- Prefer PNG format for images. Use JPG only if the image is a photo or if the PNG file size exceeds 200 KB.
+- Try to compress your image with a tool like [squoosh](https://squoosh.app/) with `OxiPNG` or `MozJPEG`.
 - Save the image with a file name that describes the image. Use lower cases and no spaces (see [file names requirements](#directory-and-file-names)).
-
- Make sure to not exceed the maximum image size of 200KB.
-
+- Make sure to not exceed the maximum image size of **200 KB**.
 - Place your images in the same directory where the README.md document that you are working on is located.
-
- Compress GIFs, maximum size 250KB.
+- Compress GIFs, maximum size **2 MB**.

 ### Add the image link to content

@@ -63,7 +63,7 @@ Help OpenProject reach more users by engaging with our content and sharing it wi
 - **Add a backlink to your website**
  Include a link to OpenProject’s website on your blog, portfolio, or company website to help more people discover our tool.
 - **Write a Review**
-  Share your thoughts about OpenProject on one of our review platforms. [Leave a review ](https://www.openproject.org/reviews/).
+  Share your thoughts about OpenProject on one of our review platforms. [Leave a review](https://www.openproject.org/reviews/).

 ## Spread the word

@@ -60,8 +60,8 @@ Once a translation has been provided, a proof reader can approve the translation

 ## Becoming a proof reader

-If you are interested in becoming a proof reader, please contact one of the project managers in the OpenProject CrowdIn project or send us an email at support@openproject.org.
+If you are interested in becoming a proof reader, please contact one of the project managers in the OpenProject CrowdIn project or send us an email at [support@openproject.com](mailto:support@openproject.com).

-If your language is not listed in the list of CrowdIn languages, please contact our project managers or send us an email so we can add your language.
+If your language is not listed in the list of CrowdIn languages, please contact our project managers or email us so we can add your language.

 Find out more about our development concepts regarding translations [here](../../development/concepts/translations).
@@ -10,7 +10,7 @@ We are pleased that you are thinking about contributing to OpenProject! This gui

 ## Get in touch

-Please get in touch with us using our [development forum](https://community.openproject.org/projects/openproject/forums/7) or send us an email to info@openproject.org.
+Please get in touch with us using our [development forum](https://community.openproject.org/projects/openproject/forums/7) or send us an email to [info@openproject.org](mailto:info@openproject.org).

 ## Issue tracking and coordination

@@ -70,7 +70,7 @@ We want to keep the Pull request list as cleaned up as possible - we will aim cl

 ## Security

-If you notice a security issue in OpenProject, please send us a GPG encrypted email to security@openproject.com and describe the issue you found. Download our public GPG key BDCF E01E DE84 EA19 9AE1 72CE 7D66 9C6D 4753 3958 [here](https://keys.openpgp.org/vks/v1/by-fingerprint/BDCFE01EDE84EA199AE172CE7D669C6D47533958).
+If you notice a security issue in OpenProject, please send us a GPG encrypted email to [security@openproject.com](mailto:security@openproject.com) and describe the issue you found. Download our public GPG key BDCF E01E DE84 EA19 9AE1 72CE 7D66 9C6D 4753 3958 [here](https://keys.openpgp.org/vks/v1/by-fingerprint/BDCFE01EDE84EA199AE172CE7D669C6D47533958).

 Please include a description on how to reproduce the issue if possible. Our security team will get your email and will attempt to reproduce and fix the issue as soon as possible.

@@ -142,9 +142,9 @@ This list is not conclusive but rather serves to highlight the difference to the

 OpenProject embeds some release information into the packages and containers to ensure they are traceable. For all containers, the following files exist under `/app`. For packages, these files reside under `/opt/openproject/` and `/opt/openproject/config`, depending on the used version.

- **CORE_VERSION**: Reference to the commit of the https://github.com/opf/openproject core repository of OpenProject that is the foundation of the build
+- **CORE_VERSION**: Reference to the commit of the [core repository of OpenProject](https://github.com/opf/openproject) that is the foundation of the build
 - **CORE_URL** URL to the commit at GitHub for easier reference
- **PRODUCT_VERSION** Commit of the flavour/product version. In case of the [openDesk container](https://hub.docker.com/r/openproject/open_desk), contains a reference to the openDesk repository https://github.com/opf/openproject-open_desk
+- **PRODUCT_VERSION** Commit of the flavour/product version. In case of the [openDesk container](https://hub.docker.com/r/openproject/open_desk), contains a reference to the [openDesk repository](https://github.com/opf/openproject-open_desk)
 - **BUILDER_VERSION** Internal reference of the building CI repository that we use to create and publish the images.

 ### Support of releases
@@ -64,7 +64,7 @@ Before requesting a review, double check your own changes:
 - Are they complete? Did you add that spec Did you take a look at the diff yourself?
 - Did you forget to remove any temporary code, debugging steps, or similar?

-Once your pull request is ready to be reviewed, convert it from a draft and add the label `needs review`. You can bookmark this query to always show all pull requests recently marked as reviewable: https://github.com/opf/openproject/pulls?q=is%3Aopen+is%3Apr+label%3A%22needs+review%22
+Once your pull request is ready to be reviewed, convert it from a draft and add the label `needs review`. You can bookmark this query to always show all pull requests recently [marked as reviewable](https://github.com/opf/openproject/pulls?q=is%3Aopen+is%3Apr+label%3A%22needs+review%22)

 Do not explicitly request people or groups as reviewers unless you have collaborated with them already, or have a good reason to request specific feedback.

@@ -211,7 +211,7 @@ export class ExampleComponent implements OnInit {

 There is one more class involved in this stack, the `EditFieldHandler`. It implements an adapter pattern to break the connection between the input-only characteristics of the `EditFieldComponent` and the handling of events towards an outer wrapper such as the `EditForm`. They are regular classes that handle events from the `EditFieldComponent` to make them reusable in cases where, for example, an `EditForm` does not exist.

-Any user event that should trigger saving or resetting of the field is being handled by the `EditFieldHandler`, hence its name. For example, pressing <kbd>ESC</kbd> on a `TextEditFieldComponent` will trigger the `EditFieldHandler#handleUserCancel` method. The same is true for submit events on the field or form (e.g., pressing <kbd>ENTER</kbd> on the field), which trigger the `EditFieldHandler#handleUserSubmit` method.
+Any user event that should trigger saving or resetting of the field is being handled by the `EditFieldHandler`, hence its name. For example, pressing \<kbd\>ESC\<\/kbd\> on a `TextEditFieldComponent` will trigger the `EditFieldHandler#handleUserCancel` method. The same is true for submit events on the field or form (e.g., pressing \<kbd\>ENTER\<\/kbd\> on the field), which trigger the `EditFieldHandler#handleUserSubmit` method.

 An example where this comes into play is the [`CustomText`](https://github.com/opf/openproject/tree/dev/frontend/src/app/shared/components/grids/widgets/custom-text/custom-text.component.ts) widget of the dashboards and My page, which use the `<edit-form-portal>` manually and pass in a handler that handles saving of these widgets without access to an edit form.

@@ -61,10 +61,10 @@ The way a developer can check for permissions obviously depends on whether the b

 While not the case throughout the application, permissions:

- * should be checked in the Contracts whenever wanting to change a record. This also includes the values that are assignable (e.g. which users are available to become assignee of a work package)
- * should be applied to scopes whenever fetching a set of records. Even when only fetching an individual record it is best to apply a scope checking the visibility before the `find` instead of fetching the record first and then check for the visibility.
- * needs unfortunately to be checked in the view/representers whenever an attribute is visible for one group of users but not for another.
- * should **not** be checked in the controller layer unless an explicit 403 response needs to be returned.
+* should be checked in the Contracts whenever wanting to change a record. This also includes the values that are assignable (e.g. which users are available to become assignee of a work package)
+* should be applied to scopes whenever fetching a set of records. Even when only fetching an individual record it is best to apply a scope checking the visibility before the `find` instead of fetching the record first and then check for the visibility.
+* needs unfortunately to be checked in the view/representers whenever an attribute is visible for one group of users but not for another.
+* should **not** be checked in the controller layer unless an explicit 403 response needs to be returned.

 ### Controller `before_action`

@@ -36,9 +36,9 @@ The `ResourceChangeset` class is a temporarily created class whose lifetime is d

 The changeset maintains references to

- * The source HAL resource (a pristine, unchanged version) such as a work package
- * The actual `Changeset` object of changes (basically a map of `attribute -> values` of changes)
- * The `FormResource` for the resource (due to temporary changes such as switching types or projects in work packages)
+* The source HAL resource (a pristine, unchanged version) such as a work package
+* The actual `Changeset` object of changes (basically a map of `attribute -> values` of changes)
+* The `FormResource` for the resource (due to temporary changes such as switching types or projects in work packages)

 The changeset provides a high level access to getting and writing changes as well as caching resources around editing to avoid reloading them too often. It also provides access to a `projectedResource`, which is a proxy class on the HAL resource with all overridden values returned from the changeset. It behaves as if the modified resource was saved and returned.

@@ -69,9 +69,8 @@ OpenProject recommends these authentication mechanisms:

 **References**

-https://cheatsheetseries.owasp.org/cheatsheets/Authentication_Cheat_Sheet.html
-
-https://guides.rubyonrails.org/security.html
+- https://cheatsheetseries.owasp.org/cheatsheets/Authentication_Cheat_Sheet.html
+- https://guides.rubyonrails.org/security.html

 ### Session Management

@@ -109,7 +108,7 @@ As OpenProject is a web application, the web session is the central mechanism of

 **References**

-https://cheatsheetseries.owasp.org/cheatsheets/Session_Management_Cheat_Sheet.html
+- https://cheatsheetseries.owasp.org/cheatsheets/Session_Management_Cheat_Sheet.html

 ## Authorization and Access Control

@@ -131,9 +130,8 @@ At its core, permissions in OpenProject are the central key to determine who can

 **References**

-https://cheatsheetseries.owasp.org/cheatsheets/Authorization_Cheat_Sheet.html
-
-https://guides.rubyonrails.org/security.html
+- https://cheatsheetseries.owasp.org/cheatsheets/Authorization_Cheat_Sheet.html
+- https://guides.rubyonrails.org/security.html

 ## User Input Validation

@@ -158,13 +156,10 @@ OpenProject is a form-driven application, meaning that users input a lot of data

 **References**

-https://guides.rubyonrails.org/security.html#injection
-
-https://owasp.org/www-community/Types_of_Cross-Site_Scripting#stored-xss-aka-persistent-or-type-i
-
-https://cheatsheetseries.owasp.org/cheatsheets/Injection_Prevention_Cheat_Sheet.html
-
-https://cheatsheetseries.owasp.org/cheatsheets/Input_Validation_Cheat_Sheet.html
+- https://guides.rubyonrails.org/security.html#injection
+- https://owasp.org/www-community/Types_of_Cross-Site_Scripting#stored-xss-aka-persistent-or-type-i
+- https://cheatsheetseries.owasp.org/cheatsheets/Injection_Prevention_Cheat_Sheet.html
+- https://cheatsheetseries.owasp.org/cheatsheets/Input_Validation_Cheat_Sheet.html

 ## Virus and Malware protection

@@ -214,9 +209,8 @@ Inconsiderate use of error handling, logging, and monitoring mechanisms of a web

 **References**

-https://cheatsheetseries.owasp.org/cheatsheets/Error_Handling_Cheat_Sheet.html
-
-https://cheatsheetseries.owasp.org/cheatsheets/Logging_Cheat_Sheet.html
+- https://cheatsheetseries.owasp.org/cheatsheets/Error_Handling_Cheat_Sheet.html
+- https://cheatsheetseries.owasp.org/cheatsheets/Logging_Cheat_Sheet.html

 ## External dependencies

@@ -243,7 +237,7 @@ OpenProject includes a number of external dependencies both in Ruby as well as i

 **References**

-https://cheatsheetseries.owasp.org/cheatsheets/Vulnerable_Dependency_Management_Cheat_Sheet.html
+- https://cheatsheetseries.owasp.org/cheatsheets/Vulnerable_Dependency_Management_Cheat_Sheet.html

 ## Packaging and containerization

@@ -11,7 +11,7 @@ keywords: Stimulus, Ruby on Rail, Hotwire

 In a decision to move OpenProject towards the [Hotwire approach](https://hotwired.dev/), we introduced [Stimulus.js](https://stimulus.hotwired.dev) to replace a collection of dynamically loaded custom JavaScript files used to sprinkle some interactivity.

-This guide will outline how to add controllers and the conventions around it. This is _not_ a documentation of stimulus itself. Use their documentation instead: https://stimulus.hotwired.dev
+This guide will outline how to add controllers and the conventions around it. This is _not_ a documentation of stimulus itself. Use their [documentation](https://stimulus.hotwired.dev) instead.

 ## Adding controllers

@@ -161,10 +161,9 @@ _CAVEAT: npm dependencies for hybrid plugins are not yet resolved._

 **To use a hybrid plugin:**

-  * declare the dependency in `Gemfile.plugins` within the `:opf_plugins` group
-    using the Bundler DSL.
-
-  * then run `bundle install`.
+* declare the dependency in `Gemfile.plugins` within the `:opf_plugins` group
+  using the Bundler DSL.
+* then run `bundle install`.

 Provided Ruby Bundler is aware of these plugins, Webpack (our node-based build pipeline)
 will bundle their assets.
@@ -173,7 +173,7 @@ are cached in a docker volume. Meaning that from the 2nd run onwards it will sta

 Wait until you see `✔ Compiled successfully.` in the frontend logs and the success message from Puma in the backend
 logs. This means both frontend and backend have come up successfully. You can now access OpenProject
-under http://localhost:3000, and via the live-reloaded under http://localhost:4200.
+under `http://localhost:3000`, and via the live-reloaded under `http://localhost:4200`.

 Again the first request to the server can take some time too. But subsequent requests will be a lot faster.

@@ -222,7 +222,7 @@ Adding additional external docker networks to the test services like `backend-te
 `docker-compose.override.yml`) breaks the functionality of the Selenium service. This results in failing tests running
 inside a Selenium context, like feature and UI tests.

-```
+```text
 Selenium::WebDriver::Error::UnknownError:
  unknown error: net::ERR_CONNECTION_REFUSED
    (Session info: chrome=130.0.6723.91)
@@ -24,6 +24,6 @@ We always appreciate early feedback from the Community:

 No matter if you have been using OpenProject for years or just logged in this week, we want to hear from you. Everyone can contribute.

-Please get in touch via: info@openproject.com and let us know how you would like to contribute.
+Please get in touch via: [info@openproject.com](mailto:info@openproject.com) and let us know how you would like to contribute.

 Thank you.
@@ -14,9 +14,9 @@ This guide will provide some insights in how to develop and test integrations wi

 The packager.io website observes changes in the repository through webhooks and will automatically triggers builds for these branches:

- `dev`: https://packager.io/gh/opf/openproject
- `release/*` (e.g.,) https://packager.io/gh/opf/openproject/refs/release/13.0
- `stable/*` (e.g.,) https://packager.io/gh/opf/openproject/refs/stable/15
+- `dev`: `https://packager.io/gh/opf/openproject`
+- `release/*` (e.g.,) `https://packager.io/gh/opf/openproject/refs/release/13.0`
+- `stable/*` (e.g.,) `https://packager.io/gh/opf/openproject/refs/stable/15`
 - `packaging/*`

 To see the status of a build, simply follow one of the links and choose a distribution whose logs you want to look at.
@@ -37,8 +37,8 @@ In an installed installations, these are the paths you have to look for:

 If you need a package of your changes before they are being merged, simply create a branch with the prefix `packaging/` to allow it being build.

-Then, trigger its builds using this URL: `https://packager.io/gh/opf/openproject/refs/BRANCH-NAME`. For example: https://packager.io/gh/opf/openproject/refs/packaging/custom-plugin-frozen
+Then, trigger its builds using this URL: `https://packager.io/gh/opf/openproject/refs/BRANCH-NAME`. For example: `https://packager.io/gh/opf/openproject/refs/packaging/custom-plugin-frozen`

-If you're pushing multiple commits and want faster turnover times, reduce the number of available distributions in the `.pkgr.yml` to only the ones you want to test here: https://github.com/opf/openproject/blob/dev/.pkgr.yml
+If you're pushing multiple commits and want faster turnover times, reduce the number of available distributions in the `.pkgr.yml` to only the ones you want to test [here](https://github.com/opf/openproject/blob/dev/.pkgr.yml).

 **Important:** Remember to remove those changes before merging!
@@ -284,10 +284,8 @@ Developed features are bundled into a version that is released to the public via
 3. QA identifies important bugs to be fixed in the release.
 4. Developer fixes bugs from regression testing as well as bugs from former versions.
 5. Tester retests bugs
-
-  * Tester adjusts status on errors (status: “test failed").
-  * Tester adjusts status when no errors are found (status: “closed").
-
+   - Tester adjusts status on errors (status: “test failed").
+   - Tester adjusts status when no errors are found (status: “closed").
 6. Developer fixes bugs that were not fixed successfully.
 7. DevOps deploys release candidate on community.openproject.org.
 8. DevOps monitors for failures.
@@ -144,7 +144,7 @@ Sanity and regression tests are manually performed tests by QA for relevant comp

 **Usage at OpenProject**

-For writing and executing manual sanity and regression testing, especially focusing on functional requirements, one of the tools in use at OpenProject is TestLink (https://testlink.org/) to achieve the following goals:
+For writing and executing manual sanity and regression testing, especially focusing on functional requirements, one of the tools in use at OpenProject is [TestLink](https://testlink.org/) to achieve the following goals:

 - Test cases have clear preconditions so that the tester prepares for executing each case with enough knowledge about requirements.
 - Test cases are as specific as possible. They should check the proper working of one single point/case and should therefore have no more than 8-10 steps.
@@ -16,11 +16,12 @@ Declarative Programming is a paradigm where the code describes **what to do** by

 #### What

-* Encapsulate logic in methods with meaningful names.
-    * Domain/Business logic: \
-Encapsulate the implementation details in the subdomain service (e.g., login should be placed in the AuthService and encapsulate all the login functionality).
-    * Presentation or interaction logic: \
-Encapsulate the implementation details in a component’s method or in a Presenter (service scoped/provided in the component).
+Encapsulate logic in methods with meaningful names.
+
+* Domain/Business logic: \
+  Encapsulate the implementation details in the subdomain service (e.g., login should be placed in the AuthService and encapsulate all the login functionality).
+* Presentation or interaction logic: \
+  Encapsulate the implementation details in a component’s method or in a Presenter (service scoped/provided in the component).

 #### Example

@@ -177,8 +178,8 @@ Are state and logic containers.
 ##### What

 * Encapsulate logic in services:
-    * State (Store) + Domain logic (state CRUD)
-    * Complex UI logic (Presenters)
+  * State (Store) + Domain logic (state CRUD)
+  * Complex UI logic (Presenters)
 * Provide a meaningful API to access the state and logic.
 * Follow the unidirectional data flow pattern

@@ -200,11 +201,11 @@ Represent a feature that interacts with the state. This could be a page (routed
 * Inject the State Services (Stores).
 * Contain Presentational Components (PC), usually.
 * Bridge State Services (Stores) and PCs:
-    * Pass down state updates (from Stores) through PCs’ @Outputs
-    * React to PCs’ @Outputs
+  * Pass down state updates (from Stores) through PCs’ @Outputs
+  * React to PCs’ @Outputs
 * Notes:
-    * Could contain other CCs.
-    * Could contain presentational logic (show/hide PCs, calculations..), in those cases are named something like Mixed Components.
+  * Could contain other CCs.
+  * Could contain presentational logic (show/hide PCs, calculations..), in those cases are named something like Mixed Components.

 ##### Example

@@ -212,7 +213,7 @@ Pages, components that are routed, are usually container components since the ne

 ##### What

-* Concentrate the interaction with the state (Stores) in Container Components.
+Concentrate the interaction with the state (Stores) in Container Components.

 ##### Why

@@ -231,12 +232,12 @@ Are the building blocks of the UI.

 * Present/display state that is passed via @Inputs.
 * Handle user interaction:
-    * Implement the interaction logic
-    * Emit @Outputs
+  * Implement the interaction logic
+  * Emit @Outputs
 * Notes:
-    * Could contain:
-        * Other Presentational Components and Container Components.
-        * Presenter Services that encapsulate complex UI logic (computed styles, UI calculations...)).
+  * Could contain:
+    * Other Presentational Components and Container Components.
+    * Presenter Services that encapsulate complex UI logic (computed styles, UI calculations...)).

 ##### Example

@@ -250,11 +251,11 @@ Components from UI libraries are usually Presentational Components (e.g., [mater

 * Reusability: \
 Presentational components are more reusable because:
-    * Are not tied to a concrete business logic.
-    * Usually perform a generic interaction/presentation (button, tab, list, layout)
+  * Are not tied to a concrete business logic.
+  * Usually perform a generic interaction/presentation (button, tab, list, layout)
 * Increase
-    * Productivity
-    * Standardization
+  * Productivity
+  * Standardization
 * Align with Design Systems
 * Improved testability because there are no side effects (pure).
 * Are easier to replace.
@@ -266,7 +267,7 @@ Clean code is easily readable, understandable, changeable, extensible, scalable
 #### What

 * Do follow clean [patterns and rules](https://github.com/labs42io/clean-code-typescript)
-    * [Summary of the Clean Code principles](https://gist.github.com/wojteklu/73c6914cc446146b8b533c0988cf8d29)
+* [Summary of the Clean Code principles](https://gist.github.com/wojteklu/73c6914cc446146b8b533c0988cf8d29)

 #### Why

@@ -279,6 +280,7 @@ Clean code is easily readable, understandable, changeable, extensible, scalable

 #### What

-* Do follow BEM directives:
-    * [https://en.bem.info/methodology/css/](https://en.bem.info/methodology/css/)
-    * [https://en.bem.info/methodology/html/](https://en.bem.info/methodology/html/)
+Do follow BEM directives:
+
+* [https://en.bem.info/methodology/css/](https://en.bem.info/methodology/css/)
+* [https://en.bem.info/methodology/html/](https://en.bem.info/methodology/html/)
@@ -36,8 +36,8 @@ keywords: feature requests, ideas, open feature request

 **Example:**

-AS an OpenProject user<br>
-I WANT to only show the allowed status fields as active for which a status transition is allowed based on the workflow<br>
+AS an OpenProject user  
+I WANT to only show the allowed status fields as active for which a status transition is allowed based on the workflow  
 SO THAT I am clearly aware which status transitions are allowed before doing them.

 ### Acceptance criteria
@@ -10,20 +10,20 @@ keywords: backups

 ## Data retention policy

-Your Enterprise cloud data is continuously backed up and retained for 30 days. Within this period, we can restore your data to any point in time with a precision of 5 minutes if needed. 
+Your Enterprise cloud data is continuously backed up and retained for 30 days. Within this period, we can restore your data to any point in time with a precision of 5 minutes if needed.
+
 > [!NOTE]
 > Currently, this applies only to cloud instances located in the openproject.com cloud environment.

 > [!IMPORTANT]
-> At the moment, it is only possible to restore the **entire instance** to a previous state. Any changes made after the restored point will be lost.
->  
+> At the moment, it is only possible to restore the **entire instance** to a previous state. Any changes made after the restored point will be lost.  
 > To help you recover lost information, the restored version will be temporarily available at a separate URL. This allows you to manually transfer the necessary data back to your production instance using **API calls or manual entry**. You will have as much time as needed to complete this process.

 ## Resource limitations for attachments

 In the Enterprise cloud, backups can only include attachments if the total file size of all attachments is less than 1 GB.

-If your attachments exceed this limit, please contact us at support@openproject.com to manually request a complete backup, which includes an SQL dump with all attachments. Alternatively, consider deleting unused attachments to reduce your data usage below 1 GB.
+If your attachments exceed this limit, please contact us at [support@openproject.com](mailto:support@openproject.com) to manually request a complete backup, which includes an SQL dump with all attachments. Alternatively, consider deleting unused attachments to reduce your data usage below 1 GB.

 If the total attachment size exceeds 1 GB, the **Include attachments** checkbox will be disabled, as shown in the screenshot below:

@@ -66,11 +66,9 @@ To select the **Pay per invoice** option, select the respective checkbox. This w
 Enter your **Billing information**. If you are a business customer from the EU, please enter a valid **VAT ID number**.

 > [!TIP]
->
 > Make sure to validate your billing email to receive the required information and invoice.

 > [!IMPORTANT]
->
 > You have to **agree to our terms of services and privacy policy**.

 Click the **Subscribe** button.
@@ -20,7 +20,7 @@ If you are currently on a lower plan for the Enterprise cloud and want to test a

 ### Can I get a custom domain name instead of example.openproject.com?

-Yes, you can create your custom domain name. For this service we charge €100 per month. Please contact us via email (sales@openproject.com) if you are interested.
+Yes, you can create your custom domain name. For this service we charge €100 per month. Please contact us via email [support@openproject.com](mailto:support@openproject.com) if you are interested.

 ### How can I change the OpenProject Enterprise cloud creators account?

@@ -61,7 +61,7 @@ The user may terminate the contract at any time, which will apply by the end of

 ### What shall I do when I run into payment issues with OpenProject?

-In case you use the bank transfer payment method please indicate the invoice number. You can find this information in the corresponding invoice (OP…). Otherwise the automatic banking system is not able to detect your payment. Please do not hesitate to contact billing@openproject.com if you have any further questions.
+In case you use the bank transfer payment method please indicate the invoice number. You can find this information in the corresponding invoice (OP…). Otherwise the automatic banking system is not able to detect your payment. Please do not hesitate to contact [billing@openproject.com](mailto:billing@openproject.com) if you have any further questions.

 You can find additional questions and answers regarding pricing and booking at the bottom of our [pricing website](https://www.openproject.org/pricing/#faq).

@@ -85,7 +85,7 @@ If you are having trouble accessing the files on your server with your browser,

 ### How can I export the documents loaded on OpenProject?

-Currently, there is unfortunately no option to export all the documents in OpenProject at once. We could manually export the entire database (including the attachments) for you. Due to the manual effort, we would however need to charge a service fee for this. Please contact sales@openproject.com.
+Currently, there is unfortunately no option to export all the documents in OpenProject at once. We could manually export the entire database (including the attachments) for you. Due to the manual effort, we would however need to charge a service fee for this. Please contact [support@openproject.com](mailto:support@openproject.com).

 ### Is it possible to access the PostgreSQL tables (read-only) on a hosted OpenProject instance via ODBC or another protocol (e.g. to extract data for PowerBI)?

@@ -8,4 +8,4 @@ keywords: enterprise cloud, status, incidents

 # OpenProject cloud status page

-The following status page provides updates on outages, maintenance announcements, and service degradations for our Enterprise cloud customers: https://status.openproject.com/
+The following status page provides updates on outages, maintenance announcements, and service degradations for our Enterprise cloud customers: [status.openproject.com](https://status.openproject.com/).
@@ -33,7 +33,7 @@ Find more information [here](https://www.openproject.org/blog/enterprise-edition

 ## How can I book additional users?

-Please use the link "Manage subscription" in the email you received confirming your subscription or contact sales@openproject.com.
+Please use the link "Manage subscription" in the email you received confirming your subscription or contact [support@openproject.com](mailto:support@openproject.com).

 ## Is it possible to only upgrade *some* users to the Enterprise edition?

@@ -314,7 +314,7 @@ If in doubt on how you should start, you can also just [contact us](https://www.

 ### How can I receive support?

-We offer our Professional Support for Enterprise on-premises users and Enterprise cloud users. Please write an email to support@openproject.com.
+We offer our Professional Support for Enterprise on-premises users and Enterprise cloud users. Please write an email to [support@openproject.com](mailto:support@openproject.com).

 If you use the Community edition please feel free to use our [forums](https://community.openproject.org/projects/openproject/forums) for exchange with other users.

@@ -10,10 +10,13 @@ keywords: Agile Boards

 This document provides an initial introduction to the boards in OpenProject, i.e. how to use a Kanban board to manage your tasks in an agile way.

-> **Note**:  The basic agile boards are included in the OpenProject Community edition.  OpenProject advanced Action boards are an Enterprise add-on 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.
+> [!NOTE]
+> The basic agile boards are included in the OpenProject Community edition. OpenProject advanced Action boards are an Enterprise add-on 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.

 <div class="glossary">
+
 **Boards** in OpenProject enable agile project management, i.e. Kanban. Boards consist of lists (columns) with cards (work packages) on it. They help to visualize work, limit work-in-progress, and maximize efficiency (or flow).
+
 </div>

 To find out more about the detailed functionalities of Boards, please visit our [user guide for boards](../../user-guide/agile-boards).
@@ -11,7 +11,9 @@ keywords: invite members, add users
 In order to see a project and work in it, you have to be a member of a project. Therefore, you have to **add team members to a project**.

 <div class="glossary">
+
 **Member** is defined as a project member in a project. Project members are added in the Members module in the project menu.
+
 </div>

 > **Note**: If you are not a member of a project, you do not see the project in the Project selection nor in the project list.
@@ -63,8 +63,11 @@ If you click the dots on the lower right hand corner in a widget you can change
 You can configure the view of a work package widget to have the information included that you need.

 <div class="glossary">
+
 **Work package** is a subset of a project that can be assigned to users for execution, such as Tasks, Bugs, User Stories, Milestones, and more. Work packages have a type, an ID and a subject and may have additional attributes, such as assignee, responsible, story points or target version. Work packages are displayed in a project timeline (unless they are filtered out in the timeline configuration) - either as a milestone or as a phase. In order to use the work packages, the work package module has to be activated in the project settings.
+
 </div>
+
 ![change the size of a widget](change-size-of-widget.gif)

 On a work package widget, click on the button with the three dots and select **Configure view...**
@@ -10,8 +10,10 @@ keywords: open project, create project, projects introduction
 Get an introduction how to work with projects in OpenProject. To start collaboration in OpenProject, you first have to set up a new project.

 <div class="glossary">
+
 A **project** is defined as a temporary, goal-driven effort to create a unique output. A project has clearly defined phases, a start and an end date, and its success is measured by whether it meets its stated objectives.
 A project in OpenProject can be understood as a project as defined above. Also, it can be set up as a "workspace" for teams to collaborate on one common topic, e.g. to organize a department.
+
 </div>

 > **Note**: In order to see a project and work in it, you have to be a [member of the project](../invite-members).
@@ -36,8 +38,11 @@ You can also start typing in a project name to filter by the project's title.
 Projects and subprojects are displayed according to their hierarchy in the drop-down menu.

 <div class="glossary">
+
 **Subproject** is defined as a child project of another project. Subprojects can be used to display a hierarchy of projects. Several filter options (e.g. in work package table and timeline) can be applied only to the current project and its subprojects.
+
 </div>
+
 ![project_hierarchy](project_hierarchy-8178054.png)

 Alternatively, you can open the list of all existing projects using the [**Global modules**](../../user-guide/home/global-modules/#projects) menu.
@@ -222,6 +222,7 @@ Internal comments are available as [Enterprise add-on](#enterprise-add-on) in Op
 Macros in OpenProject are dynamic shortcuts that help automate repetitive tasks. They work in editors like [work package](#work-package) descriptions, [wikis](#wiki) or [forums](#forum). For example, users can type 'workPackageValue:1234:subject' into a work package description and once saved, OpenProject will display the title of the work package with the ID 1234.

 **More information on macros in OpenProject**
+
 - [See a list of all possible work package attributes that can be used as macros in OpenProject](../user-guide/wysiwyg/#available-attributes-for-work-packages)
 - [Read a blog article with detailed descriptions and examples on how to use macros in OpenProject](https://www.openproject.org/blog/how-to-use-macros/)
 - [Learn about options for using macros in OpenProject's wikis](../user-guide/wiki/#macros)
@@ -9,7 +9,7 @@ sidebar_navigation:
 OpenProject can be configured via environment variables. These are often helpful for automatically deploying production systems.

 > [!NOTE]
-> This documentation is for OpenProject on-premises Installations only, if you would like to setup similar in your OpenProject cloud instance, please contact us at support@openproject.com
+> This documentation is for OpenProject on-premises Installations only, if you would like to setup similar in your OpenProject cloud instance, please contact us at [support@openproject.com](mailto:support@openproject.com)

 > [!IMPORTANT]
 > Using the configuration file `config/configuration.yml` is deprecated and is **NOT** recommended anymore
@@ -38,7 +38,7 @@ Configuring OpenProject through environment variables is described in detail [in

 ### One container per process installation

-Create a file `docker-compose.override.yml` next to `docker-compose.yml` file. Docker Compose will automatically merge those files, for more information, see https://docs.docker.com/compose/multiple-compose-files/merge/.
+Create a file `docker-compose.override.yml` next to `docker-compose.yml` file. Docker Compose will automatically merge those files, for more information, [see](https://docs.docker.com/compose/multiple-compose-files/merge/).
 Add your custom configuration to `docker-compose.override.yml`.

 In the compose folder you will also find the file `docker-compose.yml` which shall **NOT** be edited.
@@ -320,8 +320,8 @@ OPENPROJECT_SEED_DESIGN_EXPORT__COVER="..."

 ### Allowing public access

-By default, any request to the OpenProject application needs to be authenticated. If you want to enable public unauthenticated access like we do for https://community.openproject.org, you can set the `login_required` to `false`. If not provided through environment variables, this setting is also accessible in the administrative UI. Please see the [authentication settings guide](../../system-admin-guide/authentication/login-registration-settings/) for more details.
-
+By default, any request to the OpenProject application needs to be authenticated. If you want to enable public unauthenticated access like we do for community.openproject.org, you can set the `login_required` to `false`. If not provided through environment variables, this setting is also accessible in the administrative UI. Please see the [authentication settings guide](../../system-admin-guide/authentication/login-registration-settings/) for more details.
+å
 *default: true*

 To disable, set the configuration option:
@@ -460,7 +460,7 @@ OPENPROJECT_DISABLE__PASSWORD__LOGIN="true"

 ### Omniauth direct login provider

-Per default the user may choose the usual password login as well as <u>several</u> omniauth providers on the login page and in the login drop down menu. With this configuration option you can set a specific omniauth provider to be used for direct login. Meaning that the login provider selection is skipped and the configured provider is used directly (non-interactive) instead.
+Per default the user may choose the usual password login as well as **several** omniauth providers on the login page and in the login drop down menu. With this configuration option you can set a specific omniauth provider to be used for direct login. Meaning that the login provider selection is skipped and the configured provider is used directly (non-interactive) instead.

 If this option is active, a login will lead directly to the configured omniauth provider and so will a click on 'Sign in' (the drop down menu will not open).

@@ -713,7 +713,7 @@ OPENPROJECT_SECURITY__BADGE__DISPLAYED="false"

 Example: 

-```bash
+```shell
 OPENPROJECT_AFTER__LOGIN__DEFAULT__REDIRECT__URL="/my/page"
 ```

@@ -66,12 +66,6 @@ OpenProject will merge the settings from `DATABASE_URL` with manually specified
 | OPENPROJECT_DB_SSLMODE                  | Uses libpq default | https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNECT-SSLMODE |                                                              |
 | OPENPROJECT_DB_SSLCOMPRESSION           | Uses libpq default | https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNECT-SSLCOMPRESSION |                                                              |
 | OPENPROJECT_DB_SSL_MIN_PROTOCOL_VERSION | Uses libpq default | https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNECT-SSL-MIN-PROTOCOL-VERSION |                                                              |
-|                                         |                    |                                                              |                                                              |
-|                                         |                    |                                                              |                                                              |
-|                                         |                    |                                                              |                                                              |
-|                                         |                    |                                                              |                                                              |
-|                                         |                    |                                                              |                                                              |
-


 ## Using SSL/TLS with a PostgreSQL database
@@ -86,16 +80,16 @@ DATABASE_URL=postgres://user:pass@host:port/dbname?sslmode=require-full&sslcert=

 Alternatively, for better readability, you can set these parameters with separate environment variables:

-| Environment variable                    | Default                      | Description                                                  | PostgreSQL documentation                                     |
-| --------------------------------------- | ---------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
-| OPENPROJECT_DB_SSLMODE                  | prefer                       | connection mode for SSL. See                                 | [sslmode](https://www.postgresql.org/docs/13/libpq-connect.html#LIBPQ-CONNECT-SSLMODE) |
-| OPENPROJECT_DB_SSLCOMPRESSION           | 0                            | If set to 1, data sent over SSL connections will be compressed | [sslcompression](https://www.postgresql.org/docs/13/libpq-connect.html#LIBPQ-CONNECT-SSLCOMPRESSION) |
-| OPENPROJECT_DB_SSLCERT                  | ~/.postgresql/postgresql.crt | Path to certificate                                          | [sslcert](https://www.postgresql.org/docs/13/libpq-connect.html#LIBPQ-CONNECT-SSLCERT) |
-| OPENPROJECT_DB_SSLKEY                   | ~/.postgresql/postgresql.key | Path to certificate key                                      | [sslkey](https://www.postgresql.org/docs/13/libpq-connect.html#LIBPQ-CONNECT-SSLKEY) |
-| OPENPROJECT_DB_SSLPASSWORD              |                              | Password to certificate key                                  | [sslpassword](https://www.postgresql.org/docs/13/libpq-connect.html#LIBPQ-CONNECT-SSLPASSWORD) |
-| OPENPROJECT_DB_SSLROOTCERT              | ~/.postgresql/root.crt       | Path to CA                                                   | [sslrootcert](https://www.postgresql.org/docs/13/libpq-connect.html#LIBPQ-CONNECT-SSLROOTCERT) |
-| OPENPROJECT_DB_SSLCRL                   | ~/.postgresql/root.crl       | Path to revocation list                                      | [sslcrl](https://www.postgresql.org/docs/13/libpq-connect.html#LIBPQ-CONNECT-SSLCRL) |
-| OPENPROJECT_DB_SSL_MIN_PROTOCOL_VERSION | Uses libpq default           | https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNECT-SSL-MIN-PROTOCOL-VERSION |                                                              |
+| Environment variable                    | Default                      | Description                                                                                                   | PostgreSQL documentation                                     |
+| --------------------------------------- | ---------------------------- |---------------------------------------------------------------------------------------------------------------| ------------------------------------------------------------ |
+| OPENPROJECT_DB_SSLMODE                  | prefer                       | connection mode for SSL. See                                                                                  | [sslmode](https://www.postgresql.org/docs/13/libpq-connect.html#LIBPQ-CONNECT-SSLMODE) |
+| OPENPROJECT_DB_SSLCOMPRESSION           | 0                            | If set to 1, data sent over SSL connections will be compressed                                                | [sslcompression](https://www.postgresql.org/docs/13/libpq-connect.html#LIBPQ-CONNECT-SSLCOMPRESSION) |
+| OPENPROJECT_DB_SSLCERT                  | ~/.postgresql/postgresql.crt | Path to certificate                                                                                           | [sslcert](https://www.postgresql.org/docs/13/libpq-connect.html#LIBPQ-CONNECT-SSLCERT) |
+| OPENPROJECT_DB_SSLKEY                   | ~/.postgresql/postgresql.key | Path to certificate key                                                                                       | [sslkey](https://www.postgresql.org/docs/13/libpq-connect.html#LIBPQ-CONNECT-SSLKEY) |
+| OPENPROJECT_DB_SSLPASSWORD              |                              | Password to certificate key                                                                                   | [sslpassword](https://www.postgresql.org/docs/13/libpq-connect.html#LIBPQ-CONNECT-SSLPASSWORD) |
+| OPENPROJECT_DB_SSLROOTCERT              | ~/.postgresql/root.crt       | Path to CA                                                                                                    | [sslrootcert](https://www.postgresql.org/docs/13/libpq-connect.html#LIBPQ-CONNECT-SSLROOTCERT) |
+| OPENPROJECT_DB_SSLCRL                   | ~/.postgresql/root.crl       | Path to revocation list                                                                                       | [sslcrl](https://www.postgresql.org/docs/13/libpq-connect.html#LIBPQ-CONNECT-SSLCRL) |
+| OPENPROJECT_DB_SSL_MIN_PROTOCOL_VERSION | Uses libpq default           | see [here](https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNECT-SSL-MIN-PROTOCOL-VERSION) |                                                              |

 ```text
 ="prefer" # disable, allow, prefer, require, verify-ca, verify-full
@@ -107,4 +101,4 @@ Alternatively, for better readability, you can set these parameters with separat
 ="~/.postgresql/root.crl" # Path to revocation list
 ```

-PostgreSQL supports a wide variety of options in its connection string. This is not specific to OpenProject or Rails. See the following guide for more information: https://www.postgresql.org/docs/13/libpq-connect.html#LIBPQ-PARAMKEYWORDS
+PostgreSQL supports a wide variety of options in its connection string. This is not specific to OpenProject or Rails. See this [guide](https://www.postgresql.org/docs/13/libpq-connect.html#LIBPQ-PARAMKEYWORDS) for more information.
@@ -6,7 +6,7 @@ sidebar_navigation:

 # Environment variables

-> **NOTE:** This documentation is for OpenProject on-premises Installations only, if you would like to setup similar in your OpenProject cloud instance, please contact us at support@openproject.com
+> **NOTE:** This documentation is for OpenProject on-premises Installations only, if you would like to setup similar in your OpenProject cloud instance, please contact us at [support@openproject.com](mailto:support@openproject.com)

 When using environment variables, you can set the options by setting environment variables with the name of the options below in uppercase. So for example, to configure email delivery via an SMTP server, you can set the following environment variables:

@@ -77,7 +77,7 @@ Available arguments that change how the work packages are handled:

 In order to use the more secure Gmail API method, some extra initial setup in google cloud is required.

-1. Go to https://console.cloud.google.com/
+1. Go to the [Google cloud console](https://console.cloud.google.com/)
 2. Create new project
 3. Navigate to Enable APIs and Services
 4. Enable the Gmail API
@@ -87,7 +87,7 @@ In order to use the more secure Gmail API method, some extra initial setup in go
 8. Click on the new service account, go to the "Keys" tab, and add a new key.
 9. Save the JSON key file
    ***Note: Do not give anyone access to this JSON file as it contains the private key to your service account!***
-10. Go to https://admin.google.com
+10. Go to [admin.google.com](https://admin.google.com)
 11. Select Security > Access and Data Control > API Controls
 12. Go to "Domain-Wide Delegation"
 13. Add new API Client
@@ -98,13 +98,13 @@ In order to use the more secure Gmail API method, some extra initial setup in go

 Available arguments for the Gmail API rake task that specify the email behavior are

-|key | description|
-|----|------------|
-| `credentials` | Gmail service account credentials file (JSON) |
-| `username` | Gmail email address |
-| `query` | Gmail search query (https://support.google.com/mail/answer/7190?hl=en) |
-| `read_on_failure` | Mark emails as read even on failure (default: true) |
-| `max_emails` | Max emails to process (default: 1000) |
+|key | description                                                             |
+|----|-------------------------------------------------------------------------|
+| `credentials` | Gmail service account credentials file (JSON)                           |
+| `username` | Gmail email address                                                     |
+| `query` | [Gmail search query](https://support.google.com/mail/answer/7190?hl=en) |
+| `read_on_failure` | Mark emails as read even on failure (default: true)                     |
+| `max_emails` | Max emails to process (default: 1000)                                   |

 ## Format of the emails

@@ -24,7 +24,7 @@ group :opf_plugins do
 end
 ```

-**Note:** The Gitlab plugin is usually only compatible with the latest versions. For more information, please see the respective repository: https://github.com/btey/openproject-gitlab-integration/
+**Note:** The Gitlab plugin is usually only compatible with the latest versions. For more information, please see the [respective repository](https://github.com/btey/openproject-gitlab-integration/).

 The group `:opf_plugins` is generally recommended, but only required for plugins with custom frontend code that is picked up by webpack and output into their respective bundles.

@@ -293,17 +293,17 @@ Thus, if you use a separate user for Apache and OpenProject, they need to reside

 In newer versions of Git, you might see this error:

-```
+```shell
 fatal: detected dubious ownership in repository at <path>
 ```

 This happens because the owner of the repository (openproject) is not the one accessing it (www-data / web user), which is expected in this case. You will need to disable this check:

-```bash
+```shell
 git config --system --add safe.directory '*'
 ```

-Please inform yourself about the ramifications of this change. For more information, please see https://stackoverflow.com/a/73100228/420614, https://git-scm.com/docs/git-config/2.35.2#Documentation/git-config.txt-safedirectory
+Please inform yourself about the ramifications of this change. For more information, please see [stackoverflow](https://stackoverflow.com/a/73100228/420614) or [git-scm.com](https://git-scm.com/docs/git-config/2.35.2#Documentation/git-config.txt-safedirectory).

 #### Exemplary Apache Configuration

@@ -32,28 +32,21 @@ This requires your OpenProject server to be reachable using a domain name (e.g.
 1. Go to [certbot.eff.org](https://certbot.eff.org), and select "Apache" and your Linux distribution (e.g. Ubuntu 20.04) to get access to the installation instructions for your specific OS.
 2. Follow the installation instructions to get the `certbot` CLI installed.
 3. Run the `certbot` CLI to generate the certificate (and only the certificate):
-
-    ```shell
-    sudo certbot certonly --apache
-    ```
-
-  The CLI will ask for a few details and to agree to the Let's Encrypt terms of usage. Then it will perform the Let's Encrypt challenge and finally issue a certificate file and a private key file if the challenge succeeded.
-
-  At the end, it will store the certificate (`fullchain.pem`) and private key (`privkey.pem`) under `/etc/letsencrypt/live/openproject.mydomain.com/`.
-
-  You can now configure OpenProject to use them by running `openproject reconfigure`: hit ENTER until you get to the SSL wizard, and select "Yes" when the wizard asks for SSL support:
-
-  * Enter the `/etc/letsencrypt/live/openproject.mydomain.com/fullchain.pem` path when asked for the `server/ssl_cert` detail.
-  * Enter the `/etc/letsencrypt/live/openproject.mydomain.com/privkey.pem` path when asked for the `server/ssl_key` detail.
-  * Enter the `/etc/letsencrypt/live/openproject.mydomain.com/fullchain.pem` path (same as `server/ssl_cert`) when asked for the `server/ssl_ca` detail.
-
-  Hit ENTER, and after the wizard is finished your OpenProject installation should be accessible using `https://openproject.mydomain.com`.
-
+   ```shell
+   sudo certbot certonly --apache
+   ```
+   The CLI will ask for a few details and to agree to the Let's Encrypt terms of usage. Then it will perform the Let's Encrypt challenge and finally issue a certificate file and a private key file if the challenge succeeded.
+   At the end, it will store the certificate (`fullchain.pem`) and private key (`privkey.pem`) under `/etc/letsencrypt/live/openproject.mydomain.com/`.
+   You can now configure OpenProject to use them by running `openproject reconfigure`: hit ENTER until you get to the SSL wizard, and select "Yes" when the wizard asks for SSL support:
+   - Enter the `/etc/letsencrypt/live/openproject.mydomain.com/fullchain.pem` path when asked for the `server/ssl_cert` detail.
+   - Enter the `/etc/letsencrypt/live/openproject.mydomain.com/privkey.pem` path when asked for the `server/ssl_key` detail.
+   - Enter the `/etc/letsencrypt/live/openproject.mydomain.com/fullchain.pem` path (same as `server/ssl_cert`) when asked for the `server/ssl_ca` detail.
+   Hit ENTER, and after the wizard is finished your OpenProject installation should be accessible using `https://openproject.mydomain.com`.
 4. Let's Encrypt certificates are only valid for 90 days. An entry in your OS crontab should have automatically been added when `certbot` was installed. You can optionally confirm that the renewal will work by issuing the following command in dry-run mode:

-    ```shell
-    sudo certbot renew --dry-run
-    ```
+   ```shell
+   sudo certbot renew --dry-run
+   ```

 ## External SSL termination

@@ -74,4 +67,4 @@ If you're terminating SSL on the outer server, you need to set the `X-Forwarded-

 Finally, to let OpenProject know that it should create links with 'https' when no request is available (for example, when sending emails), you need to set the Protocol setting of OpenProject to `https`. You can set this configuration by setting the ENV `OPENPROJECT_HTTPS="true"`.

-_<sup>1</sup> In the packaged installation this means you selected "no" when asked for SSL in the configuration wizard but at the same time take care of SSL termination elsewhere. This can be a manual Apache setup on the same server (not recommended) or an external server, for instance._
+<sup>1</sup> In the packaged installation this means you selected "no" when asked for SSL in the configuration wizard but at the same time take care of SSL termination elsewhere. This can be a manual Apache setup on the same server (not recommended) or an external server, for instance._
@@ -470,7 +470,8 @@ After which you can access OpenProject under `http://localhost:8080`.

 If you want to connect OpenProject to an external server as example SMTP-Server or a Nextcloud-Server that uses a self-signed certificate, you need to import the root certificate that was used to create the self-signed certificate. There are two ways to archive this.

-The first way is to mount the root certificate via the ``` --mount``` option into the container and add the  certificate to the ```SSL_CERT_FILE``` variable.
+The first way is to mount the root certificate via the ```--mount``` option into the container and add the  certificate to the ```SSL_CERT_FILE``` variable.
+
 ```shell
 sudo docker run -it -p 8080:80 \
  -e OPENPROJECT_SECRET_KEY_BASE=secret \
@@ -489,6 +490,7 @@ The second way would be to build a new image of the ```openproject/openproject:1
 **2. Put your root SSL certificate** into the folder. In this example, we will name it ```my_root.crt```.

 **3. Create the `Dockerfile`** in the same folder. The contents have to look like this:
+
 ```dockerfile
 FROM openproject/openproject:15

@@ -497,6 +499,7 @@ RUN update-ca-certificates
 ```

 If you are using the -slim tag, you will need to do the following to import your root certificate:
+
 ```dockerfile
 FROM openproject/openproject:15-slim

@@ -507,6 +510,7 @@ USER $APP_USER
 ```

 **4. Build the image**
+
 ```shell
 docker build --pull -t openproject-with-custom-ca .
 ```
@@ -7,9 +7,7 @@ sidebar_navigation:
 # Install OpenProject with DEB/RPM packages

 > [!IMPORTANT]
->
 > We will not build packages for new Linux versions, such as Ubuntu 24.04. We will, however, keep releasing new package versions for the currently supported Linux versions until their EOL (end of life).
->  

 The packaged installation of OpenProject is the recommended way to install and maintain OpenProject using DEB or RPM packages.

@@ -269,9 +267,8 @@ sudo openproject configure #non-interactive - using values stored in /etc/openpr
 ```

 > [!NOTE] 
-> * Every time you will run the OpenProject wizard, by using `sudo openproject reconfigure` your choices will be persisted in a configuration file at `/etc/openproject/installer.dat` and subsequent executions of `sudo openproject configure` will re-use these values, only showing you the wizard steps for options you have not yet been asked for.
->
-> * In the interactive way you can skip dialogs you do not want to change simply by confirming them with `ENTER`.
+> Every time you will run the OpenProject wizard, by using `sudo openproject reconfigure` your choices will be persisted in a configuration file at `/etc/openproject/installer.dat` and subsequent executions of `sudo openproject configure` will re-use these values, only showing you the wizard steps for options you have not yet been asked for.
+> In the interactive way you can skip dialogs you do not want to change simply by confirming them with `ENTER`.

 ## Step 1: Select your OpenProject edition

@@ -490,7 +487,7 @@ Also, this setting will control what is the default language for new users if th

 With this last step confirmed, the OpenProject wizard will complete, and apply all the configuration options that you have just selected. This might take a few minutes depending on your machine and internet connection, as OpenProject might need to install additional packages (such as the web server, database) depending on your selections.

-In case this process crashes or exits with an obvious error, please keep the output and send your configuration from `/etc/openproject/installer.dat` (removing any passwords from it) to us at support@openproject.com , or [reach out to the community forums](https://community.openproject.org/projects/openproject/forums).
+In case this process crashes or exits with an obvious error, please keep the output and send your configuration from `/etc/openproject/installer.dat` (removing any passwords from it) to us at [support@openproject.com](mailto:support@openproject.com), or [reach out to the community forums](https://community.openproject.org/projects/openproject/forums).

 When this process completes, it will have started the internal application and web servers, the background jobs to process work-intensive jobs, and set up the connection to the database.

@@ -14,7 +14,7 @@ You need to run this migration on an OpenProject version < 13.0, as the conversi

 ## Dependencies

-We depend on `pandoc` (https://pandoc.org) for the conversion of all formattable fields in OpenProject. It provides automated means to migrate between many input and output formats, in our case from Textile to GitHub-flavored Markdown.
+We depend on [pandoc](https://pandoc.org) for the conversion of all formattable fields in OpenProject. It provides automated means to migrate between many input and output formats, in our case from Textile to GitHub-flavored Markdown.

 If you do not have an executable pandoc version of at least version 2.0 in your path, OpenProject will try download an AMD64 static linked binary for pandoc (Currently, this would be version 2.3.2). This version will be made available to OpenProject through `<OpenProject root>/vendor/pandoc` and is only used during that one-time migration step.

@@ -103,4 +103,4 @@ We're very interested in providing a smooth upgrade at all times, and would like

 **Permission errors when trying to start the OP7 container**

-If you run into permission errors trying to start the OP7 container, you might have advanced tmpfs protections in place. Disable them temporarily with `sudo sysctl fs.protected_regular=0` (https://askubuntu.com/questions/1250974)
+If you run into permission errors trying to start the OP7 container, you might have advanced tmpfs protections in place. Disable them temporarily with `sudo sysctl fs.protected_regular=0`, [see](https://askubuntu.com/questions/1250974).
@@ -39,14 +39,14 @@ sudo openproject configure

 On Ubuntu 22.04., you might see warnings like these:

-> W: https://dl.packager.io/srv/deb/opf/openproject/stable/15/ubuntu/dists/22.04/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
+> W: `https://dl.packager.io/srv/deb/opf/openproject/stable/15/ubuntu/dists/22.04/InRelease`: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.

 This message is due to Ubuntu 22.04 switching to a more secure way of adding repository sources, which is not yet supported by the repository provider. There is ongoing work on this item, the message is for information only.

 If you get an error like the following:

-> E: Repository 'https://dl.packager.io/srv/deb/opf/openproject/stable/15/ubuntu 22.04 InRelease' changed its 'Origin' value from '' to 'https://packager.io/gh/opf/openproject'
-> E: Repository 'https://dl.packager.io/srv/deb/opf/openproject/stable/15/ubuntu 22.04 InRelease' changed its 'Label' value from '' to 'Ubuntu 22.04 packages for opf/openproject'
+> E: Repository '`https://dl.packager.io/srv/deb/opf/openproject/stable/15/ubuntu` 22.04 InRelease' changed its 'Origin' value from '' to '`https://packager.io/gh/opf/openproject`'
+> E: Repository '`https://dl.packager.io/srv/deb/opf/openproject/stable/15/ubuntu` 22.04 InRelease' changed its 'Label' value from '' to 'Ubuntu 22.04 packages for opf/openproject'

 These two messages messages are expected, due to a change in Origin and Label repository metadata, to better explain what the repository is about. You should allow the change, and/or run `sudo apt-get update --allow-releaseinfo-change` for the update to go through.

@@ -97,7 +97,9 @@ If you want to perform changes to your configuration or are unsure what steps ar
 Note that this still takes previous values into consideration. Values that should not change from your previous configurations can be skipped by pressing `<Return>`. This also applies for steps with passwords, which are shown as empty even though they may have a value. Skipping those steps equals to re-use the existing value.

 ## Compose-based installation
-> **Note**: Please make sure the git repository with the docker-compose.yml file is up-to-date. If you're using an old version of the repository, the update might fail.
+
+> [!NOTE]
+> Please make sure the git repository with the docker-compose.yml file is up-to-date. If you're using an old version of the repository, the update might fail.

 When using the Compose-based docker installation, you can simply do the following:

@@ -195,21 +197,21 @@ you will need to adjust that package source.

 #### APT-based systems (Debian, Ubuntu)

- - Update the reference to `opf/openproject-ce` in `/etc/apt/sources.list.d/openproject.list` to `opf/openproject`.
- - Update the reference to `stable/8` in `/etc/apt/sources.list.d/openproject.list` to `stable/9`.
- - Perform the Upgrade steps as mentioned above in *Upgrading your OpenProject installation*
+- Update the reference to `opf/openproject-ce` in `/etc/apt/sources.list.d/openproject.list` to `opf/openproject`.
+- Update the reference to `stable/8` in `/etc/apt/sources.list.d/openproject.list` to `stable/9`.
+- Perform the Upgrade steps as mentioned above in *Upgrading your OpenProject installation*

 #### YUM-based systems (CentOS, RHEL)

- - Update the reference to `opf/openproject-ce` in `/etc/yum.repos.d/openproject.repo` to `opf/openproject`.
- - Update the reference to `stable/8` in `/etc/yum.repos.d/openproject.repo` to `stable/9`.
- - Perform the Upgrade steps as mentioned above in *Upgrading your OpenProject installation*
+- Update the reference to `opf/openproject-ce` in `/etc/yum.repos.d/openproject.repo` to `opf/openproject`.
+- Update the reference to `stable/8` in `/etc/yum.repos.d/openproject.repo` to `stable/9`.
+- Perform the Upgrade steps as mentioned above in *Upgrading your OpenProject installation*

 #### SUSE Linux Enterprise Server 12

- - Update the reference to `opf/openproject-ce` in `/etc/zypp/repos.d/openproject.repo` to `opf/openproject`.
- - Update the reference to `stable/8` in `/etc/zypp/repos.d/openproject.repo` to `stable/9`.
- - Perform the Upgrade steps as mentioned above in *Upgrading your OpenProject installation*
+- Update the reference to `opf/openproject-ce` in `/etc/zypp/repos.d/openproject.repo` to `opf/openproject`.
+- Update the reference to `stable/8` in `/etc/zypp/repos.d/openproject.repo` to `stable/9`.
+- Perform the Upgrade steps as mentioned above in *Upgrading your OpenProject installation*

 ## Upgrade notes for OpenProject 7.x to 8.x

@@ -102,8 +102,7 @@ These values are **guidelines** and should be adjusted based on actual monitorin
 - **Database**: 2-4 CPU / 8 GiB RAM
 - **CPU**: 4 CPU
 - **RAM**: 8 GB
-  **Web Workers**: 4 Workers, each with 4-8 threads
-  •
+- **Web Workers**: 4 Workers, each with 4-8 threads
 - **Background Workers**: 2 multithreaded workers with 4-6 GiB RAM
 - **Disk Space**: 50 GB + additional disk space in case of internal attachment storage

@@ -212,7 +211,7 @@ OpenProject supports the latest versions of the major browsers.

 ##### OpenProject integration

-*  [OpenProject Integration 2.8.1](https://github.com/nextcloud/integration_openproject/releases/tag/v2.8.1)
+* [OpenProject Integration 2.8.1](https://github.com/nextcloud/integration_openproject/releases/tag/v2.8.1)

 ##### Team folders

@@ -22,7 +22,7 @@ Fixed Versions: 9.0.4, 10.0.2

 ### Credits

-Thanks to David Haintz from the SEC Consult Vulnerability Lab (https://www.sec-consult.com) for identifying and responsibly disclosing the identified issues.
+Thanks to David Haintz from the [SEC Consult Vulnerability Lab](https://www.sec-consult.com) for identifying and responsibly disclosing the identified issues.

 ## Incorrect setting results in slow application and RAM usage

@@ -94,7 +94,7 @@ We have now also expanded the attribute help texts for projects. You can define

 Boards and project dashboards can now also be copied when copying a project. This enables you to set up a default project and copy it to set up a new project.

-## As always,…… there’s much more!
+## As always, there’s much more

 There are lots and lots of new things we packed into 11.0 to tell you about.

@@ -50,7 +50,7 @@ Luckily, we now automated this process in order to reduce manual effort on both

 Furthermore, we have extended the authentication profile with an **OpenID Connect provider.** Also, the printing, e.g. for wiki pages, has been optimized via the browser print function.

-## As always,…… there’s much more!
+## As always, there’s much more

 There are a lot more things we packed into 11.1 to tell you about.

@@ -21,7 +21,7 @@ When upgrading to 12.2.1, a migration was added to restore some deleted historic

 For a few customers, this migration appears to have been unsuccessful to restore all affected journal entries. This resulted in the migration to fail and being unable to continue with the update. As we could not reproduce this issue as of now, you can choose to ignore the missing journals if you're affected.

-When you update to OpenProject 12.2.2 and the migration fails again, it will output steps on how to force the migration to complete. Doing that will output a debug log of all relevant information on these journals. Please help us identifying this issue by posting this log in this ticket: https://community.openproject.org/wp/43876, or reaching out to support@openproject.org.
+When you update to OpenProject 12.2.2 and the migration fails again, it will output steps on how to force the migration to complete. Doing that will output a debug log of all relevant information on these journals. Please help us identifying this issue by posting this log in this [ticket](https://community.openproject.org/wp/43876), or reaching out to [support](mailto:support@openproject.org).

 ## Bug fixes and changes

@@ -23,9 +23,10 @@ For more information, [please see our security advisory](https://github.com/opf/

 **Patches**

-You can download the following patch file to apply the patch to any OpenProject version > 10.0: https://patch-diff.githubusercontent.com/raw/opf/openproject/pull/12708.patch
+You can download the [patch file](https://patch-diff.githubusercontent.com/raw/opf/openproject/pull/12708.patch) to apply the patch to any OpenProject version > 10.0.

 **Workaround**
+
 If you are unable to update or apply the provided patch, mark any public project as non-public for the time being and give anyone in need of access to the project a membership.

 ## Bug fixes and changes
@@ -33,8 +33,6 @@ We are delighted about the GitLab integration, which is officially available wit

 With this integration, you can manage GitLab's units of work (merge requests and issues) from within OpenProject by linking them with work packages. Read more about OpenProject's GitLab integration [in our system admin guide](../../../system-admin-guide/integrations/gitlab-integration/).

-<div class="blog-box-info">
-
 **Already using the user-generated GitLab plugin?** With OpenProject 13.4, the existing plugin will be replaced by the new integration. We recommend removing the plugin module folder and bundler references before upgrading to OpenProject. Your historical dataset will remain unaffected within OpenProject as there were no changes to the data model.

 Before upgrading, please do the following:
@@ -42,8 +40,6 @@ Before upgrading, please do the following:
 1. Remove traces of the GitLab integration in your **Gemfile.lock** and **Gemfile.modules**. See [btey/openproject-gitlab-integration#configuration](https://github.com/btey/openproject-gitlab-integration?tab=readme-ov-file#configuration). Failure to do so may result in a `Bundler::GemfileError` matching the following error message: _Your Gemfile lists the gem openproject-gitlab_integration (>= 0) more than once._
 2. Remove the module code traces of the GitLab integration by running this command: `rm -rf /path/to/openproject/modules/gitlab_integration`

-</div>
-
 ![OpenProject's GitLab integration](GitLab_integration.png)

 ### Advanced features for custom project lists
@@ -64,12 +60,8 @@ Another long-awaited improvement: When you copy a dynamic meeting, **existing ag

 And finally, the .ics file now also contains information about the (dynamic) meeting attendees - in addition to other existing information such as PARTSTAT. This now allows you to **confirm or decline invitations to a meeting directly in your calendar software**.

-<div class="blog-box-info">
-
 Stay tuned: Further advanced features for our Meetings module are planned for upcoming releases – take a look at [this EPIC](https://community.openproject.org/projects/openproject/work_packages/52820/activity?query_id=4929) for detailed information.

-</div>
-
 ### Virus scanning functionality with ClamAV (Enterprise add-on)

 Another important step towards data security: With OpenProject 13.4, users' uploaded files can be scanned for viruses, using the ClamAV antivirus engine. To do so, a new attachment menu item is created with Antivirus settings. Read more about virus scanning using ClamAV in our [system admin guide](../../../system-admin-guide/files/attachments/virus-scanning/).
@@ -121,6 +121,7 @@ With OpenProject 14.2, [embedded attributes within a work package description](.
 <!-- Warning: Anything above this line will be automatically removed by the release script -->

 ## Contributions
+
 A very special thank you goes to the City of Cologne for sponsoring features on project attributes. Also a big thanks to our Community members for reporting bugs and helping us identify and provide fixes. Special thanks for reporting and finding  bugs go to Ricardo Brenner and Sven Kunze.

 Last but not least, we are very grateful for our very engaged translation contributors on Crowdin, who translated quite a few OpenProject strings! This release we would like to highlight user [aniessalam](https://crowdin.com/profile/aniessalam) who has done an outstanding number of translations for the Malay language in recent weeks.
@@ -34,13 +34,13 @@ Users now have the ability to create and delete multiple API access keys. This e

 When navigating to the Access Tokens page in your account settings, you can add new API access keys to the list of existing keys. These keys become active immediately upon creation. Additionally, you can delete any API access key from the list, which deactivates the key. When adding a new API access key, you will be prompted to give it a name for easier identification.

-For more information, see work package https://community.openproject.org/wp/48619.
+For more information, see this [work package](https://community.openproject.org/wp/48619).

 ### CRUD News API endpoints allow automatic creation of news

 With OpenProject 14.3, we added CRUD News API endpoints. The Devkit is now able to automatically forward release messages to the OpenProject application.

-For more information, see work package https://community.openproject.org/wp/55764.
+For more information, see this [work package](https://community.openproject.org/wp/55764).

 ### Configure SMTP timeout over ENV variable

@@ -55,7 +55,7 @@ config.action_mailer.smtp_timeout = 30'

 This will extend the SMTP timeout to 30 seconds, accommodating slower mail server responses.

-For more information, see work package https://community.openproject.org/wp/55879.
+For more information, see this [work package](https://community.openproject.org/wp/55879).

 ## Important feature changes

@@ -32,7 +32,7 @@ Up to now, the system faced issues such as unclear error messages, insufficient

 Additionally, the logging structure has been enhanced to provide more detailed, tagged entries for better traceability.

-For more details, see https://community.openproject.org/wp/56861.
+For more details, see this [work package](https://community.openproject.org/wp/56861).

 ## Important feature changes

@@ -44,7 +44,7 @@ Dark mode for OpenProject is finally here! In the '[My account](../../../user-gu

 Please note that this feature has been tested extensively, and we believe it works well. However, users might encounter issues that we haven't seen. Therefore, it will remain in beta for now, until we resolve all potential errors and ensure there are no issues.

-For more details, see https://community.openproject.org/wp/36233.
+For more details, see this [work package](https://community.openproject.org/wp/36233).

 ### Project attributes: Separate permissions for viewing and editing

@@ -56,7 +56,7 @@ The update adds **two new permissions: 'View project attributes' and 'Edit proje

 Permissions are now independent, so users with 'Edit project' can lack the new permissions. Users without 'View project attributes' cannot see or search project attributes in the overview, settings, list, exports, API, or Schema API. Users without 'Edit project attributes' cannot modify these attributes but can view them if they have view permission.

-For more details, see https://community.openproject.org/wp/50844.
+For more details, visit this [work package](https://community.openproject.org/wp/50844).

 ### Status-based progress reporting: Freely input % complete values for statuses

@@ -86,7 +86,7 @@ For example, you can filter your active projects by excluding certain projects:

 ![Screenshot of OpenProject 14.4, filtering project lists with 'Project' 'is not'](openproject-14-4-project-lists-filter.png)

-For more details, see https://community.openproject.org/wp/55233.
+For more details, see this [work package](https://community.openproject.org/wp/55233).

 ### Meetings: Saving a new agenda item does not automatically add another empty one

@@ -114,7 +114,7 @@ To improve efficiency and access to file storages, OpenProject 14.4 allows admin

 In the "General information" section, there is now a link that opens in a new window and leads to the root folder of the storage. For Nextcloud, this link refers to the root folder of the Nextcloud instance. For OneDrive/SharePoint, the link refers to the root folder of the drive ID and also works with "OneDrive Business".

-See https://community.openproject.org/wp/56045 for more information on this feature.
+Visit this [work package](https://community.openproject.org/wp/56045) for more information on this feature.

 ### Show changes of long text custom fields in the activity similar to changes in the description

@@ -221,14 +221,16 @@ Clicking on the "Details" link will take the user to the diff view, which is als
 <!-- Warning: Anything above this line will be automatically removed by the release script -->

 ## Contributions
+
 A very special thank you goes to the City of Cologne again for sponsoring features on project attributes and project lists. 

 Also a big thanks to our Community members for reporting bugs and helping us identify and provide fixes.
 Special thanks for reporting and finding bugs go to Johan Bouduin, Sven Kunze and Marcel Carvalho.

 Last but not least, we are very grateful for our very engaged translation contributors on Crowdin, who translated quite a few OpenProject strings! This release we would like to highlight the three following users: 
+
 - [Jeff Li](https://crowdin.com/profile/jeff_li) for translations to Chinese Simplified,
- [Adam Siemienski ](https://crowdin.com/profile/siemienas) for translations to Polish,
+- [Adam Siemienski](https://crowdin.com/profile/siemienas) for translations to Polish,
 - [Yuliia Pavliuk](https://crowdin.com/profile/pav.yulia) for translations to Ukrainian.

 Would you like to help out with translations yourself? Then take a look at our translation guide and find out exactly how you can contribute. It is very much appreciated!
@@ -209,6 +209,7 @@ Also a big thanks to our Community members for reporting bugs and helping us ide
 Special thanks for reporting and finding bugs go to Frank Schmid, Michael Kluge, Mariusz Kamiński, Rince wind, Joris Ceelen, Michael Lathion, and Cornelius Heisse.

 Last but not least, we are very grateful for our very engaged translation contributors on Crowdin, who translated quite a few OpenProject strings! This release we would like to highlight
+
 - [Phi Công Nguyễn Vũ](https://crowdin.com/profile/nguyenvuphicong), for an outstanding number of translations into Vietnamese.
 - [daniel chou](https://crowdin.com/profile/chou0214), for an outstanding number of translations into Chinese.
 - [Sebvita_devinci](https://crowdin.com/profile/sebvita_devinci), for proof reading French translations.
@@ -38,6 +38,7 @@ At the end, you will find a complete list of all changes and bug fixes.
 <!-- Warning: Anything above this line will be automatically removed by the release script -->

 ## Contributions
+
 A very special thank you goes to our sponsors for this release.
 Also a big thanks to our Community members for reporting bugs and helping us identify and provide fixes.
 Special thanks for reporting and finding bugs go to Александр Татаринцев, Niklas Grönblom.
@@ -65,8 +65,11 @@ Before 14.6, OpenProject's editors, such as in the work package description, did
 ### See past meetings included in the number next to the Meetings tab

 On the Meetings tab in the split screen view, the number next to the “Meetings (2)” tab should include both current and past meetings. Previously, only future meetings were counted. So if you use the Meetings module and reference work packages there, you may notice a higher number on the work package tab for meetings.
+
 ### Changes to design settings in administration
+
 [Design settings in OpenProject administration](../../../system-admin-guide/design) were split into several sections, to make navigation easier and eliminate scrolling down the page to find the correct setting.
+
 <!--more-->

 ## Bug fixes and changes
@@ -134,10 +137,12 @@ On the Meetings tab in the split screen view, the number next to the “Meetings
 <!-- Warning: Anything above this line will be automatically removed by the release script -->

 ## Contributions
+
 A very special thank you goes to City of Cologne again for sponsoring features in project lists. Also, a big thanks to our Community members for reporting bugs and helping us identify and provide fixes.
 Special thanks for reporting and finding bugs go to Jan H, Joris Ceelen, André van Kaam, and Christian Jeschke.

 Last but not least, we are very grateful for our very engaged translation contributors on Crowdin, who translated quite a few OpenProject strings!  This release we would like to highlight
+
 - [DKrukoff](https://crowdin.com/profile/dkrukoff), for translations into Russian.
 - [Sara Ruela](https://crowdin.com/profile/Sara.PT), for translations into Portuguese.
 - [BigSeung](https://crowdin.com/profile/BigSeung), for translations into Korean.
@@ -30,6 +30,7 @@ At the end, you will find a complete list of all changes and bug fixes.
 <!-- Warning: Anything above this line will be automatically removed by the release script -->

 ## Contributions
+
 A very special thank you goes to our sponsors for this release.
 Also a big thanks to our Community members for reporting bugs and helping us identify and provide fixes.
 Special thanks for reporting and finding bugs go to Peter Wafzig.
@@ -21,6 +21,7 @@ A major change in version 15.0 is the overall look-and-feel of the [Activity tab
 This is a big bundle of new features that will greatly improve communication and interaction within OpenProject, making it simpler, more effective and more fun.

 Related features in 15.0:
+
 - [Change the design of the Activity panel to Primer](https://community.openproject.org/wp/54733)
 - [Emoji reactions to work package comments](https://community.openproject.org/wp/40437)
 - [Continuously update the notification center. Don't ask for loading updates.](https://community.openproject.org/wp/58253)
@@ -31,7 +32,8 @@ Let's take a closer look at the three biggest changes concerning this feature bu

 #### A new timeline design for the Activity tab of work packages

-Apart from some obvious design changes that all fit GitHub's Primer design system, users will benefit from some great new features, such as: 
+Apart from some obvious design changes that all fit GitHub's Primer design system, users will benefit from some great new features, such as:
+
 - The comment box being a fixed element anchored to the bottom of the split screen area.
 - Filtering the Activity panel with options to either show everything, changes only or comments only.
 - Ordering to either newest on top or newest at the bottom.
@@ -93,6 +95,7 @@ With OpenProject 15.0, we are pleased to release another great improvement for o
 ### Experience simplified design settings with fewer sidebar design variables needed

 Before version 15.0, the design configuration in the administration was very complex as there were many variables to be defined. This is why with OpenProject 15.0, the following design colors cannot be customized anymore:
+
 - Header font
 - Header font on hover
 - Header border
@@ -230,6 +233,7 @@ For more information, please see our updated guides on these topics:
 A very special thank you goes to the City of Cologne for sponsoring parts of this release. Also a big thanks to our Community members for reporting bugs and helping us identify and provide fixes. Special thanks for reporting and finding bugs go to Bill Bai, Sam Yelman, Knight Chang, Gábor Alexovics, Gregor Buergisser, Andrey Dermeyko, Various Interactive, Clayton Belcher, Александр Татаринцев, and Keno Krewer.

 Last but not least, we are very grateful for our very engaged translation contributors on Crowdin, who translated quite a few OpenProject strings! This release we would like to highlight
+
 - [Alexander Aleschenko](https://crowdin.com/profile/top4ek), for a great number of translations into Russian.
 - [Alin Marcu](https://crowdin.com/profile/deconfcom), for a great number of translations into Romanian.
 - [hmmftg](https://crowdin.com/profile/hmmftg), for a great number of translations into Persian.
@@ -143,6 +143,7 @@ A very special thank you goes to Deutsche Bahn and City of Cologne for sponsorin
 Also, a big thanks to our Community members for reporting bugs and helping us identify and provide fixes. Special thanks for reporting and finding bugs go to Bill Bai, Sam Yelman, Knight Chang, Gábor Alexovics, Gregor Buergisser, Andrey Dermeyko, Various Interactive, Clayton Belcher, Александр Татаринцев, and Keno Krewer.

 Last but not least, we are very grateful for our very engaged translation contributors on Crowdin, who translated quite a few OpenProject strings! This release we would like to highlight
+
 - [Alexander Aleschenko](https://crowdin.com/profile/top4ek), for a great number of translations into Russian.
 - [José Helbert Pina](https://crowdin.com/profile/GZTranslations), for a great number of translations into Portuguese.
 - [BigSeung](https://crowdin.com/profile/BigSeung), for a great number of translations into Korean.
@@ -124,11 +124,13 @@ We continued introducing standardized components for page headers and subheaders
 <!-- Warning: Anything above this line will be automatically removed by the release script -->

 ## Contributions
+
 A heartfelt thank you to the City of Cologne and ZenDiS for sponsoring parts of this release. Your support, combined with the incredible efforts of our Community, continues to drive these innovations forward.

 Also a big thanks to our Community members for reporting bugs and helping us identify and provide fixes. Special thanks for reporting and finding bugs go to Stefan Weiberg.

 Last but not least, we are very grateful for our very engaged translation contributors on Crowdin, who translated quite a few OpenProject strings! This release we would like to highlight
+
 - [atifahnordin](https://crowdin.com/profile/atifahnordin), for an outstanding number of translations into Malay.
 - [Vlastislav Dockal](https://crowdin.com/profile/vdockal), for a great number of translations into Czech.
 - [Alin Marcu](https://crowdin.com/profile/deconfcom), for a great number of translations into Romanian.
@@ -39,6 +39,7 @@ At the end, you will find a complete list of all changes and bug fixes.
 <!-- Warning: Anything above this line will be automatically removed by the release script -->

 ## Contributions
+
 A big thanks to our Community members for reporting bugs and helping us identify and provide fixes.
 This release, special thanks for reporting and finding bugs go to Boris Lukashev, Serg Baranov, Lars Briem, Andrey Dermeyko.

@@ -88,7 +88,8 @@ OpenProject now provides better visibility into dependencies by displaying relat

 OpenProject 15.3 improves transparency by displaying all relations in the Relations tab. While restricted work packages remain inaccessible, their **start and finish dates will now be visible**, along with lag time for applicable relations. This way, users still cannot interact with restricted work packages but will now understand why a task is scheduled at a specific time.

-Please note that currently, **only the following relations are displayed with a date** – not dependent on permissions: 
+Please note that currently, **only the following relations are displayed with a date** – not dependent on permissions:
+
 - Successors (after)
 - Predecessors (before)
 - Children
@@ -258,6 +259,7 @@ A very special thank you goes to City of Cologne, Deutsche Bahn and ZenDiS for s
 Also, a big thanks to our Community members for reporting bugs and helping us identify and provide fixes. Special thanks for reporting and finding bugs go to Luka Bradesko, Max Mutzge, Lars Geiger, Rudi B., Alexander Aleschenko, Alex Fantini, Peter Wafzig.

 Last but not least, we are very grateful for our very engaged translation contributors on Crowdin, who translated quite a few OpenProject strings! This release we would like to highlight
+
 - [greench](https://crowdin.com/profile/greench), for an outstanding number of translations into Turkish.
 - [Kuma Yamashita](https://crowdin.com/profile/dredgk), for a great number of translations into Japanese.
 - [Willers-ICT](https://crowdin.com/profile/willers-ict), for a great number of translations into Dutch.
@@ -32,5 +32,6 @@ At the end, you will find a complete list of all changes and bug fixes.
 <!-- Warning: Anything above this line will be automatically removed by the release script -->

 ## Contributions
+
 A big thanks to our Community members for reporting bugs and helping us identify and provide fixes.
 This release, special thanks for reporting and finding bugs go to Çağlar Yeşilyurt, Andrej Sandorf.
@@ -218,6 +218,7 @@ For more information, see [this code maintenance work package on our Community i
 <!-- Warning: Anything above this line will be automatically removed by the release script -->

 ## Contributions
+
 A very special thank you goes to City of Cologne, Deutsche Bahn and ZenDiS for sponsoring released or upcoming features. Your support, alongside the efforts of our amazing Community, helps drive these innovations. We also thank the City of Chemnitz for providing us with a lot of helpful input regarding the automatic scheduling mode.

 Also, a big thanks to our Community members for reporting bugs and helping us identify and provide fixes. Special thanks for reporting and finding bugs go to René Schodder, Abhiyan Paudyal, Gunter Ohrner and Markus K..
@@ -34,5 +34,6 @@ At the end, you will find a complete list of all changes and bug fixes.
 <!-- Warning: Anything above this line will be automatically removed by the release script -->

 ## Contributions
+
 A big thanks to our Community members for reporting bugs and helping us identify and provide fixes.
 This release, special thanks for reporting and finding bugs go to Robb E.
@@ -167,11 +167,13 @@ To prepare for this transition, the **Classic option in the + Meeting dropdown i
 <!-- Warning: Anything above this line will be automatically removed by the release script -->

 ## Contributions
+
 A very special thank you goes to City of Cologne, Deutsche Bahn and ZenDiS for sponsoring released or upcoming features. Your support, alongside the efforts of our amazing Community, helps drive these innovations.

 Special thanks for reporting and finding bugs go to Abhiyan Paudyal, Andreas H., Paul Kernstock, Patrick Stapf, and Stefan Weiberg.

 Last but not least, we are very grateful for our very engaged translation contributors on Crowdin, who translated quite a few OpenProject strings! This release we would like to particularly thank the following users:
+
 - [Yuliia Pavliuk](https://crowdin.com/profile/pav.yulia), for a great number of translations into Ukrainian.
 - [Adam Siemienski](https://crowdin.com/profile/siemienas), for a great number of translations into Polish.
 - [NCAA](https://crowdin.com/profile/ncaa), for a great number of translations into Danish.
@@ -287,9 +287,11 @@ be able to use them in additional contexts. Starting with OpenProject 16.0.0, we
 <!-- Warning: Anything above this line will be automatically removed by the release script -->

 ## Contributions
+
 A very special thank you goes to City of Cologne, Deutsche Bahn and ZenDiS for sponsoring released or upcoming features. Your support, alongside the efforts of our amazing Community, helps drive these innovations. Also a big thanks to our Community members for reporting bugs and helping us identify and provide fixes. Special thanks for reporting and finding bugs go to alex e, Klaas vT, Daniel Elkeles, Marcel Carvalho, Regina Schikora, Çağlar Yeşilyurt, and Александр Татаринцев.

 Last but not least, we are very grateful for our very engaged translation contributors on Crowdin, who translated quite a few OpenProject strings! This release we would like to particularly thank the following users:
+
 - [Сергей Баранов](https://crowdin.com/profile/postbse), for a great number of translations into Russian.
 - [Gzyyy](https://crowdin.com/profile/gzyyy), for a great number of translations into Chinese simplified.
 - [rlmpereira](https://crowdin.com/profile/rlmpereira), for a great number of translations into Portuguese.
@@ -19,17 +19,16 @@ In addition, an error concerning the API v2 has been solved
 and several usability bug fixes in the meetings and documents plugin are
 included in 3.0.12:

-  - Meetings plugin:  
-    The preview function for the agenda and minutes which produced an
-    internal error has been fixed and works properly now
-    ([#15208](https://community.openproject.org/work_packages/15208 "Internal error when clicking on preview on agenda/minutes (closed)")).
-
-  - Documents plugin:  
-    With 3.0.12 an error in the documents plugin which caused an
-    internal error when opening a user page
-    ([#12620](https://community.openproject.org/work_packages/12620 "Missing event type cause 500 ERROR on user page. (closed)"))
-    has been fixed. Many thanks to [Björn Blissing](https://github.com/bjornblissing) who reported and fixed
-    this error.
+- Meetings plugin:  
+  The preview function for the agenda and minutes which produced an
+  internal error has been fixed and works properly now
+  ([#15208](https://community.openproject.org/work_packages/15208 "Internal error when clicking on preview on agenda/minutes (closed)")).
+- Documents plugin:  
+  With 3.0.12 an error in the documents plugin which caused an
+  internal error when opening a user page
+  ([#12620](https://community.openproject.org/work_packages/12620 "Missing event type cause 500 ERROR on user page. (closed)"))
+  has been fixed. Many thanks to [Björn Blissing](https://github.com/bjornblissing) who reported and fixed
+  this error.

 For a complete list of changes, pleas refer to the
 [OpenProject 3.0.12 query](https://community.openproject.org/versions/450).
@@ -14,12 +14,12 @@ It is possible to extend OpenProject by using Omni-Auth providers. Users
 can for example use the OpenProject Auth plugin for an
 easy integration with OmniAuth strategy providers such as Google.

-  - Authentication in OpenProject via OmniAuth provider
-  - Easier integration with OmniAuth providers (such as Google) via
-    OpenProject Auth plugin
-  - Easier implementation of OmniAuth strategies
-  - Multiple authentication provider can be integrated and are shown in
-    the login screen
+- Authentication in OpenProject via OmniAuth provider
+- Easier integration with OmniAuth providers (such as Google) via
+  OpenProject Auth plugin
+- Easier implementation of OmniAuth strategies
+- Multiple authentication provider can be integrated and are shown in
+  the login screen

 ## Integrated toolbar on work package page

@@ -33,20 +33,20 @@ work packages right from the work package table.
 Accessing, filtering and changing the work package page has become even
 more intuitive.

-  - Expandable filter section
-  - Instantly applied work package filters
-  - Work package creation from work package table
-  - Two different views: Work package table and split-screen
-  - Create new queries based on existing ones (Save as)
+- Expandable filter section
+- Instantly applied work package filters
+- Work package creation from work package table
+- Two different views: Work package table and split-screen
+- Create new queries based on existing ones (Save as)

 ## Integrated query title on work package page

 The query selection is now integrated in the work package title. Queries
 are being persisted.

-  - Title includes query selection
-  - Auto-completion of queries is supported
-  - Selected query is persisted
+- Title includes query selection
+- Auto-completion of queries is supported
+- Selected query is persisted

 ## Column header functions in work package table

@@ -54,11 +54,11 @@ To provide users with a maximum of flexibility and convenience, it is
 possible to perform some of the most frequently used actions in the work
 package table right on a column header.

-  - Perform often used functions right on the column header
-  - Sort by column
-  - Group by column attribute
-  - Hide / Remove column
-  - Add new column
+- Perform often used functions right on the column header
+- Sort by column
+- Group by column attribute
+- Hide / Remove column
+- Add new column

 ## Split screen mode added to work package page

@@ -70,42 +70,42 @@ The included work package details pane is separated in the different
 tabs **Overview, Activity, Relations, Watchers** and **Attachments**,
 allowing users to see the most important information at a glance.

-  - Expandable work package details pane
-  - “Overview” tab for general work package information
-  - “Activity” tab showing history
-  - “Relations” tab for dependencies
-  - “Watchers” tab to follow work package
-  - “Attachments” tab showing attached documents
+- Expandable work package details pane
+- “Overview” tab for general work package information
+- “Activity” tab showing history
+- “Relations” tab for dependencies
+- “Watchers” tab to follow work package
+- “Attachments” tab showing attached documents

 ## Improved design

 Several design changes have been made to improve the readability and
 overall usability of OpenProject.

-  - Bigger line spacing in work package table
-  - Table background single color white
-  - All-cap headings throughout the application
-  - New hovering color in work package table
-  - Changed headlines
-  - Round avatars
+- Bigger line spacing in work package table
+- Table background single color white
+- All-cap headings throughout the application
+- New hovering color in work package table
+- Changed headlines
+- Round avatars

 ## Many accessibility improvements

 Numerous accessibility improvements – especially in the work package
 page.

-  - Work package page very accessible
-  - Extension of work package context menu to include option to activate
-    work package split screen
-  - Keyboard shortcuts and access key fully functional in work package
-    page
+- Work package page very accessible
+- Extension of work package context menu to include option to activate
+  work package split screen
+- Keyboard shortcuts and access key fully functional in work package
+  page

 ## New plugins released

-  - OpenProject Auth plugin
-    [GitHub](https://github.com/opf/openproject-auth_plugins)
-  - OpenProject GitHub integration plugin
-    [GitHub](https://github.com/finnlabs/openproject-github_integration)
+- OpenProject Auth plugin
+  [GitHub](https://github.com/opf/openproject-auth_plugins)
+- OpenProject GitHub integration plugin
+  [GitHub](https://github.com/finnlabs/openproject-github_integration)

 ## Substantial Number of Bug Fixes

@@ -12,11 +12,11 @@ OpenProject 4.0.12 contains a bug fix and a security fix.

 The following bugs have been fixed:

-  - In projects with a lot of members and/or custom fields creating a
-    work package could lead to an internal error (500)
-    ([#21068](https://community.openproject.org/work_packages/21068)).
-  - In addition, a security bug has been fixed which potentially enabled
-    XSS attacks.
+- In projects with a lot of members and/or custom fields creating a
+  work package could lead to an internal error (500)
+  ([#21068](https://community.openproject.org/work_packages/21068)).
+- In addition, a security bug has been fixed which potentially enabled
+  XSS attacks.

 For further information on the release, please refer to the
 [Changelog v.4.0.12](https://community.openproject.org/versions/756)
@@ -16,20 +16,20 @@ With OpenProject 4.0.2 the Rails version has been updated to 3.2.21
 ([#17467](https://community.openproject.org/work_packages/17467 "Updating Rails to 3.2.21 (closed)")).  
 In addition, several bugs have been fixed:

-  - An error preventing work packages from being created with an
-    activated split screen has been resolved
-    ([#17333](https://community.openproject.org/work_packages/17333 "Not possible to create work package from work package page with activated split screen (wrong link) (closed)"))
-  - Errors with regards to time tracking have been fixed
-    ([#17500](https://community.openproject.org/work_packages/17500 "Permission for 'spent time' not applied on legacy WP view and list of time entries (closed)"),
-    [#17499](https://community.openproject.org/work_packages/17499 "Spent time not part of work package API (closed)"),
-    [#17222](https://community.openproject.org/work_packages/17222 "[TimeEntries] spent_on date always displays the current date (closed)"))
-  - Timelines embedded via wiki macros are now properly sized
-    ([#17353](https://community.openproject.org/work_packages/17353 "[Wiki] Timelines macro does not have sufficient width (closed)"))
-  - Custom fields of type version are now displayed in the work package
-    split screen
-    ([#17354](https://community.openproject.org/work_packages/17354 "Value for custom fields of type version not displayed in details pane (closed)"))
-  - Accessibility improvements have been made
-    ([#17230](https://community.openproject.org/work_packages/17230 "[Accessibility] Star/Watch icon in Details pane not accessible  (closed)")).
+- An error preventing work packages from being created with an
+  activated split screen has been resolved
+  ([#17333](https://community.openproject.org/work_packages/17333 "Not possible to create work package from work package page with activated split screen (wrong link) (closed)"))
+- Errors with regards to time tracking have been fixed
+  ([#17500](https://community.openproject.org/work_packages/17500 "Permission for 'spent time' not applied on legacy WP view and list of time entries (closed)"),
+  [#17499](https://community.openproject.org/work_packages/17499 "Spent time not part of work package API (closed)"),
+  [#17222](https://community.openproject.org/work_packages/17222 "[TimeEntries] spent_on date always displays the current date (closed)"))
+- Timelines embedded via wiki macros are now properly sized
+  ([#17353](https://community.openproject.org/work_packages/17353 "[Wiki] Timelines macro does not have sufficient width (closed)"))
+- Custom fields of type version are now displayed in the work package
+  split screen
+  ([#17354](https://community.openproject.org/work_packages/17354 "Value for custom fields of type version not displayed in details pane (closed)"))
+- Accessibility improvements have been made
+  ([#17230](https://community.openproject.org/work_packages/17230 "[Accessibility] Star/Watch icon in Details pane not accessible  (closed)")).

 A big thanks to everyone involved in fixing and reporting those bugs!

@@ -15,9 +15,9 @@ OpenProject 4.0.4.

 ## OpenProject 4.0.4

-  - Due to a regression it was not possible to group by attributes which
-    are not displayed in the work package table. This has been resolved
-    ([#17738](https://community.openproject.org/work_packages/17738 "500 on WP table on grouping by non displayed column (closed)")).
+- Due to a regression it was not possible to group by attributes which
+  are not displayed in the work package table. This has been resolved
+  ([#17738](https://community.openproject.org/work_packages/17738 "500 on WP table on grouping by non displayed column (closed)")).

 ## List of changes

@@ -13,17 +13,17 @@ We advise everyone to update their OpenProject installations.

 The following bugs have been fixed in the core:

-  - When sorting by a version in the work package table, the result was
-    not shown but an unclear error message displayed
-    ([#17928](https://community.openproject.org/work_packages/17928 "Sorting by version leads to 500 in experimental API (\"Unable to retrieve query from URL\") (closed)")).
-  - Clicking on the project name in a timeline let to “Page not found”
-    ([#17819](https://community.openproject.org/work_packages/17819 "[Regression] Page not found when clicking on project link in timeline (NaN in link) (closed)")).
-  - The “Close” icon of modals was cut off
-    ([#17818](https://community.openproject.org/work_packages/17818 "[Regression] Close icon of modals is cut off (closed)")).
-  - Dates in the work package table were sometimes not displayed properly
-    ([#17043](https://community.openproject.org/work_packages/17043 "Single bad translation on work package table. (closed)")).
-    Thanks a lot to [Mike Lewis](https://community.openproject.org/users/35400) for reporting
-    this error!
+- When sorting by a version in the work package table, the result was
+  not shown but an unclear error message displayed
+  ([#17928](https://community.openproject.org/work_packages/17928 "Sorting by version leads to 500 in experimental API (\"Unable to retrieve query from URL\") (closed)")).
+- Clicking on the project name in a timeline let to “Page not found”
+  ([#17819](https://community.openproject.org/work_packages/17819 "[Regression] Page not found when clicking on project link in timeline (NaN in link) (closed)")).
+- The “Close” icon of modals was cut off
+  ([#17818](https://community.openproject.org/work_packages/17818 "[Regression] Close icon of modals is cut off (closed)")).
+- Dates in the work package table were sometimes not displayed properly
+  ([#17043](https://community.openproject.org/work_packages/17043 "Single bad translation on work package table. (closed)")).
+  Thanks a lot to [Mike Lewis](https://community.openproject.org/users/35400) for reporting
+  this error!

 Additionally, the work package export via CSV is working properly again
 ([#16813](https://community.openproject.org/work_packages/16813 "CSV Export is fixed (closed)")).
@@ -20,12 +20,12 @@ with OpenProject 4.0.7.

 Additionally, several errors on the work package table have been fixed:

-  - Deleted work package queries which have been added to the side menu
-    are now properly removed when the query is deleted
-    ([#18591](https://community.openproject.org/work_packages/18591 "#18591")).
-  - The “Save” button in the query list is now only displayed when
-    changes have been made
-    ([#18592](https://community.openproject.org/work_packages/18592 "#18592")).
+- Deleted work package queries which have been added to the side menu
+  are now properly removed when the query is deleted
+  ([#18591](https://community.openproject.org/work_packages/18591 "#18591")).
+- The “Save” button in the query list is now only displayed when
+  changes have been made
+  ([#18592](https://community.openproject.org/work_packages/18592 "#18592")).

 Furthermore, a bug has been fixed which caused an internal error when
 creating a new reporting
@@ -14,15 +14,15 @@ The layout of the work package split screen was updated to provide a
 clearer, more accessible interface. Several changes have been
 implemented to the split screen:

-  - In order to allow users to see the most relevant work package
-    information at a glance, only the work package attributes which have
-    values assigned are displayed by default.
-  - Work package attributes which have no values assigned can be
-    displayed via the “Show all” button, which has been moved to the top
-    of the attribute list.
-  - To provide a logical structure to the work package, work package
-    attributes are clustered into separate groups (Details, People,
-    Estimates & Time, Costs, Other).
+- In order to allow users to see the most relevant work package
+  information at a glance, only the work package attributes which have
+  values assigned are displayed by default.
+- Work package attributes which have no values assigned can be
+  displayed via the “Show all” button, which has been moved to the top
+  of the attribute list.
+- To provide a logical structure to the work package, work package
+  attributes are clustered into separate groups (Details, People,
+  Estimates & Time, Costs, Other).

 ## In-place editing on work package split screen

@@ -31,9 +31,9 @@ to update work packages without leaving the work package table. Via the
 split screen many work package attributes can be edited on the fly, such
 as:

-  - Work package subject
-  - Work package description
-  - Work package attributes (including custom fields)
+- Work package subject
+- Work package description
+- Work package attributes (including custom fields)

 Several work package values can be edited at once.

@@ -44,20 +44,20 @@ filters – even when the filter section is collapsed. Additionally, the
 work package ID in the work package table is no longer static, but can be
 configured as the other columns in the work package table:

-  - Number of activated filters shown
-  - Work package ID in work package table can be added, removed, changed
-    in order
+- Number of activated filters shown
+- Work package ID in work package table can be added, removed, changed
+  in order

 ## Improved work package full screen

 The design of the work package page and the work package form has been
 updated:

-  - When editing a work package, the type, parent and subject can be
-    edited right away without having to expand a separate section.
-  - The spacing of the work package attributes has been increased.
-  - The work package hierarchy, related work packages and watchers have
-    been styled more prominently.
+- When editing a work package, the type, parent and subject can be
+  edited right away without having to expand a separate section.
+- The spacing of the work package attributes has been increased.
+- The work package hierarchy, related work packages and watchers have
+  been styled more prominently.

 ## New design through Foundation framework

@@ -71,13 +71,13 @@ with OpenProject 4.1.
 Numerous accessibility improvements have been introduced – particularly
 on the work package page.

-  - Split screen accessible
-  - In-place editing can be performed via keyboard
-  - Modal windows on work package page include helpful hints for both
-    seeing and blind users
-  - Additional access key for switching between work package table and
-    split screen
-  - Contrast for watcher icon improved
+- Split screen accessible
+- In-place editing can be performed via keyboard
+- Modal windows on work package page include helpful hints for both
+  seeing and blind users
+- Additional access key for switching between work package table and
+  split screen
+- Contrast for watcher icon improved

 ## Substantial number of bug fixes

@@ -17,49 +17,45 @@ We strongly recommend to upgrade to the current version.

 **OpenProject core:**

-  - The timezone in the work package view was incorrect. This has been
-    fixed
-    ([#20210](https://community.openproject.org/work_packages/20210)).
-    Thanks to [Javier Martínez](https://community.openproject.org/users/39048) for
-    reporting this error.
-  - For subfolder installations of OpenProject, the assignee and
-    responsible could not be edited. This has been fixed
-    ([#20311](https://community.openproject.org/work_packages/20311)).
-  - Due to an error, the quick reference for syntax was displayed when
-    editing text fields. This has been resolved with
-    [#20314](https://community.openproject.org/work_packages/20314).
-  - An error prevented the deletion of global work package queries. This
-    is working properly again with OpenProject 4.1.2
-    ([#20316](https://community.openproject.org/work_packages/20316)).
-  - Additional a number of design errors have been fixed
-    ([#20305](https://community.openproject.org/work_packages/20305),
-    [#20306](https://community.openproject.org/work_packages/20306),
-    [#20308](https://community.openproject.org/work_packages/20308),
-    [#20309](https://community.openproject.org/work_packages/20309),
-    [#20317](https://community.openproject.org/work_packages/20317),
-    [#20313](https://community.openproject.org/work_packages/20313)).
-
+- The timezone in the work package view was incorrect. This has been fixed
+  ([#20210](https://community.openproject.org/work_packages/20210)).
+  Thanks to [Javier Martínez](https://community.openproject.org/users/39048) for
+  reporting this error.
+- For subfolder installations of OpenProject, the assignee and
+  responsible could not be edited. This has been fixed
+  ([#20311](https://community.openproject.org/work_packages/20311)).
+- Due to an error, the quick reference for syntax was displayed when
+  editing text fields. This has been resolved with
+  [#20314](https://community.openproject.org/work_packages/20314).
+- An error prevented the deletion of global work package queries. This
+  is working properly again with OpenProject 4.1.2
+  ([#20316](https://community.openproject.org/work_packages/20316)).
+- Additional a number of design errors have been fixed
+  ([#20305](https://community.openproject.org/work_packages/20305),
+  [#20306](https://community.openproject.org/work_packages/20306),
+  [#20308](https://community.openproject.org/work_packages/20308),
+  [#20309](https://community.openproject.org/work_packages/20309),
+  [#20317](https://community.openproject.org/work_packages/20317),
+  [#20313](https://community.openproject.org/work_packages/20313)).
+  
 As an additional improvement, the icons in the administration section
 have been updated
 ([#20305](https://community.openproject.org/work_packages/20305)).

 **Backlogs plugin:**

-  - The burndown chart is displayed properly again with OpenProject
-    4.1.1
-    ([#20312](https://community.openproject.org/work_packages/20312)).
+- The burndown chart is displayed properly again with OpenProject 4.1.1 ([#20312](https://community.openproject.org/work_packages/20312)).

 **Costs plugin:**

-  - An error in budget prevented the deletion of planned cost item. This
-    has been fixed
-    ([#20307](https://community.openproject.org/work_packages/20307)).
+- An error in budget prevented the deletion of planned cost item. This has been fixed
+  ([#20307](https://community.openproject.org/work_packages/20307)).

 **Meetings plugin:**

-  - In OpenProject 4.1.1 it was not possible to delete meetings. This
-    feature has been fixed
-    ([#20149](https://community.openproject.org/work_packages/20149)).
+- In OpenProject 4.1.1 it was not possible to delete meetings. This
+  feature has been fixed
+  ([#20149](https://community.openproject.org/work_packages/20149)).

 For further information on the release, please refer to the
 [Changelog v.4.1.2](https://community.openproject.org/versions/726)
@@ -15,14 +15,14 @@ which is an important part of the software stack used by OpenProject

 In addition, a number of bug fixes are included in the new release:

-  - Dates on the details pane were not visible for anonymous users
-    ([#20266](https://community.openproject.org/work_packages/20266)).
-  - The title was displayed twice in email notifications when creating
-    new work packages
-    ([#20232](https://community.openproject.org/work_packages/20232)).
-  - An unnecessary warning message was displayed when reloading the work
-    package page after adding a comment via the details pane
-    ([#19515](https://community.openproject.org/work_packages/19515)).
+- Dates on the details pane were not visible for anonymous users
+  ([#20266](https://community.openproject.org/work_packages/20266)).
+- The title was displayed twice in email notifications when creating
+  new work packages
+  ([#20232](https://community.openproject.org/work_packages/20232)).
+- An unnecessary warning message was displayed when reloading the work
+  package page after adding a comment via the details pane
+  ([#19515](https://community.openproject.org/work_packages/19515)).

 Additionally, the styling of the activities section on the details pane
 has been updated
@@ -12,11 +12,11 @@ OpenProject 4.1.4 contains a bug fix and a security fix.

 The following bugs have been fixed:

-  - In projects with a lot of members and/or custom fields creating a
-    work package could lead to an internal error (500)
-    ([#21067](https://community.openproject.org/work_packages/21067)).
-  - In addition, a security bug has been fixed which potentially enabled
-    XSS attacks.
+- In projects with a lot of members and/or custom fields creating a
+  work package could lead to an internal error (500)
+  ([#21067](https://community.openproject.org/work_packages/21067)).
+- In addition, a security bug has been fixed which potentially enabled
+  XSS attacks.

 For further information on the release, please refer to the
 [Changelog v.4.1.4](https://community.openproject.org/versions/755)
@@ -14,11 +14,11 @@ prevented translations from being displayed properly

 Additionally, some other translation related errors have been fixed:

-  - In the admin area several languages were wrongly displayed as
-    “English”
-    ([#20801](https://community.openproject.org/work_packages/20801)).
-  - Some translations in the work package context menu broke the layout
-    ([#20835](https://community.openproject.org/work_packages/20835)).
+- In the admin area several languages were wrongly displayed as
+  “English”
+  ([#20801](https://community.openproject.org/work_packages/20801)).
+- Some translations in the work package context menu broke the layout
+  ([#20835](https://community.openproject.org/work_packages/20835)).

 For further information on the release, please refer to the
 [Changelog v.4.2.1](https://community.openproject.org/versions/731)
@@ -14,13 +14,13 @@ core and plugins, for instance complete translations for French

 Additionally, some bugs have been fixed:

-  - Several wrong English translations have been fixed – in the core and
-    in plugins
-    ([#20901](https://community.openproject.org/work_packages/20901),
-    [#20902](https://community.openproject.org/work_packages/20902),
-    [#20859](https://community.openproject.org/work_packages/20859)).
-  - The last login is no longer visible in the user profile
-    ([#20892](https://community.openproject.org/work_packages/20892)).
+- Several wrong English translations have been fixed – in the core and
+  in plugins
+  ([#20901](https://community.openproject.org/work_packages/20901),
+  [#20902](https://community.openproject.org/work_packages/20902),
+  [#20859](https://community.openproject.org/work_packages/20859)).
+- The last login is no longer visible in the user profile
+  ([#20892](https://community.openproject.org/work_packages/20892)).

 For further information on the release, please refer to the
 [Changelog v.4.2.2](https://community.openproject.org/versions/729)
@@ -13,29 +13,29 @@ OpenProject 4.2.3 contains several bug fixes and updated translations.

 The following bugs have been fixed:

-  - A bug was fixed which could lead to an error 500 if a work package
-    was created in a project which has a lot of possible watchers and
-    /or custom fields
-    ([#20998](https://community.openproject.org/work_packages/20998)).
-  - With OpenProject 4.2.2 logged out users could see the “Modules” menu
-    even when the option “Authentication required” was activated. This
-    has been fixed
-    ([#20935](https://community.openproject.org/work_packages/20935)).
-  - In some circumstances journal entries in work packages were
-    displayed twice. This has been fixed
-    ([#20914](https://community.openproject.org/work_packages/20914)).
-  - The REST API option is now activated for new OpenProject instances
-    by default
-    ([#20914](https://community.openproject.org/work_packages/20914)).
+- A bug was fixed which could lead to an error 500 if a work package
+  was created in a project which has a lot of possible watchers and
+  /or custom fields
+  ([#20998](https://community.openproject.org/work_packages/20998)).
+- With OpenProject 4.2.2 logged out users could see the “Modules” menu
+  even when the option “Authentication required” was activated. This
+  has been fixed
+  ([#20935](https://community.openproject.org/work_packages/20935)).
+- In some circumstances journal entries in work packages were
+  displayed twice. This has been fixed
+  ([#20914](https://community.openproject.org/work_packages/20914)).
+- The REST API option is now activated for new OpenProject instances
+  by default
+  ([#20914](https://community.openproject.org/work_packages/20914)).

 Apart from the OpenProject core, several wrong strings in plugins have
 been fixed:

-  - Global Roles: In the details view of a role a wrong string was
-    displayed
-    ([#21001](https://community.openproject.org/work_packages/21001)).
-  - PDF Export: A success notification contained a type
-    ([#20996](https://community.openproject.org/work_packages/20996)).
+- Global Roles: In the details view of a role a wrong string was
+  displayed
+  ([#21001](https://community.openproject.org/work_packages/21001)).
+- PDF Export: A success notification contained a type
+  ([#20996](https://community.openproject.org/work_packages/20996)).

 For further information on the release, please refer to the
 [Changelog v.4.2.3](https://community.openproject.org/versions/748)
@@ -12,9 +12,8 @@ OpenProject 4.2.4 contains a bug fix and updated translations.

 The following bug has been fixed:

-  - An English string in the project dependencies was wrong and has been
-    fixed
-    ([#20910](https://community.openproject.org/work_packages/20910)).
+- An English string in the project dependencies was wrong and has been fixed
+  ([#20910](https://community.openproject.org/work_packages/20910)).

 Additionally, new translations have been included (including complete
 translations for Portuguese, Brazilian).
@@ -12,17 +12,17 @@ OpenProject 4.2.5 contains bug fixes and updated translations.

 The following bugs have been fixed:

-  - When an action is performed on the work package split screen, the
-    toolbar is correctly displayed. Before, the toolbar and pagination
-    were partly hidden
-    ([#21204](https://community.openproject.org/work_packages/21204)).
-  - An error has been fixed which caused a random language to be
-    displayed when first logging into an OpenProject instance if no
-    language has been configured
-    ([#21119](https://community.openproject.org/work_packages/21119)).
-  - For users of OpenProject-CE packager installation on CentOS, a bug
-    has been fixed which affects a wrong autostart configuration
-    ([#21126](https://community.openproject.org/work_packages/21126)).
+- When an action is performed on the work package split screen, the
+  toolbar is correctly displayed. Before, the toolbar and pagination
+  were partly hidden
+  ([#21204](https://community.openproject.org/work_packages/21204)).
+- An error has been fixed which caused a random language to be
+  displayed when first logging into an OpenProject instance if no
+  language has been configured
+  ([#21119](https://community.openproject.org/work_packages/21119)).
+- For users of OpenProject-CE packager installation on CentOS, a bug
+  has been fixed which affects a wrong autostart configuration
+  ([#21126](https://community.openproject.org/work_packages/21126)).

 Additionally, new translations have been included (including complete
 translations for Swedish).
@@ -12,20 +12,20 @@ OpenProject 4.2.6 contains a bug fixes and updated translations.

 The following bugs have been fixed:

-  - In projects with a lot of (potential) watchers an error occurred
-    when changing the work package type while creating a work package.
-    This error has been fixed
-    ([#21233](https://community.openproject.org/work_packages/21233)).
-  - Occasionally, a wrong language was displayed in the work package
-    split screen. This has been fixed
-    ([#21219](https://community.openproject.org/work_packages/21219)).
-  - An error has been fixed which prevented user creation with
-    authentication via LDAP
-    ([#21129](https://community.openproject.org/work_packages/21129)).
-  - Several wrong English strings have been fixed
-    ([#21240](https://community.openproject.org/work_packages/21240),
-    [#21248](https://community.openproject.org/work_packages/21248),
-    [#21253](https://community.openproject.org/work_packages/21253)).
+- In projects with a lot of (potential) watchers an error occurred
+  when changing the work package type while creating a work package.
+  This error has been fixed
+  ([#21233](https://community.openproject.org/work_packages/21233)).
+- Occasionally, a wrong language was displayed in the work package
+  split screen. This has been fixed
+  ([#21219](https://community.openproject.org/work_packages/21219)).
+- An error has been fixed which prevented user creation with
+  authentication via LDAP
+  ([#21129](https://community.openproject.org/work_packages/21129)).
+- Several wrong English strings have been fixed
+  ([#21240](https://community.openproject.org/work_packages/21240),
+  [#21248](https://community.openproject.org/work_packages/21248),
+  [#21253](https://community.openproject.org/work_packages/21253)).

 Additionally, OpenProject 4.2.6 contains new translations.

@@ -35,14 +35,14 @@ package.

 ## Improved work package split screen

-  - It is possible to edit and comment in one step in the work package
-    split screen
-    ([#20208](https://community.openproject.org/wp/20208)).
-  - Watcher behavior changed: User receive an email notification when
-    they have been added as watchers.
-  - Repository revisions are shown in the activity tab on the work
-    package split screen
-    ([#15422](https://community.openproject.org/wp/15422)).
+- It is possible to edit and comment in one step in the work package
+  split screen
+  ([#20208](https://community.openproject.org/wp/20208)).
+- Watcher behavior changed: User receive an email notification when
+  they have been added as watchers.
+- Repository revisions are shown in the activity tab on the work
+  package split screen
+  ([#15422](https://community.openproject.org/wp/15422)).

 ## New home screen

@@ -135,21 +135,21 @@ attributes.
 In order to reduce complexity, some rarely used OpenProject features
 have been deprecated and removed with OpenProject 5.0:

-  - The field “Homepage” in the project settings has been removed to
-    reduce complexity. Instead a custom field or the project description
-    can be used to contain the homepage information
-    ([#1928](https://community.openproject.org/wp/1928)).
-  - The field “Summary” in the project settings has been removed to
-    reduce complexity. Instead of the summary the first row of the
-    project description is shown on the project list.
-  - Project dependencies have been removed from OpenProject since they
-    didn’t serve  a significant purpose. Additionally, the “second
-    grouping criterion” has been removed from the timelines filters
-    ([#21509](https://community.openproject.org/wp/21509)).
-  - The column “Set current rate” has been removed from the project
-    member table
-    ([#21501](https://community.openproject.org/wp/21501)).
-    A user’s hourly rate can be set in the user administration.
+- The field “Homepage” in the project settings has been removed to
+  reduce complexity. Instead a custom field or the project description
+  can be used to contain the homepage information
+  ([#1928](https://community.openproject.org/wp/1928)).
+- The field “Summary” in the project settings has been removed to
+  reduce complexity. Instead of the summary the first row of the
+  project description is shown on the project list.
+- Project dependencies have been removed from OpenProject since they
+  didn’t serve  a significant purpose. Additionally, the “second
+  grouping criterion” has been removed from the timelines filters
+  ([#21509](https://community.openproject.org/wp/21509)).
+- The column “Set current rate” has been removed from the project
+  member table
+  ([#21501](https://community.openproject.org/wp/21501)).
+  A user’s hourly rate can be set in the user administration.

 The **copy** and **duplicate** functionality on the work package
 fullscreen and split screen has been temporarily excluded. It will be
@@ -160,12 +160,12 @@ re-implemented in the next OpenProject version.
 Aside from the main features, several smaller usability improvements are
 included in OpenProject 5.0:

-  - The custom fields have been moved to a separate tab in the project
-    settings
-    ([#20841](https://community.openproject.org/wp/20841)).
-  - Status reports are no longer a separate menu entry in the side menu
-    but they have been moved to the timeline
-    toolbar ([#21822](https://community.openproject.org/wp/21822)).
+- The custom fields have been moved to a separate tab in the project
+  settings
+  ([#20841](https://community.openproject.org/wp/20841)).
+- Status reports are no longer a separate menu entry in the side menu
+  but they have been moved to the timeline
+  toolbar ([#21822](https://community.openproject.org/wp/21822)).

 ## Improved design

@@ -181,16 +181,14 @@ and the layout has been improved in many other places as well.
 ## Additional functionalities for API v3

 The future OpenProject API (API v3) has been extended by several
-functionalities. For instance, the [API
-v3](../../../api/) now includes an
+functionalities. For instance, the [API v3](../../../api/) now includes an
 endpoint for the work package index-action.

 Please note that the API v3 is still a draft.

 ## Updated Rails version

-Rails – the main framework used for OpenProject – has been updated to
-Rails 4.2
+Rails – the main framework used for OpenProject – has been updated to Rails 4.2
 ([#20045](https://community.openproject.org/wp/20045)).

 This ensures the technical reliability and allows future improvements.
@@ -200,20 +198,13 @@ This ensures the technical reliability and allows future improvements.
 Several new plugins have been published. They are included in the
 OpenProject Packager edition.

-  - OpenProject – Local Avatars ([Read more on
-    GitHub](https://www.github.com/finnlabs/openproject-local_avatars))
-  - OpenProject – Announcements ([Read more on
-    GitHub](https://www.github.com/finnlabs/openproject-announcements))
-  - OpenProject – XLS-Export ([Read more on
-    GitHub](https://www.github.com/finnlabs/openproject-xls_export))
-  - OpenProject – Dark-Theme ([Read more on
-    GitHub](https://www.github.com/finnlabs/openproject-themes-dark))
-  - OpenProject – OpenID-Connect ([Read more on
-    GitHub](https://www.github.com/finnlabs/openproject-openid_connect))
-  - OpenProject – OmniAuth OpenID-Connect-Providers ([Read more on
-    GitHub](https://www.github.com/finnlabs/omniauth-openid-connect))
+- OpenProject – Local Avatars ([Read more on GitHub](https://www.github.com/finnlabs/openproject-local_avatars))
+- OpenProject – Announcements ([Read more on GitHub](https://www.github.com/finnlabs/openproject-announcements))
+- OpenProject – XLS-Export ([Read more on GitHub](https://www.github.com/finnlabs/openproject-xls_export))
+- OpenProject – Dark-Theme ([Read more on GitHub](https://www.github.com/finnlabs/openproject-themes-dark))
+- OpenProject – OpenID-Connect ([Read more on GitHub](https://www.github.com/finnlabs/openproject-openid_connect))
+- OpenProject – OmniAuth OpenID-Connect-Providers ([Read more on GitHub](https://www.github.com/finnlabs/omniauth-openid-connect))

 ## Substantial number of bug fixes

-A large number of bugs have been fixed with the release of OpenProject
-5.0.
+A large number of bugs have been fixed with the release of OpenProject 5.0.
@@ -13,29 +13,29 @@ for the OpenProject core and plugins.

 The following bugs have been fixed with OpenProject 5.0.1:

-  - An error in the documents plugin caused an error on the enumeration
-    page
-    ([#22093](https://community.openproject.org/work_packages/22093)).
-  - A bug has been fixed which prevented custom fields for time tracking
-    to be displayed
-    ([#22116](https://community.openproject.org/work_packages/22116)).
-  - An error which prevented managed remotes used for SVN to be
-    accessible on localhost has been fixed
-    ([#22095](https://community.openproject.org/work_packages/22095)).
-  - The watch icon did not update the list of watchers when the user was
-    on the watchers tab
-    ([#21946](https://community.openproject.org/work_packages/21946)).
-  - A redirect to work packages in private projects did not work when
-    the user had to login first
-    ([#21868](https://community.openproject.org/work_packages/21868)).
-  - The work package create button was not disabled while creating a
-    work package – leading to possible conflicts
-    ([#22070](https://community.openproject.org/work_packages/22070)).
-  - Several styling fixes have been applied
-    ([#22028](https://community.openproject.org/work_packages/22028),
-    [#22062](https://community.openproject.org/work_packages/22062)).
-  - A wrong English translation has been adjusted
-    ([#22092](https://community.openproject.org/work_packages/22092)).
+- An error in the documents plugin caused an error on the enumeration
+  page
+  ([#22093](https://community.openproject.org/work_packages/22093)).
+- A bug has been fixed which prevented custom fields for time tracking
+  to be displayed
+  ([#22116](https://community.openproject.org/work_packages/22116)).
+- An error which prevented managed remotes used for SVN to be
+  accessible on localhost has been fixed
+  ([#22095](https://community.openproject.org/work_packages/22095)).
+- The watch icon did not update the list of watchers when the user was
+  on the watchers tab
+  ([#21946](https://community.openproject.org/work_packages/21946)).
+- A redirect to work packages in private projects did not work when
+  the user had to login first
+  ([#21868](https://community.openproject.org/work_packages/21868)).
+- The work package create button was not disabled while creating a
+  work package – leading to possible conflicts
+  ([#22070](https://community.openproject.org/work_packages/22070)).
+- Several styling fixes have been applied
+  ([#22028](https://community.openproject.org/work_packages/22028),
+  [#22062](https://community.openproject.org/work_packages/22062)).
+- A wrong English translation has been adjusted
+  ([#22092](https://community.openproject.org/work_packages/22092)).

 In addition, new translations have been added to OpenProject and the
 plugins.
@@ -10,32 +10,32 @@ release_date: 2016-01-22

 OpenProject 5.0.10 contains several bug and accessibility fixes:

-  - An internal error has been fixed which occurred accessing a group
-    with an assigned custom field
-    ([#22518](https://community.openproject.org/work_packages/22518)).
-  - Several work package errors have been fixed
-    ([#22544](https://community.openproject.org/work_packages/22544),
-    [#21684](https://community.openproject.org/work_packages/21684),
-    [#21709](https://community.openproject.org/work_packages/21709),
-    [#22485](https://community.openproject.org/work_packages/22485),
-    [#22506](https://community.openproject.org/work_packages/22506)).
-  - A memory leak error which prevented work packages from being opened
-    on Safari (mobile or desktop) or Chrome (mobile) has been fixed
-    ([#22378](https://community.openproject.org/work_packages/22378)).
-  - The preview function for forums did not work when editing a comment.
-    This has been fixed
-    ([#21697](https://community.openproject.org/work_packages/21697)).
-  - The link to work packages in forum emails has been fixed
-    ([#22386](https://community.openproject.org/work_packages/22386)).
-  - Several design errors have been fixed
-    ([#22336](https://community.openproject.org/work_packages/22336),
-    [#22335](https://community.openproject.org/work_packages/22335),
-    [#22338](https://community.openproject.org/work_packages/22338),
-    [#22340](https://community.openproject.org/work_packages/22340),
-    [#22370](https://community.openproject.org/work_packages/22370),
-    [#22433](https://community.openproject.org/work_packages/22433),
-    [#19820](https://community.openproject.org/work_packages/19820)).
-  - Multiple accessibility improvements are included.
+- An internal error has been fixed which occurred accessing a group
+  with an assigned custom field
+  ([#22518](https://community.openproject.org/work_packages/22518)).
+- Several work package errors have been fixed
+  ([#22544](https://community.openproject.org/work_packages/22544),
+  [#21684](https://community.openproject.org/work_packages/21684),
+  [#21709](https://community.openproject.org/work_packages/21709),
+  [#22485](https://community.openproject.org/work_packages/22485),
+  [#22506](https://community.openproject.org/work_packages/22506)).
+- A memory leak error which prevented work packages from being opened
+  on Safari (mobile or desktop) or Chrome (mobile) has been fixed
+  ([#22378](https://community.openproject.org/work_packages/22378)).
+- The preview function for forums did not work when editing a comment.
+  This has been fixed
+  ([#21697](https://community.openproject.org/work_packages/21697)).
+- The link to work packages in forum emails has been fixed
+  ([#22386](https://community.openproject.org/work_packages/22386)).
+- Several design errors have been fixed
+  ([#22336](https://community.openproject.org/work_packages/22336),
+  [#22335](https://community.openproject.org/work_packages/22335),
+  [#22338](https://community.openproject.org/work_packages/22338),
+  [#22340](https://community.openproject.org/work_packages/22340),
+  [#22370](https://community.openproject.org/work_packages/22370),
+  [#22433](https://community.openproject.org/work_packages/22433),
+  [#19820](https://community.openproject.org/work_packages/19820)).
+- Multiple accessibility improvements are included.

 In addition the performance when saving a work package has been improved
 ([#21757](https://community.openproject.org/work_packages/21757)).
@@ -11,17 +11,17 @@ release_date: 2016-02-01

 OpenProject 5.0.12 contains several bug fixes:

-  - An error message on a work package page was not displayed properly.
-    This has been
-    resolved ([#21902](https://community.openproject.org/work_packages/21902)).
-  - The button to create versions was not displayed when only inherited
-    versions were displayed in a project. This has been
-    fixed ([#22599](https://community.openproject.org/work_packages/22599)).
-  - Several design issues have been resolved
-    ([#22564](https://community.openproject.org/work_packages/22564),
-    [#22570](https://community.openproject.org/work_packages/22570),
-    [#22571](https://community.openproject.org/work_packages/22571),
-    [#20683](https://community.openproject.org/work_packages/20683)).
+- An error message on a work package page was not displayed properly.
+  This has been
+  resolved ([#21902](https://community.openproject.org/work_packages/21902)).
+- The button to create versions was not displayed when only inherited
+  versions were displayed in a project. This has been
+  fixed ([#22599](https://community.openproject.org/work_packages/22599)).
+- Several design issues have been resolved
+  ([#22564](https://community.openproject.org/work_packages/22564),
+  [#22570](https://community.openproject.org/work_packages/22570),
+  [#22571](https://community.openproject.org/work_packages/22571),
+  [#20683](https://community.openproject.org/work_packages/20683)).

 For further information on the release, please refer to the  
 [Changelog v.5.0.12](https://community.openproject.org/versions/800)
@@ -10,20 +10,20 @@ release_date: 2016-02-05

 OpenProject 5.0.14 contains several bug fixes:

-  - User avatars were not displayed unless a specific admin setting was
-    selected. This has been adjusted
-    ([#22595](https://community.openproject.org/work_packages/22595)).
-  - Deleting a work package via bulk action was not possible when time
-    was logged on a work package. This has been fixed
-    ([#22485](https://community.openproject.org/work_packages/22485)).
-  - An error in the incoming emails functionality has been resolved
-    ([#22607](https://community.openproject.org/work_packages/22607)).
-  - Several design errors have been fixed
-    ([#20714](https://community.openproject.org/work_packages/20714),
-    [#22497](https://community.openproject.org/work_packages/22497),
-    [#22498](https://community.openproject.org/work_packages/22498),
-    [#22562](https://community.openproject.org/work_packages/22562),
-    [#22597](https://community.openproject.org/work_packages/22597)).
+- User avatars were not displayed unless a specific admin setting was
+  selected. This has been adjusted
+  ([#22595](https://community.openproject.org/work_packages/22595)).
+- Deleting a work package via bulk action was not possible when time
+  was logged on a work package. This has been fixed
+  ([#22485](https://community.openproject.org/work_packages/22485)).
+- An error in the incoming emails functionality has been resolved
+  ([#22607](https://community.openproject.org/work_packages/22607)).
+- Several design errors have been fixed
+  ([#20714](https://community.openproject.org/work_packages/20714),
+  [#22497](https://community.openproject.org/work_packages/22497),
+  [#22498](https://community.openproject.org/work_packages/22498),
+  [#22562](https://community.openproject.org/work_packages/22562),
+  [#22597](https://community.openproject.org/work_packages/22597)).

 For further information on the release, please refer to the  
 [Changelog v.5.0.14](https://community.openproject.org/versions/799)
@@ -11,19 +11,19 @@ release_date: 2016-02-16

 OpenProject 5.0.15 contains several bug fixes:

-  - The date on the project activity was based on UTC+0 and therefore
-    showed the wrong date when being in a different time zone
-    ([#22641](https://community.openproject.org/work_packages/22641)).
-  - When selecting a query and updating several work packages at once
-    using bulk edit, the focus was lost to the work package page. It now
-    remains on the query
-    ([#22330](https://community.openproject.org/work_packages/22330)).
-  - Due to an error the search text for queries in the dark theme was
-    not visible. This has been fixed
-    ([#22654](https://community.openproject.org/work_packages/22654)).
-  - Several design improvements have been
-    made ([#21338](https://community.openproject.org/work_packages/21338),
-    [#21794](https://community.openproject.org/work_packages/21794)).
+- The date on the project activity was based on UTC+0 and therefore
+  showed the wrong date when being in a different time zone
+  ([#22641](https://community.openproject.org/work_packages/22641)).
+- When selecting a query and updating several work packages at once
+  using bulk edit, the focus was lost to the work package page. It now
+  remains on the query
+  ([#22330](https://community.openproject.org/work_packages/22330)).
+- Due to an error the search text for queries in the dark theme was
+  not visible. This has been fixed
+  ([#22654](https://community.openproject.org/work_packages/22654)).
+- Several design improvements have been
+  made ([#21338](https://community.openproject.org/work_packages/21338),
+  [#21794](https://community.openproject.org/work_packages/21794)).

 In addition, the accessibility has been improved
 ([#21910](https://community.openproject.org/work_packages/21910),
@@ -8,41 +8,40 @@ release_date: 2016-03-08

 # OpenProject 5.0.16

-OpenProject 5.0.16 contains several bug
-    fixes:
+OpenProject 5.0.16 contains several bug fixes:

-  - Work package links (via \#\# and \#\#\#) in emails sent when
-    watching forums were not displayed properly. This has been fixed
-    ([#22728](https://community.openproject.org/work_packages/22728)).
-  - An error on the work package page has been fixed which caused
-    multiple work packages to be created when clicking the “Create”
-    button multiple times
-    ([#22735](https://community.openproject.org/work_packages/22735)).
-  - The selected work package type when creating a new child work
-    package was not based on the type order displayed in the
-    administration. This has been adjusted
-    ([#22639](https://community.openproject.org/work_packages/22639)).
-  - Due to an error the project list could not be accessed in the
-    accessibility mode. This has been fixed.
-  - The star icon in the project list showing which project the user is
-    a member in was missing. It has been added
-    ([#22692](https://community.openproject.org/work_packages/22692)).
-  - In the cost report, the cells were not displayed properly when
-    applying a grouping in the report. This has been fixed
-    ([#22762](https://community.openproject.org/work_packages/22762)).
-  - In the Task board the option to adjust the column width was only
-    shown when the burndown chart option was available. It has been
-    adjusted to always be displayed
-    ([#22297](https://community.openproject.org/work_packages/22297)).
-  - Several design issues have been fixed
-    ([#22805](https://community.openproject.org/work_packages/22805),
-    [#22802](https://community.openproject.org/work_packages/22802),
-    [#22803](https://community.openproject.org/work_packages/22803),
-    [#22732](https://community.openproject.org/work_packages/22732),
-    [#22716](https://community.openproject.org/work_packages/22716),
-    [#22705](https://community.openproject.org/work_packages/22705),
-    [#22686](https://community.openproject.org/work_packages/22686),
-    [#21902](https://community.openproject.org/work_packages/21902)).
+- Work package links (via \#\# and \#\#\#) in emails sent when
+  watching forums were not displayed properly. This has been fixed
+  ([#22728](https://community.openproject.org/work_packages/22728)).
+- An error on the work package page has been fixed which caused
+  multiple work packages to be created when clicking the “Create”
+  button multiple times
+  ([#22735](https://community.openproject.org/work_packages/22735)).
+- The selected work package type when creating a new child work
+  package was not based on the type order displayed in the
+  administration. This has been adjusted
+  ([#22639](https://community.openproject.org/work_packages/22639)).
+- Due to an error the project list could not be accessed in the
+  accessibility mode. This has been fixed.
+- The star icon in the project list showing which project the user is
+  a member in was missing. It has been added
+  ([#22692](https://community.openproject.org/work_packages/22692)).
+- In the cost report, the cells were not displayed properly when
+  applying a grouping in the report. This has been fixed
+  ([#22762](https://community.openproject.org/work_packages/22762)).
+- In the Task board the option to adjust the column width was only
+  shown when the burndown chart option was available. It has been
+  adjusted to always be displayed
+  ([#22297](https://community.openproject.org/work_packages/22297)).
+- Several design issues have been fixed
+  ([#22805](https://community.openproject.org/work_packages/22805),
+  [#22802](https://community.openproject.org/work_packages/22802),
+  [#22803](https://community.openproject.org/work_packages/22803),
+  [#22732](https://community.openproject.org/work_packages/22732),
+  [#22716](https://community.openproject.org/work_packages/22716),
+  [#22705](https://community.openproject.org/work_packages/22705),
+  [#22686](https://community.openproject.org/work_packages/22686),
+  [#21902](https://community.openproject.org/work_packages/21902)).

 Furthermore, the performance on the work package page has been improved
 ([#22586](https://community.openproject.org/work_packages/22586),
@@ -10,35 +10,35 @@ release_date: 2016-04-11

 OpenProject 5.0.17 contains several bug fixes:

-  - The work package attribute “Estimated time” could not be set back to zero once set
-    ([#22829](https://community.openproject.org/wp/22829)).
-  - The documents widget on My page could not be removed once added
-    ([#22814](https://community.openproject.org/wp/22814)).
-  - On small screens the login button was not displayed
-    ([#22945](https://community.openproject.org/wp/22945)).
-  - Several design bugs existed
-    ([#22833](https://community.openproject.org/wp/22833),
-    [#22836](https://community.openproject.org/wp/22836),
-    [#22876](https://community.openproject.org/wp/22876),
-    [#22906](https://community.openproject.org/wp/22906),
-    [#22907](https://community.openproject.org/wp/22907),
-    [#22936](https://community.openproject.org/wp/22936)).
-  - Several accessibility errors
-    existed ([#22935](https://community.openproject.org/wp/22935),
-    [#22948](https://community.openproject.org/wp/22948),
-    [#22957](https://community.openproject.org/wp/22957)).
+- The work package attribute “Estimated time” could not be set back to zero once set
+  ([#22829](https://community.openproject.org/wp/22829)).
+- The documents widget on My page could not be removed once added
+  ([#22814](https://community.openproject.org/wp/22814)).
+- On small screens the login button was not displayed
+  ([#22945](https://community.openproject.org/wp/22945)).
+- Several design bugs existed
+  ([#22833](https://community.openproject.org/wp/22833),
+  [#22836](https://community.openproject.org/wp/22836),
+  [#22876](https://community.openproject.org/wp/22876),
+  [#22906](https://community.openproject.org/wp/22906),
+  [#22907](https://community.openproject.org/wp/22907),
+  [#22936](https://community.openproject.org/wp/22936)).
+- Several accessibility errors
+  existed ([#22935](https://community.openproject.org/wp/22935),
+  [#22948](https://community.openproject.org/wp/22948),
+  [#22957](https://community.openproject.org/wp/22957)).

 In addition, there are several design and usability improvements:

-  - Several buttons for quick actions have been added to the project
-    page
-    ([#22808](https://community.openproject.org/wp/22808)).
-  - The design and usability of the wiki page has been improved
-    ([#22887](https://community.openproject.org/wp/22887)).
-  - In order to offer a better user experience for mobile users, the
-    tabs on the work package page are displayed at the bottom of the
-    page on small screens
-    ([#22953](https://community.openproject.org/wp/22953)).
+- Several buttons for quick actions have been added to the project
+  page
+  ([#22808](https://community.openproject.org/wp/22808)).
+- The design and usability of the wiki page has been improved
+  ([#22887](https://community.openproject.org/wp/22887)).
+- In order to offer a better user experience for mobile users, the
+  tabs on the work package page are displayed at the bottom of the
+  page on small screens
+  ([#22953](https://community.openproject.org/wp/22953)).

 For further information on the release, please refer to the
 [Changelog v.5.0.17](https://community.openproject.org/versions/805)
@@ -10,36 +10,36 @@ release_date: 2016-05-27

 OpenProject 5.0.18 contains several bug fixes:

-  - The wiki toolbar did not work. This has been fixed
-    ([#23050](https://community.openproject.org/wp/23050)).
-  - When a project contains no members the button to add a member on the
-    project overview was not displayed. Also the link on the button was
-    wrong. This has been fixed
-    ([#22970](https://community.openproject.org/wp/22970)).
-  - Some of the links on the landing page were wrong and have been
-    corrected
-    ([#22967](https://community.openproject.org/wp/22967)).
-  - An error preventing exported PDFs to be opened on Mac OS X El
-    Capitan has been fixed
-    ([#22730](https://community.openproject.org/wp/22730)).
-  - Gravatars were not properly loaded. This has been fixed
-    ([#5120](https://community.openproject.org/wp/5120)).
+- The wiki toolbar did not work. This has been fixed
+  ([#23050](https://community.openproject.org/wp/23050)).
+- When a project contains no members the button to add a member on the
+  project overview was not displayed. Also the link on the button was
+  wrong. This has been fixed
+  ([#22970](https://community.openproject.org/wp/22970)).
+- Some of the links on the landing page were wrong and have been
+  corrected
+  ([#22967](https://community.openproject.org/wp/22967)).
+- An error preventing exported PDFs to be opened on Mac OS X El
+  Capitan has been fixed
+  ([#22730](https://community.openproject.org/wp/22730)).
+- Gravatars were not properly loaded. This has been fixed
+  ([#5120](https://community.openproject.org/wp/5120)).

 In addition, there are several design and usability improvements:

-  - The styling for the documents module was missing. This has been
-    fixed
-    ([#23158](https://community.openproject.org/wp/23158)).
-  - Several improvements have been made to responsive / mobile layouts
-    ([#22953](https://community.openproject.org/wp/22953),
-    [#22944](https://community.openproject.org/wp/22944)).
-  - Several design errors have been fixed
-    ([#23109](https://community.openproject.org/wp/23109),
-    [#23104](https://community.openproject.org/wp/23104),
-    [#23052](https://community.openproject.org/wp/23052),
-    [#23046](https://community.openproject.org/wp/23046),
-    [#22997](https://community.openproject.org/wp/22997)).
-  - Many accessibility improvements have been made.
+- The styling for the documents module was missing. This has been
+  fixed
+  ([#23158](https://community.openproject.org/wp/23158)).
+- Several improvements have been made to responsive / mobile layouts
+  ([#22953](https://community.openproject.org/wp/22953),
+  [#22944](https://community.openproject.org/wp/22944)).
+- Several design errors have been fixed
+  ([#23109](https://community.openproject.org/wp/23109),
+  [#23104](https://community.openproject.org/wp/23104),
+  [#23052](https://community.openproject.org/wp/23052),
+  [#23046](https://community.openproject.org/wp/23046),
+  [#22997](https://community.openproject.org/wp/22997)).
+- Many accessibility improvements have been made.

 The textbox above a forum does now render textile. It’s therefore
 possible to e.g. include links or references
@@ -10,28 +10,28 @@ release_date: 2016-06-20

 OpenProject 5.0.19 contains several bug fixes:

-  - An error has been resolved which prevented the assignment of work
-    packages to groups when editing a work package
-    ([#23099](https://community.openproject.org/wp/23099)).
-  - An error in the calculation of the progress of work packages with
-    children has been fixed
-    ([#23251](https://community.openproject.org/wp/23251)).
-  - The burndown chart on the backlogs page was broken when a language
-    other than English was selected. This has been fixed
-    ([#23253](https://community.openproject.org/wp/23253)).
-  - The context menu on the backlogs page did not disappear when an
-    entry was selected. This has been resolved
-    ([#22837](https://community.openproject.org/wp/22837)).
-  - It was not possible to delete files attached to a budget. This has
-    been fixed
-    ([#23110](https://community.openproject.org/wp/23110)).
-  - When creating or editing budgets and assigning groups for the
-    planned labor costs, “Deleted user” was shown instead of the group
-    name. This has been resolved
-    ([#23057](https://community.openproject.org/wp/23057)).
-  - A security error has been fixed which allowed Angular injections in
-    texts
-    ([#23073](https://community.openproject.org/wp/23073)).
+- An error has been resolved which prevented the assignment of work
+  packages to groups when editing a work package
+  ([#23099](https://community.openproject.org/wp/23099)).
+- An error in the calculation of the progress of work packages with
+  children has been fixed
+  ([#23251](https://community.openproject.org/wp/23251)).
+- The burndown chart on the backlogs page was broken when a language
+  other than English was selected. This has been fixed
+  ([#23253](https://community.openproject.org/wp/23253)).
+- The context menu on the backlogs page did not disappear when an
+  entry was selected. This has been resolved
+  ([#22837](https://community.openproject.org/wp/22837)).
+- It was not possible to delete files attached to a budget. This has
+  been fixed
+  ([#23110](https://community.openproject.org/wp/23110)).
+- When creating or editing budgets and assigning groups for the
+  planned labor costs, “Deleted user” was shown instead of the group
+  name. This has been resolved
+  ([#23057](https://community.openproject.org/wp/23057)).
+- A security error has been fixed which allowed Angular injections in
+  texts
+  ([#23073](https://community.openproject.org/wp/23073)).

 For further information on the release, please refer to the
 [Changelog v.5.0.19](https://community.openproject.org/versions/810)
@@ -13,17 +13,17 @@ for the OpenProject core and plugins.

 The following bugs have been fixed with OpenProject 5.0.2:

-  - The link to create new forum boards was incorrect. It has been fixed
-    ([#22142](https://community.openproject.org/work_packages/22142)).
-  - Creating new documents (using the documents plugin) was not possible
-    due to an error. The bug has been fixed
-    ([#22140](https://community.openproject.org/work_packages/22140)).
-  - An error was resolved which prevented work packages from being
-    displayed when appending a slash at the end
-    ([#21997](https://community.openproject.org/work_packages/21997)).
-  - Several design fixes have been include
-    ([#22088](https://community.openproject.org/work_packages/22088),
-    [#21876](https://community.openproject.org/work_packages/21876)).
+- The link to create new forum boards was incorrect. It has been fixed
+  ([#22142](https://community.openproject.org/work_packages/22142)).
+- Creating new documents (using the documents plugin) was not possible
+  due to an error. The bug has been fixed
+  ([#22140](https://community.openproject.org/work_packages/22140)).
+- An error was resolved which prevented work packages from being
+  displayed when appending a slash at the end
+  ([#21997](https://community.openproject.org/work_packages/21997)).
+- Several design fixes have been include
+  ([#22088](https://community.openproject.org/work_packages/22088),
+  [#21876](https://community.openproject.org/work_packages/21876)).

 Additionally, the order of default roles has been changed
 ([#22044](https://community.openproject.org/work_packages/22044)).
@@ -10,9 +10,9 @@ release_date: 2015-11-24

 OpenProject 5.0.3 contains a bug fix for creating versions:

-  - It was not possible to create a version in the project settings if
-    there were no other version in a project
-    ([#22094](https://community.openproject.org/work_packages/22094)).
+- It was not possible to create a version in the project settings if
+  there were no other version in a project
+  ([#22094](https://community.openproject.org/work_packages/22094)).

 For further information on the release, please refer to the  
 [Changelog v.5.0.3](https://community.openproject.org/versions/782)
@@ -11,20 +11,20 @@ release_date: 2015-11-27
 OpenProject 5.0.4 contains several bug fixes and performance
 improvements:

-  - Copying projects works properly again
-    ([#22126](https://community.openproject.org/work_packages/22126)).
-  - Several work package related errors have been fixed
-    ([#22149](https://community.openproject.org/work_packages/22149),
-    [#22122](https://community.openproject.org/work_packages/22122),
-    [#21976](https://community.openproject.org/work_packages/21976),
-    [#21952](https://community.openproject.org/work_packages/21952)).
-  - The performance on the work package page has been improved
-    ([#22100](https://community.openproject.org/work_packages/22100),
-    [#22183](https://community.openproject.org/work_packages/22183)).
-  - In addition, several design bugs have been fixed
-    ([#22144](https://community.openproject.org/work_packages/22144),
-    [#22065](https://community.openproject.org/work_packages/22065),
-    [#22047](https://community.openproject.org/work_packages/22047)).
+- Copying projects works properly again
+  ([#22126](https://community.openproject.org/work_packages/22126)).
+- Several work package related errors have been fixed
+  ([#22149](https://community.openproject.org/work_packages/22149),
+  [#22122](https://community.openproject.org/work_packages/22122),
+  [#21976](https://community.openproject.org/work_packages/21976),
+  [#21952](https://community.openproject.org/work_packages/21952)).
+- The performance on the work package page has been improved
+  ([#22100](https://community.openproject.org/work_packages/22100),
+  [#22183](https://community.openproject.org/work_packages/22183)).
+- In addition, several design bugs have been fixed
+  ([#22144](https://community.openproject.org/work_packages/22144),
+  [#22065](https://community.openproject.org/work_packages/22065),
+  [#22047](https://community.openproject.org/work_packages/22047)).

 For further information on the release, please refer to the
 [Changelog v.5.0.4](https://community.openproject.org/versions/779)
--- a/Show More
+++ b/Show More