Merge pull request #23619 from opf/merge-release/17.5-20260609045502

Merge release/17.5 into dev
This commit is contained in:
Jens Ulferts
2026-06-09 10:07:07 +02:00
committed by GitHub
539 changed files with 6545 additions and 11769 deletions
@@ -4,6 +4,9 @@
@include text-shortener
min-width: 25px
max-width: 66%
// The label has a height of 18.5px. Half pixels are resolved differently by each OS/browser combination,
// resulting in cases where the bottom of the label was cut off
min-height: 19px
&--id
white-space: nowrap
+24 -17
View File
@@ -82,7 +82,7 @@ In OpenProject, authentication is an important element to guarantee a data prote
Backlogs is a [module](#module) in OpenProject that brings features that support [Agile project management](#agile-project-management), in particular the Scrum methodology, such as a product backlog and sprint backlogs.
It includes functionality for planning and managing sprints, including a sprint board that is automatically created when a sprint is started. Within the backlog, work packages can be organized using **backlog buckets** to group items into clearly defined sections. Work packages that are not assigned to a backlog bucket or a sprint are listed in the **index backlog**.
It includes functionality for planning and managing [sprints](#sprint), including a sprint [board](#board) that is automatically created when a sprint is started. Within the backlog, work packages can be organized using **backlog buckets** to group items into clearly defined sections. Work packages that are not assigned to a backlog bucket or a sprint are listed in the **inbox** backlog bucket.
To use backlogs in OpenProject, the Backlogs module has to be activated in the [project settings](#project-settings) by a project admin.
@@ -98,7 +98,7 @@ BIM stands for Building Information Modeling. In OpenProject, we offer a special
### Board
A board in OpenProject is a view that allows you to see your work packages as cards divided into columns. A board is a typical element in [agile project management](#agile-project-management), supporting methodologies such as Scrum or Kanban. OpenProject, you can use a [basic board](../user-guide/agile-boards/#basic-boards) or [advanced Action boards](../user-guide/agile-boards). Use advanced Action boards to quickly change attributes of your work package. [Read more about boards for agile project management](../user-guide/agile-boards/).
A board in OpenProject is a view that allows you to see your work packages as cards divided into columns. A board is a typical element in [agile project management](#agile-project-management), supporting methodologies such as Scrum or Kanban. In OpenProject, you can use a [basic board](../user-guide/agile-boards/#basic-boards) or [advanced Action boards](../user-guide/agile-boards). Use advanced Action boards to quickly change attributes of your work package. [Read more about boards for agile project management](../user-guide/agile-boards/).
**More information on boards in OpenProject**
@@ -200,7 +200,7 @@ Excel synchronization is an integration in OpenProject which allows you to easil
### File storage
File storages can be configured in the System Administration and then be selected in the [project settings](#project-settings). OpenProject offers a [Nextcloud integration](#nextcloud-integration) to support file storage. [More information on file storage with the Nextcloud integration](../user-guide/file-management/nextcloud-integration/).
File storages can be configured in the system administration and then be selected in the [project settings](#project-settings). OpenProject offers a [Nextcloud integration](#nextcloud-integration) to support file storage. [More information on file storage with the Nextcloud integration](../user-guide/file-management/nextcloud-integration/).
### Filters
@@ -218,11 +218,11 @@ The Gantt charts [module](#module) in OpenProject displays the work packages in
### Global modules
In OpenProject, global modules are defined as a menu to access all [modules](#module) for *all* your projects. With global modules you can easily see all your project-overarching information at one place, e.g. for work packages, boards, calendars or meetings. Click on the grid icon on the left side of the header menu to access the global modules. [Read more about global modules in OpenProject](../user-guide/home/global-modules/).
In OpenProject, global modules are defined as a menu to access all [modules](#module) for *all* your projects. With global modules you can easily see all your project-overarching information at one place, e.g. for [work packages](#work-package), [boards](#board), calendars or [meetings](#meetings). Click on the grid icon on the left side of the header menu to access the global modules. [Read more about global modules in OpenProject](../user-guide/home/global-modules/).
### Group
A group in OpenProject is defined as a list of users which can be added as a member to projects with a selected [role](#role). Groups can also be assigned to work packages. New groups can be defined in *Administration → Users and permissions → Groups*.
A group in OpenProject is defined as a list of users which can be added as a member to projects with a selected [role](#role). Groups can also be assigned to work packages. They can be nested to represent organizational structures and inherit permissions from parent groups. New groups can be defined in *Administration → Users and permissions → Groups*.
## H
@@ -343,7 +343,7 @@ OpenProject on-premises is a self-hosted version of OpenProject. As opposed to t
**More information on OpenProject on-premises**
- [See our pricing side about your options for OpenProject](https://www.openproject.org/pricing/).
- [See our pricing page about your options for OpenProject](https://www.openproject.org/pricing/).
- [Read a blog article comparing on-premises and cloud](https://www.openproject.org/blog/why-self-hosting-software/).
- [Read how to activate the Enterprise on-premises edition](../enterprise-guide/enterprise-on-premises-guide/activate-enterprise-on-premises/).
- [Read how to start a trial for Enterprise on-premises](../enterprise-guide/enterprise-on-premises-guide/enterprise-on-premises-trial/).
@@ -379,7 +379,7 @@ PM² is a project management framework developed by the European Commission to s
### PMflex
PMflex is is a comprehensive and flexible project management system based on the European [PM²](#pm--pm2) standard and further developed for public administration in Germany. [Read more about how to use PMflex with OpenProject](https://www.openproject.org/pmflex). If you are looking for specific PMflex terminology, please see our [use case of implementing PM² and PMflex project management in OpenProject](../use-cases/project-management-pm2-pmflex/#implementing-pm-and-pmflex-project-management-in-openproject).
PMflex is a comprehensive and flexible project management system based on the European [PM²](#pm--pm2) standard and further developed for public administration in Germany. [Read more about how to use PMflex with OpenProject](https://www.openproject.org/pmflex). If you are looking for specific PMflex terminology, please see our [use case of implementing PM² and PMflex project management in OpenProject](../use-cases/project-management-pm2-pmflex/#implementing-pm-and-pmflex-project-management-in-openproject).
### Portfolio
@@ -388,7 +388,7 @@ In OpenProject, you can manage your project portfolio by creating, filtering and
### Primer design system
OpenProject started adopting [Github's Primer Design System](https://primer.style/) in 2023. New features will be developed using Primer and existing features will will be gradually revised. Relevant reusable components from Primer as well as common patterns and compositions of these components will be documented in our [Lookbook](https://qa.openproject-edge.com/lookbook/pages/how_to_use). [Read more about OpenProject's decision to use Primer](https://www.openproject.org/blog/primer-design-system/).
OpenProject started adopting [Github's Primer Design System](https://primer.style/) in 2023. New features will be developed using Primer and existing features will be gradually revised. Relevant reusable components from Primer as well as common patterns and compositions of these components will be documented in our [Lookbook](https://qa.openproject-edge.com/lookbook/pages/how_to_use). [Read more about OpenProject's decision to use Primer](https://www.openproject.org/blog/primer-design-system/).
### Project
@@ -404,9 +404,7 @@ A project attribute in OpenProject is a [custom field](#custom-field) that appli
### Project folder
Project folders help collaborating in the most efficient way. They can be used with
OpenProject's [Nextcloud integration](#nextcloud-integration) or with
OpenProject's [OneDrive integration](#onedrive-integration). [Read more about project folders in OpenProject](../user-guide/projects/project-settings/files/#project-folders).
Project folders help collaborating in the most efficient way. They can be used with OpenProject's [Nextcloud integration](#nextcloud-integration) or with OpenProject's [OneDrive integration](#onedrive-integration). [Read more about project folders in OpenProject](../user-guide/projects/project-settings/files/#project-folders).
### Project home
@@ -437,7 +435,7 @@ Phases and phase gates are visible on the [project home](#project-home) page, in
### Project lists
In OpenProject, project lists are very useful for project portfolio managers to get an overview of all their [projects](#project) on the instance. Access your project lists on OpenProject by either navigating to the "All projects" menu and clicking on the "Project lists" button, or via the [Global modules](#global-modules). [Read more about project lists OpenProject](../user-guide/projects/project-lists/).
In OpenProject, project lists are very useful for project portfolio managers to get an overview of all their [projects](#project) on the instance. Access your project lists on OpenProject by either navigating to the "All projects" menu and clicking on the "Project lists" button, or via the [Global modules](#global-modules). [Read more about project lists in OpenProject](../user-guide/projects/project-lists/).
### Project navigation
@@ -481,7 +479,7 @@ In OpenProject, you can set work packages in relation to each other. Some relati
OpenProject offers different types of reminders so that you can lean back and never forget a task. One is the [date alert](#date-alerts) (Enterprise add-on), which generates automatic and customized [notifications](#notifications) regarding a work package's due date or start date.
OpenProject also allows you to set **work package reminders**: Simply activate the clock icon on top of a work package and choose from different options, e.g. to be reminded the next day (at 9 am) or in one week. You can also set a custom date. [Read more about work package reminders in OpenProject](../user-guide/work-packages/edit-work-package/#work-package-reminders).
OpenProject also allows you to set **work package reminders**: Simply activate the clock icon on top of a work package and choose from different options, e.g. to be reminded the next day (at 9 am) or in one week. You can also set a custom date. [Read more about work package reminders in OpenProject](../user-guide/work-packages/edit-work-package/#work-package-reminders).
### Repository
@@ -509,6 +507,10 @@ SAML (Security Assertion Markup Language) is an open standard for exchanging aut
OpenProject offers the possibility to share work packages with external groups or users that are not [members](#member) of the project. This feature is an [Enterprise add-on](#enterprise-add-on). Every user with whom a work package is shared must either already be a user of the instance or be newly created. The latter requires special rights. [Read more about OpenProject's feature to share work packages with project non-members](../user-guide/work-packages/share-work-packages/).
### Sprint
A sprint is a time-boxed iteration used in agile project management to plan and execute work during a defined period. In OpenProject, sprints are managed through the [Backlogs](#backlogs) module and include attributes such as start and end dates. Sprint [boards](#board) are automatically created when a sprint is started.
### Story points
Story points is a term known in Scrum. They are defined as numbers assigned to a [work package](#work-package) used to estimate (relatively) the size of the work. In OpenProject, you can add story points to work packages. [Read how to work with story points in OpenProject](../user-guide/backlogs-scrum/#story-points).
@@ -545,7 +547,7 @@ The OpenProject [user guide](../user-guide/) is an in-depth guide of all feature
### Versions
Versions in OpenProject are defined as an attribute for [work packages](#work-package) or in the [Backlogs](#backlogs) module. Versions will be displayed in the [Roadmap](#roadmap). In the [Enterprise edition](#enterprise-add-on), you can also create a version [board](#board) to get an overview of the progress of your versions. [Read more about how to manage versions in OpenProject](../user-guide/projects/project-settings/versions/).
Versions in OpenProject are used to group and organize work packages, for example to plan releases, milestones, or delivery targets. Versions are displayed in the [Roadmap](#roadmap) and can be assigned to work packages as an attribute. You can also create a version [board](#board) to get an overview of the progress of your versions. [Read more about how to manage versions in OpenProject](../user-guide/projects/project-settings/versions/).
## W
@@ -569,7 +571,8 @@ In OpenProject, a wiki is defined as a [module](#module) that allows to use wiki
### Work, Remaining Work and % Complete
In OpenProject, '**Work**' refers to a work package attribute indicating the estimated hours and days needed to complete a task.
In OpenProject, '**Work**' refers to a work package attribute indicating the estimated hours and days needed to complete a task.
'**Remaining work**' is a work package attribute that shows how much work is left to finish the work package. It is automatically calculated if you work with [status-based progress reporting](../user-guide/time-and-costs/progress-tracking/#status-based-progress-reporting). And '**% Complete**' is an automatically calculated work package attribute that shows in percentage how much work is already completed. All three attributes are important for [progress reporting with OpenProject](https://www.openproject.org/blog/changes-progress-work-estimates/).
To make it easier for project managers to work with work package hierarchies, OpenProject also displays a value (in blue) for the total amount of work in the Work field for parent work packages next to the value for the dedicated work package. This **total work value** is the sum of the work value of the parent work package and all the work values of its children. The same principle applies to the work package attribute Remaining Work. [Read in our user guide about how to configure a work package](../user-guide/work-packages/work-package-table-configuration/)
@@ -599,7 +602,11 @@ If you need a Category that applies to all projects on your instance, we recomme
### Work package ID
Work package ID is defined as a unique ascending number assigned to a newly created work package. Work package IDs cannot be changed and are numbered across all projects of an OpenProject instance (therefore, the numbering within a project may not be sequential).
In OpenProject, every work package has a unique ID (identifier). It is automatically assigned when a work package is created. Work package IDs are configured globally and apply across the entire OpenProject instance.
By default, work package IDs are numerical, ascending numbers, for example #429. System [administrators](#admin) can optionally switch to project-based work package IDs, which consist of a project-specific prefix and an ascending number (e.g. OP-382). Project-based identifiers that have been used are [reserved and can be released if necessary](../system-admin-guide/projects/reserved-project-identifiers/) so that they can be used again.
Administrators can configure work package identifiers under *Administration → Work packages → Identifiers*. [Read more in the OpenProject system admin guide](../user-guide/projects/project-settings/project-information/#change-project-identifier).
### Work package subject
@@ -617,7 +624,7 @@ Work package types are the different items a work package can represent. Each wo
### Work package view
A list of work packages is considered a view. The containing work packages in any view can be displayed a number of different ways. Examples for most used work package views are the [table view](#work-package-table), the full screen view or the split screen view. You can also display work packages in a card view and use them in a [board](#board) to use agile methods. [Read more about work package views in OpenProject](../user-guide/work-packages/work-package-views/#work-packages-views).
A list of work packages is considered a view. The containing work packages in any view can be displayed a number of different ways. Examples for most used work package views are the [table view](#work-package-table), the full screen view or the split screen view. You can also display work packages in a card view and use them in a [board](#board) to use agile methods. [Read more about work package views in OpenProject](../user-guide/work-packages/work-package-views/#work-packages-views).
### WYSIWYG editor
+80
View File
@@ -0,0 +1,80 @@
---
title: OpenProject 17.3.3
sidebar_navigation:
title: 17.3.3
release_version: 17.3.3
release_date: 2026-06-08
---
# OpenProject 17.3.3
Release date: 2026-06-08
We released [OpenProject 17.3.3](https://community.openproject.org/versions/2299).
The release contains several bug fixes and we recommend updating to the newest version.
Below you will find a complete list of all changes and bug fixes.
<!-- BEGIN SECURITY FIXES AUTOMATED SECTION -->
## Security fixes
### CVE-2026-47193 - Journal diff endpoint bypasses object, journal, and field visibility checks
This vulnerability was reported as part of the [YesWeHack.com OpenProject Bug Bounty program](https://yeswehack.com/programs/openproject), sponsored by the European Commission.
For more information, please see the [GitHub advisory #GHSA-f2rx-x2qj-2hgj](https://github.com/opf/openproject/security/advisories/GHSA-f2rx-x2qj-2hgj)
### GHSA-3vpx-94qx-xpw6 - IDOR through /projects/<A>/settings/project_storages/<A_ps_id> via PATCH parameter "storages_project_storage[project_folder_id]" leads to Access to Unauthorized Resources
A project-admin in one project can hijack the managed Nextcloud or OneDrive folder of another project on the same storage by writing the victim project&#39;s `project_folder_id` into the attacker&#39;s `Storages::ProjectStorage` row. The next managed-folder sync overwrites the ACL on the referenced folder with the attacker project&#39;s user list.
This vulnerability was reported as part of the [YesWeHack.com OpenProject Bug Bounty program](https://yeswehack.com/programs/openproject), sponsored by the European Commission.
For more information, please see the [GitHub advisory #GHSA-3vpx-94qx-xpw6](https://github.com/opf/openproject/security/advisories/GHSA-3vpx-94qx-xpw6)
### GHSA-6crw-7f5r-4qj9 - CSRF on TARGET through /users/:id via POST parameter "user[admin]"
Turbo Drive auto-injects CSRF tokens (from `<meta name="csrf-token">`) on forms injected via the XSS&#39;s `append` Turbo Stream action. A second action, `dispatch_event` with `name="submit"`, auto-submits the form with no victim interaction beyond viewing the work package, resulting in a CSRF attack
This vulnerability was reported as part of the [YesWeHack.com OpenProject Bug Bounty program](https://yeswehack.com/programs/openproject), sponsored by the European Commission.
For more information, please see the [GitHub advisory #GHSA-6crw-7f5r-4qj9](https://github.com/opf/openproject/security/advisories/GHSA-6crw-7f5r-4qj9)
### GHSA-98vw-2r87-fx2r - SQL injection in timestamps functionality
OpenProject baseline comparison allows callers to request historic work-package attributes using the `timestamps` parameter.
The timestamp parser accepts a relative date keyword on the first line because its regular expression uses line anchors. The parser validates the input, but the original multi-line string is kept and later interpolated into a raw SQL `CASE ... THEN '<timestamp>'` expression.
An authenticated user who can save a query can persist a timestamp array value containing literal commas and trigger a top-level data-modifying CTE. This gives the attacker a generic database write primitive as the OpenProject application database role.
The demonstrated impact is administrator privilege escalation: the attacker uses that write primitive to update their own account record, setting the account&#39;s administrator flag to true. The same injection also allows in-band data disclosure through work-package timestamp metadata.
This vulnerability was reported as part of the [YesWeHack.com OpenProject Bug Bounty program](https://yeswehack.com/programs/openproject), sponsored by the European Commission.
For more information, please see the [GitHub advisory #GHSA-98vw-2r87-fx2r](https://github.com/opf/openproject/security/advisories/GHSA-98vw-2r87-fx2r)
### GHSA-h83w-5q5x-pq27 - Information Disclosure (cleartext storage of data) on localhost through memcached via Others "storage.<id>.httpx_access_token" leads to Sensitive Data Exposure
OpenProject&#39;s Storages module writes the OneDrive/SharePoint userless OAuth `access_token` plaintext to `Rails.cache` under the deterministic key `storage.<id>.httpx_access_token`, repopulated continuously by an hourly cron and every userless-OAuth call site (see Write cadence). None of the three allowed cache backends (`file_store`, `memcache`, `redis`) encrypts at rest. An attacker with read access to the cache backend recovers the Azure-AD application-tier bearer with an anonymous `get` over the memcached binary protocol (or the equivalent against Redis)
This vulnerability was reported as part of the [YesWeHack.com OpenProject Bug Bounty program](https://yeswehack.com/programs/openproject), sponsored by the European Commission.
For more information, please see the [GitHub advisory #GHSA-h83w-5q5x-pq27](https://github.com/opf/openproject/security/advisories/GHSA-h83w-5q5x-pq27)
### GHSA-q33w-f822-hg8x - Stored XSS on openproject.example.com through /api/v3/projects/{project}/work_packages via POST parameter "description"
The HTML sanitizer grants `<macro>` elements unrestricted `data-*` attributes via `:data` wildcard. An attacker injects `data-controller="poll-for-changes"` into a work package description, causing Stimulus.js to mount a controller that fetches an attacker-uploaded attachment and passes it to `renderStreamMessage()`. This executes arbitrary Turbo Stream actions — including `redirect_to` — in every victim&#39;s authenticated browser session, redirecting them to an attacker-controlled server.
This vulnerability was reported as part of the [YesWeHack.com OpenProject Bug Bounty program](https://yeswehack.com/programs/openproject), sponsored by the European Commission.
For more information, please see the [GitHub advisory #GHSA-q33w-f822-hg8x](https://github.com/opf/openproject/security/advisories/GHSA-q33w-f822-hg8x)
### GHSA-qj96-f42f-6336 - Cache store poisoning leads to Remote Code Execution (RCE)
This vulnerability was reported as part of the [YesWeHack.com OpenProject Bug Bounty program](https://yeswehack.com/programs/openproject), sponsored by the European Commission.
For more information, please see the [GitHub advisory #GHSA-qj96-f42f-6336](https://github.com/opf/openproject/security/advisories/GHSA-qj96-f42f-6336)
<!-- END SECURITY FIXES AUTOMATED SECTION -->
<!--more-->
## Bug fixes and changes
<!-- Warning: Anything within the below lines will be automatically removed by the release script -->
<!-- BEGIN AUTOMATED SECTION -->
<!-- END AUTOMATED SECTION -->
<!-- Warning: Anything above this line will be automatically removed by the release script -->
+28
View File
@@ -0,0 +1,28 @@
---
title: OpenProject 17.3.4
sidebar_navigation:
title: 17.3.4
release_version: 17.3.4
release_date: 2026-06-08
---
# OpenProject 17.3.4
Release date: 2026-06-08
We released [OpenProject 17.3.4](https://community.openproject.org/versions/2305).
The release contains several bug fixes and we recommend updating to the newest version.
Below you will find a complete list of all changes and bug fixes.
<!-- BEGIN SECURITY FIXES AUTOMATED SECTION -->
<!-- END SECURITY FIXES AUTOMATED SECTION -->
<!--more-->
## Bug fixes and changes
<!-- Warning: Anything within the below lines will be automatically removed by the release script -->
<!-- BEGIN AUTOMATED SECTION -->
- Bugfix: Memcached serialization is broken in 17.3.3 \[[#75753](https://community.openproject.org/wp/75753)\]
<!-- END AUTOMATED SECTION -->
<!-- Warning: Anything above this line will be automatically removed by the release script -->
+92
View File
@@ -0,0 +1,92 @@
---
title: OpenProject 17.4.1
sidebar_navigation:
title: 17.4.1
release_version: 17.4.1
release_date: 2026-06-08
---
# OpenProject 17.4.1
Release date: 2026-06-08
We released [OpenProject 17.4.1](https://community.openproject.org/versions/2301).
The release contains several bug fixes and we recommend updating to the newest version.
Below you will find a complete list of all changes and bug fixes.
<!-- BEGIN SECURITY FIXES AUTOMATED SECTION -->
## Security fixes
### CVE-2026-47193 - Journal diff endpoint bypasses object, journal, and field visibility checks
This vulnerability was reported as part of the [YesWeHack.com OpenProject Bug Bounty program](https://yeswehack.com/programs/openproject), sponsored by the European Commission.
For more information, please see the [GitHub advisory #GHSA-f2rx-x2qj-2hgj](https://github.com/opf/openproject/security/advisories/GHSA-f2rx-x2qj-2hgj)
### CVE-2026-49355 - Private work package data disclosure through single meeting agenda item API
`GET /api/v3/meetings/:meeting_id/agenda_items/:agenda_item_id` discloses private work package data from a linked work package that belongs to a private/inaccessible project.
This vulnerability was reported as part of the [YesWeHack.com OpenProject Bug Bounty program](https://yeswehack.com/programs/openproject), sponsored by the European Commission.
For more information, please see the [GitHub advisory #GHSA-g387-6rm2-xw88](https://github.com/opf/openproject/security/advisories/GHSA-g387-6rm2-xw88)
### GHSA-3vpx-94qx-xpw6 - IDOR through /projects/<A>/settings/project_storages/<A_ps_id> via PATCH parameter "storages_project_storage[project_folder_id]" leads to Access to Unauthorized Resources
A project-admin in one project can hijack the managed Nextcloud or OneDrive folder of another project on the same storage by writing the victim project&#39;s `project_folder_id` into the attacker&#39;s `Storages::ProjectStorage` row. The next managed-folder sync overwrites the ACL on the referenced folder with the attacker project&#39;s user list.
This vulnerability was reported as part of the [YesWeHack.com OpenProject Bug Bounty program](https://yeswehack.com/programs/openproject), sponsored by the European Commission.
For more information, please see the [GitHub advisory #GHSA-3vpx-94qx-xpw6](https://github.com/opf/openproject/security/advisories/GHSA-3vpx-94qx-xpw6)
### GHSA-6crw-7f5r-4qj9 - CSRF on TARGET through /users/:id via POST parameter "user[admin]"
Turbo Drive auto-injects CSRF tokens (from `<meta name="csrf-token">`) on forms injected via the XSS&#39;s `append` Turbo Stream action. A second action, `dispatch_event` with `name="submit"`, auto-submits the form with no victim interaction beyond viewing the work package, resulting in a CSRF attack
This vulnerability was reported as part of the [YesWeHack.com OpenProject Bug Bounty program](https://yeswehack.com/programs/openproject), sponsored by the European Commission.
For more information, please see the [GitHub advisory #GHSA-6crw-7f5r-4qj9](https://github.com/opf/openproject/security/advisories/GHSA-6crw-7f5r-4qj9)
### GHSA-98vw-2r87-fx2r - SQL injection in timestamps functionality
OpenProject baseline comparison allows callers to request historic work-package attributes using the `timestamps` parameter.
The timestamp parser accepts a relative date keyword on the first line because its regular expression uses line anchors. The parser validates the input, but the original multi-line string is kept and later interpolated into a raw SQL `CASE ... THEN '<timestamp>'` expression.
An authenticated user who can save a query can persist a timestamp array value containing literal commas and trigger a top-level data-modifying CTE. This gives the attacker a generic database write primitive as the OpenProject application database role.
The demonstrated impact is administrator privilege escalation: the attacker uses that write primitive to update their own account record, setting the account&#39;s administrator flag to true. The same injection also allows in-band data disclosure through work-package timestamp metadata.
This vulnerability was reported as part of the [YesWeHack.com OpenProject Bug Bounty program](https://yeswehack.com/programs/openproject), sponsored by the European Commission.
For more information, please see the [GitHub advisory #GHSA-98vw-2r87-fx2r](https://github.com/opf/openproject/security/advisories/GHSA-98vw-2r87-fx2r)
### GHSA-h83w-5q5x-pq27 - Information Disclosure (cleartext storage of data) on localhost through memcached via Others "storage.<id>.httpx_access_token" leads to Sensitive Data Exposure
OpenProject&#39;s Storages module writes the OneDrive/SharePoint userless OAuth `access_token` plaintext to `Rails.cache` under the deterministic key `storage.<id>.httpx_access_token`, repopulated continuously by an hourly cron and every userless-OAuth call site (see Write cadence). None of the three allowed cache backends (`file_store`, `memcache`, `redis`) encrypts at rest. An attacker with read access to the cache backend recovers the Azure-AD application-tier bearer with an anonymous `get` over the memcached binary protocol (or the equivalent against Redis)
This vulnerability was reported as part of the [YesWeHack.com OpenProject Bug Bounty program](https://yeswehack.com/programs/openproject), sponsored by the European Commission.
For more information, please see the [GitHub advisory #GHSA-h83w-5q5x-pq27](https://github.com/opf/openproject/security/advisories/GHSA-h83w-5q5x-pq27)
### GHSA-q33w-f822-hg8x - Stored XSS on openproject.example.com through /api/v3/projects/{project}/work_packages via POST parameter "description"
The HTML sanitizer grants `<macro>` elements unrestricted `data-*` attributes via `:data` wildcard. An attacker injects `data-controller="poll-for-changes"` into a work package description, causing Stimulus.js to mount a controller that fetches an attacker-uploaded attachment and passes it to `renderStreamMessage()`. This executes arbitrary Turbo Stream actions — including `redirect_to` — in every victim&#39;s authenticated browser session, redirecting them to an attacker-controlled server.
This vulnerability was reported as part of the [YesWeHack.com OpenProject Bug Bounty program](https://yeswehack.com/programs/openproject), sponsored by the European Commission.
For more information, please see the [GitHub advisory #GHSA-q33w-f822-hg8x](https://github.com/opf/openproject/security/advisories/GHSA-q33w-f822-hg8x)
### GHSA-qj96-f42f-6336 - Cache store poisoning leads to Remote Code Execution (RCE)
This vulnerability was reported as part of the [YesWeHack.com OpenProject Bug Bounty program](https://yeswehack.com/programs/openproject), sponsored by the European Commission.
For more information, please see the [GitHub advisory #GHSA-qj96-f42f-6336](https://github.com/opf/openproject/security/advisories/GHSA-qj96-f42f-6336)
<!-- END SECURITY FIXES AUTOMATED SECTION -->
<!--more-->
## Bug fixes and changes
<!-- Warning: Anything within the below lines will be automatically removed by the release script -->
<!-- BEGIN AUTOMATED SECTION -->
- Bugfix: Migration 20250929070310 failing due to update code failing on not-yet fully migrated schema \[[#75286](https://community.openproject.org/wp/75286)\]
<!-- END AUTOMATED SECTION -->
<!-- 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 Alexander Aleschenko.
+21
View File
@@ -13,6 +13,27 @@ Stay up to date and get an overview of the new features included in the releases
<!--- New release notes are generated below. Do not remove comment. -->
<!--- RELEASE MARKER -->
## 17.3.4
Release date: 2026-06-08
[Release Notes](17-3-4/)
## 17.4.1
Release date: 2026-06-08
[Release Notes](17-4-1/)
## 17.3.3
Release date: 2026-06-08
[Release Notes](17-3-3/)
## 17.4.0
Release date: 2026-05-13
@@ -20,45 +20,64 @@ To manage users click on your avatar (top right corner) and select **Administrat
In the Community edition there is no limit to the number of users. In Enterprise editions (cloud and on-premises) the user limit is based on your subscription. The number of users for your subscription is thus not bound to names. For example, if you block a user you can add a new one without upgrading.
| Topic | Content |
| ----------------------------------------------- | -------------------------------------------------------- |
| [User list](#user-list) | Manage all users in OpenProject. |
| [Filter users](#filter-users) | Filter users in the list. |
| [Lock and unlock users](#lock-and-unlock-users) | Block a user permanently in the system or unlock a user. |
| [Create users](#create-users) | Invite or create new users. Resend or delete user invitations |
| [Manage user settings](#manage-user-settings) | Manage user details. |
| [Authentication](#authentication) | Set and use authentication methods. |
| [Delete users](#delete-users) | Delete a user from the system. |
| Topic | Content |
| ----------------------------------------------- | ------------------------------------------------------------ |
| [User list](#user-list) | Manage all users in OpenProject. |
| [Filter users](#filter-users) | Filter users in the list. |
| [Configure view](#configure-view) | Configure how user information is displayed. |
| [Lock and unlock users](#lock-and-unlock-users) | Block a user permanently in the system or unlock a user. |
| [Create users](#create-users) | Invite or create new users. Resend or delete user invitations |
| [Manage user settings](#manage-user-settings) | Manage user details. |
| [Authentication](#authentication) | Set and use authentication methods. |
| [Delete users](#delete-users) | Delete a user from the system. |
## User list
The User list is where users are managed. They can be added, edited or deleted from this list, which can be filtered if required.
![openproject_system_admin_guide_users_list](openproject_system_admin_guide_users_list.png)
![List of users under OpenProject administration](openproject_system_admin_guide_users_list.png)
Column headers can be clicked to toggle sort direction. Arrows indicate sort order, up for ascending (a-z/0-9) and down for descending (z-a/9-0). Paging controls are shown at the bottom of the list. You will also see whether a user is a system administrator in OpenProject.
## Filter users
At the top of the user list is a filter box. Filter by status. group or name, then click the green **Apply** button to filter the list. Click the **Clear** button to reset the filter fields and refresh the list.
To filter for users, begin by clicking the **Filters** button.
* **Status** - select from Active, All or Locked Temporarily. Each selection shows the number of users.
* **Group** - select from the list of existing groups.
* **Name** - enter any text; this can contain a "%" wild card for 0 or more characters. The filter applies to user name, first name, last name and email address.
!["Filters" button to filter through users list in OpenProject administration](openproject_systemguide_filters_button.png)
![Filter users in OpenProject](openproject_systemguide_filter_users.png)
Clicking on it opens up the **+Add filter** form. Here, you can filter by group, status, name or username, and your list is automatically updated. Each filter button displays additional filtering options to help you narrow down results. The results are then filtered based on the selected criteria. Click the **x** symbol in front of each selected filter to clear the filter and the **x** symbol at the **top-right corner** to close the form.
![Add filter form](openproject_systemguide_add_filters.png)
- **Username** - enter any text or character like @, .com which is unique to the user list.
- **Name** - enter any text; this can contain a "%" wild card for 0 or more characters. For example, if you are filtering for a user named Niklas but are unsure if it's Niklas, Niclas, Nikolas, or Nicholas, you can search for “Ni%las” and all matching users will be listed. The filter applies to first name, last name and email address.
- **Group** - select from the list of existing groups.
- **Status** - select from Active, Registered, Locked, Invited, Deleted. Each selection shows the number of users.
![Filters for user list in OpenProject administration](openproject_systemguide_filter_users.png)
## Configure view
To configure how the table of users is displayed, click on the More menu **(...)**.
![Menu for configure view for the user list in OpenProject administration](openproject_systemguide_configure_view.png)
This opens up a form where you can add columns, or manage and reorder columns via drag and drop. Click **Apply** to save your changes.
![Open form to configure view for the user list in OpenProject administration](openproject_systemguide_configure_view_form.png)
## Lock and unlock users
Handling locking and unlocking of users is also done from the user list. To disable a user's access click the **Lock permanently** link next to a user. Use the **Unlock** link to restore the user's access.
Handling locking and unlocking of users is also done from the user list. To disable a user's access click, the **Lock permanently** link next to a user. Use the **Unlock** link to restore the user's access.
If you are using [Enterprise cloud](../../../enterprise-guide/enterprise-cloud-guide) or [Enterprise on-premises](../../../enterprise-guide/enterprise-on-premises-guide) locking a user will free up a user license and so you could add another user to the system within your booked plan.
> **Note**: The previous activities from a locked user will still be displayed in the system.
> [!NOTE]
> The previous activities from a locked user will still be displayed in the system.
![Lock users in OpenProject](open_project_system_admin_lock_user_permanently.png)
If a user has repeated failed logins the user will be locked temporarily and a **Reset failed logins** link will be shown in the user list. Click the link to unlock it right away, or wait and it will be unlocked automatically. Have a look at the section [Other authentication settings](../../authentication/login-registration-settings/) for failed attempts and time blocked.
If a user has repeated failed logins, the user will be locked temporarily and a **Reset failed logins** link will be shown in the user list. Click the link to unlock it right away, or wait and it will be unlocked automatically. Have a look at the section [Other authentication settings](../../authentication/login-registration-settings/) for failed attempts and time blocked.
## Create users
@@ -75,7 +94,7 @@ Enter the email address, first name, and last name of the new user. Tick the box
Note: the email field must be a valid format and be unique or it will be rejected on clicking the button.
Click the **Create** button to add the user and show that user's details page. Click the **Create and continue** button to add the user and stay on the new user form to add another user. Either way, the new user will be invited via email.
When adding the last of multiple users you can click on **Create** or click the **Users** link in the menu on the left. The **Users list** will be shown. Click on the name of each user to [edit their details](#set-initial-details).
When adding the last of multiple users you can click on **Create** or click the **Users** link in the menu on the left. The **Users list** will be shown. Click on the name of each user to [edit their details](#set-initial-details).
### Create user (via self-registration)
@@ -110,8 +129,10 @@ In the top right, click the **Send invitation** button in order to send the emai
### Delete user invitations
To invalidate or revoke a user's invitation click on the user name and then on **Delete** in the upper right corner. This will prevent the invited user from logging in.
Please note: this only works for users who haven't logged in yet. If the user is already active this will delete his/her whole profile and account. Deleting users can't be revoked.
To invalidate or revoke a user's invitation, click on the user name and then on **Delete** in the upper right corner. This will prevent the invited user from logging in.
> [!NOTE]
> This only works for users who haven't logged in yet. If the user is already active, this will delete his/her whole profile and account. Deleting users can't be revoked.
## Manage user settings
@@ -119,11 +140,11 @@ You can manage individual user details if you click on the user name in the list
### General settings
![administration-user-settings-manage-user](openproject_system_guide_general_tab.png)
![Settings to manage a user under OpenProject administration](openproject_system_guide_general_tab.png)
On the **General** tab the following fields are shown:
1. User's master date
1. User's master data
- **Status** - this is set by the system.
- **Username** - this defaults to the email address for a new user (unless the user used the self registration). It can be changed on this page. Users cannot change their own user name.
- **First name**, **Last name**, **Email** - these fields are filled from the **New user** page. Users can change them under their **Profile** page; they are mandatory.
@@ -139,7 +160,7 @@ On the **General** tab the following fields are shown:
To create a new password for a user (e.g. if he/she lost it) navigate to the **Authentication** section of the **General** tab. You can either **Assign a random password** (check the box on top) or set a new password manually and send it to them (preferably through secured communication). Consider checking the box next to **Enforce password change on next login**.
![reset-user-password](Authentication.png)
![Reset user password under OpenProject administration](Authentication.png)
### Add users to a project
@@ -147,19 +168,20 @@ In order to see and work in a project, a user has to be a member of a project an
On the **Projects** tab, select the new project from the drop-down list, choose the [roles](../roles-permissions) for this project and click the green **Add** button.
![Sysadmin add project](Sys-admin-add-project1.gif)
![Add users to a project under OpenProject system administration](Sys-admin-add-project1.gif)
### Add users to groups
On the **Groups** tab you can see the groups the user belongs to. If a group is shown, click the group name link.
![User groups](system_guide_user_groups.png)
![User groups in OpenProject administration](system_guide_user_groups.png)
If no groups are shown (i.e. the user does not belong to any group, yet), click the **Manage groups** link to [edit groups](../groups).
![Manage Groups](system_guide_manage_groups.png)
![Manage groups in OpenProject administration](system_guide_manage_groups.png)
**Please note**: The **Groups** tab is only shown if at least one user group exists in OpenProject.
> [!NOTE]
> The **Groups** tab is only shown if at least one user group exists in OpenProject.
### Global roles
@@ -167,7 +189,7 @@ In order to add a global role to a user, at least one global role needs to be [c
On the **Global roles** tab, select or de-select the global role(s) for this user. Click the **Add** button.
![Add global roles](openproject_system_guide_add_global_roles.png)
![Add global user roles in OpenProject administration](openproject_system_guide_add_global_roles.png)
### Notification settings
@@ -181,13 +203,13 @@ Under **Email reminders** tab you can edit the [email reminders settings](../../
The rate history tab shows the hourly rates that have been defined for the user. The **Default rate** is applied to projects with no rate defined. All projects that the user is a member of are listed with the user's rates.
The **Valid from** date will effect the rate used when creating a [budget](../../../user-guide/budgets/) and when [logging time](../../../user-guide/time-and-costs/time-tracking/).
The **Valid from** date will affect the rate used when creating a [budget](../../../user-guide/budgets/) and when [logging time](../../../user-guide/time-and-costs/time-tracking/).
If you want to set a different hourly rate for the user on different projects, you can overwrite the default rate with a different rate below in the respective projects.
To enter a new hourly rate, click on the **Update** icon next to the rate history. You can either set a **default hourly rate** or define a rate for a certain project.
![set-hourly-rate-administration](system_guide_rate_history.png)
![Set hourly rates for users in OpenProject administrationin OpenProject administration](system_guide_rate_history.png)
1. Enter a date from which the rate is **Valid from**.
2. Enter the (hourly) **Rate**. The currency can only be changed in the [respective settings](../../time-and-costs).
@@ -199,10 +221,9 @@ To enter a new hourly rate, click on the **Update** icon next to the rate histor
### Avatar
The **Avatar** tab shows the default icon to be shown for this user. A custom image can be uploaded as the avatar. In addition, users can also use their [Gravatar](https://en.wikipedia.org/wiki/Gravatar). User can manage this under their [profile settings](../../../user-guide/account-settings/#set-an-avatar). These features can be disabled in the [avatar settings](../avatars).
The **Avatar** tab shows the default icon to be shown for this user. A custom image can be uploaded as the avatar. In addition, users can also use their [Gravatar](https://en.wikipedia.org/wiki/Gravatar). Users can manage this under their [profile settings](../../../user-guide/account-settings/#set-an-avatar). These features can be disabled in the [avatar settings](../avatars).
> [!TIP]
>
> Hovering over a user's avatar or name, for example on the Members page or the Activity page, will display their information.
### Two-factor authentication (2FA)
@@ -219,9 +240,9 @@ Use the **self-registration** field to give the following controls over a new us
The user details Authentication section has fields **Assign random password**, **Password**, **Confirmation** and **Enforce password change**.
* If you are near the new user, you can enter a password and confirmation then tell the user what it is. They can then sign in. It is recommended that you also tick the enforce password change checkbox, so that the user is prompted to change their password after they sign in.
* You can phone the new user or send them an email, not using OpenProject, to give them the password. In this case it is more important to tick the enforce password change checkbox.
* Tick the Assign random password, and probably the enforce password change checkbox. When the details are saved OpenProject will send an email to the new user with their password.
- If you are near the new user, you can enter a password and confirmation then tell the user what it is. They can then sign in. It is recommended that you also tick the enforce password change checkbox, so that the user is prompted to change their password after they sign in.
- You can phone the new user or send them an email, not using OpenProject, to give them the password. In this case it is more important to tick the enforce password change checkbox.
- Tick the Assign random password, and probably the enforce password change checkbox. When the details are saved OpenProject will send an email to the new user with their password.
### Account activation by email
@@ -231,8 +252,8 @@ Leave all fields blank. When the details are saved OpenProject will send an emai
Two [settings](../settings/#user-deletion) allow users to be deleted from the system:
* **User accounts deletable by admins** - if ticked, a **Delete** button is shown on the user details page.
* **Users allowed to delete their accounts** - if ticked, a **Delete account** menu entry is shown in the **Account settings** page.
- **User accounts deletable by admins** - if ticked, a **Delete** button is shown on the user details page.
- **Users allowed to delete their accounts** - if ticked, a **Delete account** menu entry is shown in the **Account settings** page.
To delete another user's account open the [user list](#user-list). Click on the **user name** of the user which you want to delete. Click the **Delete** button at the top right.
@@ -240,7 +261,7 @@ To delete another user's account open the [user list](#user-list). Click on the
You will then be asked to confirm the deletion of the user permanently from the system. Checking the consent box will activate the **Delete permanently** button.
![delete user](delete-user-confirmation.png)
![Delete user in OpenProject administration](delete-user-confirmation.png)
> [!CAUTION]
> Deleting a user account is a permanent action and cannot be reversed. The previous activities from this user will still be displayed in the system but reassigned to **Deleted user**. This is also true for the Time and cost and the Budget modules. Spent time will be still be visible for **Deleted user** inside a Work package. Time and cost reports will contain the entries with reference to **Deleted user**. Labor budgets that have been setup for the user are displayed under **Deleted user**, too. If you would like to keep track of the user's name in connection with the mentioned activities, the spent time and the budget, you are able to keep the user's name in the historical data by simply [locking the user](#lock-and-unlock-users).
Binary file not shown.

Before

Width:  |  Height:  |  Size: 16 KiB

After

Width:  |  Height:  |  Size: 54 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 16 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 23 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 24 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 23 KiB

After

Width:  |  Height:  |  Size: 56 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 11 KiB

+4 -4
View File
@@ -12,7 +12,7 @@
"@blocknote/server-util": "^0.51.3",
"@hocuspocus/extension-logger": "^3.4.4",
"@hocuspocus/server": "^3.4.0",
"op-blocknote-extensions": "https://github.com/opf/op-blocknote-extensions/releases/download/v0.1.0/op-blocknote-extensions-0.1.0.tgz",
"op-blocknote-extensions": "https://github.com/opf/op-blocknote-extensions/releases/download/v0.1.1/op-blocknote-extensions-0.1.1.tgz",
"tsx": "^4.21.0"
},
"devDependencies": {
@@ -4245,9 +4245,9 @@
"license": "MIT"
},
"node_modules/op-blocknote-extensions": {
"version": "0.1.0",
"resolved": "https://github.com/opf/op-blocknote-extensions/releases/download/v0.1.0/op-blocknote-extensions-0.1.0.tgz",
"integrity": "sha512-JKwG2P5RXM0JDED0AzDeiVoxuamHtzqLO5fp88EoFig+YXlPsedJHc90zjTDqCFRilwTDamCq3jjzdFvl42kCA==",
"version": "0.1.1",
"resolved": "https://github.com/opf/op-blocknote-extensions/releases/download/v0.1.1/op-blocknote-extensions-0.1.1.tgz",
"integrity": "sha512-4VO5Qf51Z8WQGD24AYhNmGHGGwnfnB3q8KwL48hWTifZq/9IL5rKpwKB+QkxvVUCaT8iwFYwB6QPzGgLJKRVFA==",
"dependencies": {
"@primer/octicons-react": "^19.20.0",
"i18next": "^25.6.3",
@@ -26,7 +26,7 @@
"@blocknote/server-util": "^0.51.3",
"@hocuspocus/extension-logger": "^3.4.4",
"@hocuspocus/server": "^3.4.0",
"op-blocknote-extensions": "https://github.com/opf/op-blocknote-extensions/releases/download/v0.1.0/op-blocknote-extensions-0.1.0.tgz",
"op-blocknote-extensions": "https://github.com/opf/op-blocknote-extensions/releases/download/v0.1.1/op-blocknote-extensions-0.1.1.tgz",
"tsx": "^4.21.0"
},
"devDependencies": {
+4 -4
View File
@@ -106,7 +106,7 @@
"ng2-dragula": "^6.0.0",
"ngx-cookie-service": "^21.3.1",
"observable-array": "0.0.4",
"op-blocknote-extensions": "https://github.com/opf/op-blocknote-extensions/releases/download/v0.1.0/op-blocknote-extensions-0.1.0.tgz",
"op-blocknote-extensions": "https://github.com/opf/op-blocknote-extensions/releases/download/v0.1.1/op-blocknote-extensions-0.1.1.tgz",
"openapi-explorer": "^2.4.799",
"pako": "^2.0.3",
"qr-creator": "^1.0.0",
@@ -17516,9 +17516,9 @@
}
},
"node_modules/op-blocknote-extensions": {
"version": "0.1.0",
"resolved": "https://github.com/opf/op-blocknote-extensions/releases/download/v0.1.0/op-blocknote-extensions-0.1.0.tgz",
"integrity": "sha512-JKwG2P5RXM0JDED0AzDeiVoxuamHtzqLO5fp88EoFig+YXlPsedJHc90zjTDqCFRilwTDamCq3jjzdFvl42kCA==",
"version": "0.1.1",
"resolved": "https://github.com/opf/op-blocknote-extensions/releases/download/v0.1.1/op-blocknote-extensions-0.1.1.tgz",
"integrity": "sha512-4VO5Qf51Z8WQGD24AYhNmGHGGwnfnB3q8KwL48hWTifZq/9IL5rKpwKB+QkxvVUCaT8iwFYwB6QPzGgLJKRVFA==",
"dependencies": {
"@primer/octicons-react": "^19.20.0",
"i18next": "^25.6.3",
+1 -1
View File
@@ -153,7 +153,7 @@
"ng2-dragula": "^6.0.0",
"ngx-cookie-service": "^21.3.1",
"observable-array": "0.0.4",
"op-blocknote-extensions": "https://github.com/opf/op-blocknote-extensions/releases/download/v0.1.0/op-blocknote-extensions-0.1.0.tgz",
"op-blocknote-extensions": "https://github.com/opf/op-blocknote-extensions/releases/download/v0.1.1/op-blocknote-extensions-0.1.1.tgz",
"openapi-explorer": "^2.4.799",
"pako": "^2.0.3",
"qr-creator": "^1.0.0",
@@ -13,12 +13,12 @@
class="op-ian-item"
[class.op-ian-item_expanded]="records[0].expanded"
[class.op-ian-item_read]="records[0].readIAN === true"
[class.op-ian-item_selected]="(selectedWorkPackage$ | async) === idFromLink(records[0]._links.resource.href)"
[class.op-ian-item_selected]="notificationMatchesSelectedWorkPackage(records[0], selectedWorkPackage$ | async)"
[notification]="records[0]"
[aggregatedNotifications]="records"
attr.data-test-selector="op-ian-notification-item-{{records[0].id}}"
[attr.data-qa-ian-read]="records[0].readIAN === true || undefined"
[attr.data-qa-ian-selected]="(selectedWorkPackage$ | async) === idFromLink(records[0]._links.resource.href)"
[attr.data-qa-ian-selected]="notificationMatchesSelectedWorkPackage(records[0], selectedWorkPackage$ | async)"
/>
</cdk-virtual-scroll-viewport>
} @else {
@@ -153,7 +153,7 @@ export class InAppNotificationCenterComponent implements OnInit {
protected readonly idFromLink = idFromLink;
ngOnInit():void {
const facet = this.urlParams.get('facet') || 'unread';
const facet = this.urlParams.get('facet') ?? 'unread';
this.storeService.setFacet(facet as 'unread'|'all');
this.storeService.setFilters({
filter: this.urlParams.get('filter'),
@@ -172,4 +172,12 @@ export class InAppNotificationCenterComponent implements OnInit {
return this.text.no_notification_for_filter;
}
notificationMatchesSelectedWorkPackage(notification:INotification, selected:string|null):boolean {
const href = notification._links.resource?.href;
const workPackageId = href ? idFromLink(href) : null;
const workPackage = workPackageId ? this.apiV3.work_packages.cache.current(workPackageId) : null;
return selected === workPackageId || selected === workPackage?.displayId;
}
}
+8 -3
View File
@@ -82,9 +82,14 @@ class BlockNoteElement extends HTMLElement {
this.reactRoot = createRoot(this.editorMount);
this.renderCallback = (provider:HocuspocusProvider) => {
this.reactRoot?.render(
React.createElement(React.StrictMode, null, this.BlockNoteReactContainer(provider))
);
// Do NOT wrap in React.StrictMode. StrictMode's dev-mode double-mount causes
// BlockNoteView to destroy and recreate the ProseMirror view between the two mounts.
// y-prosemirror's `yUndoPlugin` destroys the Y.UndoManager on view-destroy (removing
// its `afterTransaction` handler from the Y.Doc), but the plugin's STATE retains the
// now-destroyed UndoManager reference. On the second mount the editor reuses the
// destroyed UndoManager, no `afterTransaction` handler is ever re-attached, no stack
// items are recorded, and Ctrl+Z becomes a no-op.
this.reactRoot?.render(this.BlockNoteReactContainer(provider));
};
LiveCollaborationManager.onReady(this.renderCallback);
@@ -42,6 +42,7 @@ import {
openProjectWorkPackageInlineSpec,
workPackageSlashMenu,
useOpBlockNoteExtensions,
PasteDeduplicateInstanceIdsExtension,
useHashWpMenu,
} from 'op-blocknote-extensions';
import { useCallback, useEffect, useMemo } from 'react';
@@ -118,13 +119,18 @@ export function OpBlockNoteEditor({
dictionary: localeDictionary,
...(attachmentsEnabled && { uploadFile }),
extensions: [
PasteDeduplicateInstanceIdsExtension,
ExternalLinkA11yExtension,
...(captureExternalLinks ? [ExternalLinkCaptureExtension] : []),
],
};
}, [hocuspocusProvider, doc, activeUser, localeDictionary, attachmentsEnabled, uploadFile, captureExternalLinks]);
const editor = useCreateBlockNote(editorParams, [activeUser]);
// Create the editor exactly once per mount. `useCreateBlockNote(options, deps)` uses `deps`
// as the sole `useMemo` key — `options` is intentionally NOT in deps. `[activeUser]` rebuilt
// the editor (wiping `Y.UndoManager` history) whenever a fresh `activeUser` reference
// reached this component, e.g. on Stimulus reconnect / Turbo morph.
const editor = useCreateBlockNote(editorParams, []);
useOpBlockNoteExtensions(editor);
type EditorType = typeof editor;
const theme = useOpTheme();
@@ -74,6 +74,17 @@ export default class extends Controller {
connect():void {
this.currentToken = this.tokenPayloadValue;
// If a provider for this document is already live, don't build a duplicate
// — adopt it. Stimulus can fire connect() a second time (HMR replay, Turbo
// morph, parent re-attach) without firing disconnect(); building a fresh
// Y.Doc + provider in that case would destroy the live one and wipe the
// editor's Y.UndoManager mid-session.
const existing = LiveCollaborationManager.getCurrentSessionFor(this.documentNameValue);
if (existing) {
this.ownedProvider = existing.provider;
return;
}
const ydoc:Doc = new Y.Doc();
const provider = new HocuspocusProvider({
url: this.hocuspocusUrlValue,
@@ -87,7 +98,7 @@ export default class extends Controller {
},
});
LiveCollaborationManager.initializeYjsProvider(provider, ydoc);
LiveCollaborationManager.initializeYjsProvider(provider, ydoc, this.documentNameValue);
this.ownedProvider = provider;
if (this.refreshUrlValue && this.tokenExpiresInSecondsValue) {
@@ -36,21 +36,47 @@ type Listener = (provider:HocuspocusProvider) => void;
class LiveCollaborationManagerClass {
yjsProviderInstance:HocuspocusProvider|null = null;
yjsDocInstance:Doc|null = null;
private currentDocumentName:string|null = null;
private listeners:Listener[] = [];
/**
* Initializes the YJS Provider
* Returns the active session for the given document, or null if none.
*
* Used by the init-yjs-provider Stimulus controller to detect that a
* provider for the same document is already live — letting it adopt the
* existing session instead of building a duplicate Y.Doc + provider pair.
* Stimulus can fire `connect()` a second time (HMR replay, Turbo morph)
* without firing `disconnect()`; without this check, the spurious re-init
* would tear down the live Y.Doc and wipe the editor's Y.UndoManager
* history mid-session.
*/
getCurrentSessionFor(documentName:string):{provider:HocuspocusProvider; doc:Doc} | null {
if (this.yjsProviderInstance && this.yjsDocInstance && this.currentDocumentName === documentName) {
return { provider: this.yjsProviderInstance, doc: this.yjsDocInstance };
}
return null;
}
/**
* Initializes the YJS Provider for the given document.
*
* Callers SHOULD first check {@link getCurrentSessionFor} and adopt any
* existing session rather than calling this with a fresh provider, since
* this method unconditionally tears down the previous provider/doc.
*
* @param provider The provider to use
* @param doc The Y.Doc instance to use
* @param documentName Logical identifier of the document being edited
* @returns void
*/
initializeYjsProvider(provider:HocuspocusProvider, doc:Doc) {
initializeYjsProvider(provider:HocuspocusProvider, doc:Doc, documentName:string) {
this.destroyYjsProvider();
this.destroyYjsDoc();
this.yjsProviderInstance = provider;
this.yjsDocInstance = doc;
this.currentDocumentName = documentName;
this.listeners.forEach((listener) => listener(this.yjsProviderInstance!));
}
@@ -82,6 +108,7 @@ class LiveCollaborationManagerClass {
private destroy():void {
this.destroyYjsProvider();
this.destroyYjsDoc();
this.currentDocumentName = null;
this.listeners = [];
}
+3 -12
View File
@@ -40,7 +40,6 @@ af:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Agterstand tipe
@@ -124,8 +123,6 @@ af:
label_burndown_chart: Burndown chart
label_is_done_status: Status %{status_name} beteken klaar
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ af:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Werk pakket is klaar, wanneer
burndown:
@@ -195,19 +190,18 @@ af:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Agterstand
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Agterstand
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Af
label_points_burn_up: Op
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Taak bord
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -215,9 +209,6 @@ af:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ ar:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: نوع الأعمال المتراكمة غير المنجزة
@@ -132,8 +131,6 @@ ar:
label_burndown_chart: Burndown chart
label_is_done_status: الحالة %{status_name} تعني أنها منجزة
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -198,8 +195,6 @@ ar:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: مجموعة العمل قد تمت، عندما
burndown:
@@ -211,19 +206,18 @@ ar:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: الأعمال المتراكمة غير المنجزة
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: الوارد
label_backlogs: الأعمال المتراكمة غير المنجزة
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: الأسفل
label_points_burn_up: الأعلى
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: لوحة المهمة
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -231,9 +225,6 @@ ar:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ az:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: ''
@@ -124,8 +123,6 @@ az:
label_burndown_chart: Burndown chart
label_is_done_status: "%{status_name}"
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ az:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Work package is done, when
burndown:
@@ -195,19 +190,18 @@ az:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Backlogs
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Down
label_points_burn_up: Up
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Task board
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -215,9 +209,6 @@ az:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ be:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Тып бэклогу
@@ -128,8 +127,6 @@ be:
label_burndown_chart: Burndown chart
label_is_done_status: Status %{status_name} means done
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -190,8 +187,6 @@ be:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Work package is done, when
burndown:
@@ -203,19 +198,18 @@ be:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Backlogs
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Down
label_points_burn_up: Up
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Task board
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -223,9 +217,6 @@ be:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ bg:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Backlog type
@@ -124,8 +123,6 @@ bg:
label_burndown_chart: Burndown chart
label_is_done_status: Статус %{status_name} означава готово
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ bg:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Работният пакет е готов, когато
burndown:
@@ -195,19 +190,18 @@ bg:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Backlogs
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Надолу
label_points_burn_up: Нагоре
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Task board
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -215,9 +209,6 @@ bg:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ ca:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Tipus de backlog
@@ -124,8 +123,6 @@ ca:
label_burndown_chart: Burndown chart
label_is_done_status: L'estat %{status_name} significa fet
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ ca:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Paquet de treball completat, quan
burndown:
@@ -195,19 +190,18 @@ ca:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Backlogs
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: A baix
label_points_burn_up: Amunt
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Tauler de tasques
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -215,9 +209,6 @@ ca:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
@@ -40,7 +40,6 @@ ckb-IR:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: جۆری Backlog
@@ -124,8 +123,6 @@ ckb-IR:
label_burndown_chart: Burndown chart
label_is_done_status: Status %{status_name} means done
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ ckb-IR:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Work package is done, when
burndown:
@@ -195,19 +190,18 @@ ckb-IR:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Backlogs
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Down
label_points_burn_up: Up
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Task board
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -215,9 +209,6 @@ ckb-IR:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ cs:
in_planning: V plánování
active: Aktivní
completed: Dokončen
work_packages: Pracovní balíčky
work_package:
backlog_bucket: Sekce backlogu
backlogs_work_package_type: Typ backlogu
@@ -128,8 +127,6 @@ cs:
label_burndown_chart: Burndown chart
label_is_done_status: Stav %{status_name} znamená hotovo
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Přesunout do sprintu
label_sprint: Sprint
@@ -190,8 +187,6 @@ cs:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Pracovní balíček je hotov, když
burndown:
@@ -203,19 +198,18 @@ cs:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Backlogy
label_backlog_and_sprints: Backlogy a sprinty
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Backlogy
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Dolů
label_points_burn_up: Nahoru
label_sprint_edit: Upravit sprint
label_sprint_new: Nový sprint
label_backlog_and_sprints: Backlogy a sprinty
label_task_board: Tabule úkolů
notice_successful_start: Sprint byl zahájen.
notice_successful_finish: Sprint byl dokončen.
@@ -223,9 +217,6 @@ cs:
notice_unsuccessful_start_with_reason: 'Sprint nebylo možné zahájit: %{reason}'
notice_unsuccessful_finish: Sprint nebylo možné dokončit.
notice_unsuccessful_finish_with_reason: 'Sprint nebylo možné dokončit: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Vytváření sprintů
permission_manage_sprint_items: Správa položek sprintu
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ da:
in_planning: Under planlægning
active: Aktiv
completed: Færdiggjort
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Backlog-type
@@ -124,8 +123,6 @@ da:
label_burndown_chart: Burndown-diagram
label_is_done_status: Status %{status_name} betyder færdig
label_sprint_board: Sprinttavle
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Flyt til sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ da:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Arbejdspakken er færdig, når
burndown:
@@ -195,19 +190,18 @@ da:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Backlogger
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Redigér backlog bucket
label_backlog_bucket_new: Ny backlog bucket
label_burndown_chart: Burndown-diagram
label_inbox: Indbakke
label_backlogs: Backlogger
label_burndown_chart: Burndown-diagram
label_sprint_board: Sprinttavle
label_points_burn_down: Ned
label_points_burn_up: Op
label_sprint_edit: Redigér sprint
label_sprint_new: Ny sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Opgaveoversigt
notice_successful_start: Sprinten blev sat i gang.
notice_successful_finish: Sprinten blev afsluttet.
@@ -215,9 +209,6 @@ da:
notice_unsuccessful_start_with_reason: 'Sprinten kunne ikke startes: %{reason}'
notice_unsuccessful_finish: Sprinten kunne ikke afsluttes.
notice_unsuccessful_finish_with_reason: 'Sprinten kunne ikke afsluttes: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Opret sprints
permission_manage_sprint_items: Håndtér sprint-emner
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ de:
in_planning: In Planung
active: Aktiv
completed: Abgeschlossen
work_packages: Arbeitspakete
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Backlog Typ
@@ -124,8 +123,6 @@ de:
label_burndown_chart: Burndown-Diagramm
label_is_done_status: Status %{status_name} bedeutet abgeschlossen
label_sprint_board: Sprint-Board
move_to_bucket_dialog_component:
title: In Backlog Bucket verschieben
move_to_sprint_dialog_component:
title: Zum Sprint verschieben
label_sprint: Sprint
@@ -182,8 +179,6 @@ de:
copy_url_to_clipboard: URL in die Zwischenablage kopieren
copy_work_package_id: Arbeitspaket-ID kopieren
move_menu: Verschieben
move_to_backlog_bucket: In Backlog Bucket verschieben
move_to_inbox: In Posteingang verschieben
move_to_sprint: Zum Sprint verschieben
work_package_is_closed: Arbeitspaket ist abgeschlossen, wenn
burndown:
@@ -195,19 +190,18 @@ de:
upsell:
sprint_sharing:
description: Teilen Sie Sprints über Projekte hinweg, um Teams aufeinander abzustimmen und die Arbeit in skalierten agilen Setups (SAFe) zu koordinieren.
label_all_sprints: Alle Sprints
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Backlog und Sprints
label_backlog_bucket_edit: Backlog Bucket bearbeiten
label_backlog_bucket_new: Neuer Backlog Bucket
label_burndown_chart: Burndown-Diagramm
label_inbox: Posteingang
label_backlogs: Backlogs
label_burndown_chart: Burndown-Diagramm
label_sprint_board: Sprint-Board
label_points_burn_down: Runter
label_points_burn_up: Hoch
label_sprint_edit: Sprint bearbeiten
label_sprint_new: Neuer Sprint
label_backlog_and_sprints: Backlog und Sprints
label_task_board: Taskboard
notice_successful_start: Der Sprint wurde gestartet.
notice_successful_finish: Der Sprint wurde abgeschlossen.
@@ -215,9 +209,6 @@ de:
notice_unsuccessful_start_with_reason: 'Der Sprint konnte nicht gestartet werden: %{reason}'
notice_unsuccessful_finish: Der Sprint konnte nicht abgeschlossen werden.
notice_unsuccessful_finish_with_reason: 'Der Sprint konnte nicht abgeschlossen werden: %{reason}'
notice_work_package_invisible_after_move: 'Das Arbeitspaket wurde auf %{backlog} verschoben, ist aber nicht sichtbar, weil sein Typ oder Status gemäß Konfiguration im Backlog ausgeblendet wird.
'
permission_create_sprints: Sprints erstellen
permission_manage_sprint_items: Sprint-Elemente verwalten
permission_select_backlog_types_and_statuses: Typen und Status für Backlogs wählen
+3 -12
View File
@@ -40,7 +40,6 @@ el:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Τύπος backlog
@@ -124,8 +123,6 @@ el:
label_burndown_chart: Burndown chart
label_is_done_status: Η κατάσταση %{status_name} σημαίνει ολοκληρωμένη
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ el:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Το πακέτο εργασίας ολοκληρώνεται, όταν
burndown:
@@ -195,19 +190,18 @@ el:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Backlogs
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Κάτω
label_points_burn_up: Πάνω
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Πίνακας εργασιών
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -215,9 +209,6 @@ el:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ eo:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Backlog type
@@ -124,8 +123,6 @@ eo:
label_burndown_chart: Burndown chart
label_is_done_status: Status %{status_name} means done
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ eo:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Work package is done, when
burndown:
@@ -195,19 +190,18 @@ eo:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Backlogs
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Malsupren
label_points_burn_up: Supren
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Task board
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -215,9 +209,6 @@ eo:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ es:
in_planning: En planificación
active: Activo
completed: Completado
work_packages: Paquetes de trabajo
work_package:
backlog_bucket: Buckets de backlog
backlogs_work_package_type: Tipo de Backlog
@@ -124,8 +123,6 @@ es:
label_burndown_chart: Diagrama Burndown
label_is_done_status: El estado %{status_name} significa completado
label_sprint_board: Tablero Sprint
move_to_bucket_dialog_component:
title: Mover al bucket de backlog
move_to_sprint_dialog_component:
title: Mover al sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ es:
copy_url_to_clipboard: Copiar URL al portapapeles
copy_work_package_id: Copiar el ID del paquete de trabajo
move_menu: Mover
move_to_backlog_bucket: Mover al bucket de backlog
move_to_inbox: Mover a la bandeja de entrada
move_to_sprint: Mover al sprint
work_package_is_closed: El paquete de trabajo esta terminado, cuando
burndown:
@@ -195,19 +190,18 @@ es:
upsell:
sprint_sharing:
description: Comparte sprints entre proyectos para coordinar a los equipos y organizar el trabajo en entornos ágiles a gran escala (SAFe).
label_all_sprints: Todos los sprints
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Backlog y sprints
label_backlog_bucket_edit: Editar bucket de backlog
label_backlog_bucket_new: Nuevo bucket de backlog
label_burndown_chart: Diagrama Burndown
label_inbox: Bandeja de entrada
label_backlogs: Backlogs
label_burndown_chart: Diagrama Burndown
label_sprint_board: Tablero Sprint
label_points_burn_down: Abajo
label_points_burn_up: Arriba
label_sprint_edit: Editar sprint
label_sprint_new: Nuevo sprint
label_backlog_and_sprints: Backlog y sprints
label_task_board: Tablero de tareas
notice_successful_start: Se inició el sprint.
notice_successful_finish: El sprint se completó.
@@ -215,9 +209,6 @@ es:
notice_unsuccessful_start_with_reason: 'El sprint no pudo iniciarse: %{reason}'
notice_unsuccessful_finish: El sprint no pudo completarse.
notice_unsuccessful_finish_with_reason: 'El sprint no pudo completarse: %{reason}'
notice_work_package_invisible_after_move: 'El paquete de trabajo se ha trasladado a %{backlog}, pero no se ve porque su tipo o estado están excluidos de la lista de tareas pendientes.
'
permission_create_sprints: Crear sprints
permission_manage_sprint_items: Gestionar elementos de sprint
permission_select_backlog_types_and_statuses: Selecciona los tipos y estados del backlog
+3 -12
View File
@@ -40,7 +40,6 @@ et:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Backlog type
@@ -124,8 +123,6 @@ et:
label_burndown_chart: Burndown chart
label_is_done_status: Status %{status_name} means done
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ et:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Work package is done, when
burndown:
@@ -195,19 +190,18 @@ et:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Backlogs
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Alla
label_points_burn_up: Üles
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Task board
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -215,9 +209,6 @@ et:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ eu:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Backlog type
@@ -124,8 +123,6 @@ eu:
label_burndown_chart: Burndown chart
label_is_done_status: Status %{status_name} means done
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ eu:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Work package is done, when
burndown:
@@ -195,19 +190,18 @@ eu:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Backlogs
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Behera
label_points_burn_up: Gora
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Task board
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -215,9 +209,6 @@ eu:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ fa:
in_planning: در حال برنامه ریزی
active: فعال
completed: تکمیل شده
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Backlog type
@@ -124,8 +123,6 @@ fa:
label_burndown_chart: Burndown chart
label_is_done_status: Status %{status_name} means done
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ fa:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Work package is done, when
burndown:
@@ -195,19 +190,18 @@ fa:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: پس‌افت
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: پس‌افت
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: پایین
label_points_burn_up: بالا
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: تابلوی وظیفه
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -215,9 +209,6 @@ fa:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ fi:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Työjonon tyyppi
@@ -124,8 +123,6 @@ fi:
label_burndown_chart: Burndown chart
label_is_done_status: Tila %{status_name} tarkoittaa valmista
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ fi:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Tehtävä on valmis, kun
burndown:
@@ -195,19 +190,18 @@ fi:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Työjonot
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Työjonot
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Alas
label_points_burn_up: Ylös
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Tehtävätaulu
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -215,9 +209,6 @@ fi:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
@@ -40,7 +40,6 @@ fil:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Backlog type
@@ -124,8 +123,6 @@ fil:
label_burndown_chart: Burndown chart
label_is_done_status: Status %{status_name} means done
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ fil:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Work package is done, when
burndown:
@@ -195,19 +190,18 @@ fil:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Backlogs
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Down
label_points_burn_up: Up
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Task board
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -215,9 +209,6 @@ fil:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ fr:
in_planning: En cours de planification
active: Actif
completed: Terminé
work_packages: Lots de travaux
work_package:
backlog_bucket: Bucket de backlog
backlogs_work_package_type: Type de backlog
@@ -124,8 +123,6 @@ fr:
label_burndown_chart: Graphique burndown
label_is_done_status: Le statut %{status_name} signifie fait
label_sprint_board: Tableau de sprint
move_to_bucket_dialog_component:
title: Déplacer vers un bucket de backlog
move_to_sprint_dialog_component:
title: Passer au sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ fr:
copy_url_to_clipboard: Copier l'URL dans le presse-papier
copy_work_package_id: Copier l'ID du lot de travaux
move_menu: Déplacer
move_to_backlog_bucket: Déplacer vers un bucket de backlog
move_to_inbox: Déplacer vers la boîte de réception
move_to_sprint: Déplacer dans le sprint
work_package_is_closed: Le lot de travaux est fait lorsque
burndown:
@@ -195,19 +190,18 @@ fr:
upsell:
sprint_sharing:
description: Partager les sprints entre les projets afin d'aligner les équipes et de coordonner le travail dans des configurations agiles à grande échelle (SAFe).
label_all_sprints: Tous les sprints
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Backlog et sprints
label_backlog_bucket_edit: Modifier le bucket de backlog
label_backlog_bucket_new: Nouveau bucket de backlog
label_burndown_chart: Graphique burndown
label_inbox: Boîte de réception
label_backlogs: Backlogs
label_burndown_chart: Graphique burndown
label_sprint_board: Tableau de sprint
label_points_burn_down: Vers le bas
label_points_burn_up: Vers le haut
label_sprint_edit: Modifier le sprint
label_sprint_new: Nouveau sprint
label_backlog_and_sprints: Backlog et sprints
label_task_board: Tableau des tâches
notice_successful_start: Le sprint a commencé.
notice_successful_finish: Le sprint est terminé.
@@ -215,9 +209,6 @@ fr:
notice_unsuccessful_start_with_reason: 'Le sprint n''a pas pu être démarré : %{reason}'
notice_unsuccessful_finish: Le sprint n'a pas pu être terminé.
notice_unsuccessful_finish_with_reason: 'Le sprint n''a pas pu être achevé : %{reason}'
notice_work_package_invisible_after_move: 'Le lot de travaux a été déplacé vers %{backlog} mais n''est pas visible car son type ou son statut est exclu de l''arriéré.
'
permission_create_sprints: Créer des sprints
permission_manage_sprint_items: Gérer les éléments du sprint
permission_select_backlog_types_and_statuses: Sélectionner les types et les statuts du backlog
+3 -12
View File
@@ -40,7 +40,6 @@ he:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Backlog type
@@ -128,8 +127,6 @@ he:
label_burndown_chart: Burndown chart
label_is_done_status: Status %{status_name} means done
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -190,8 +187,6 @@ he:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Work package is done, when
burndown:
@@ -203,19 +198,18 @@ he:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Backlogs
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Down
label_points_burn_up: Up
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Task board
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -223,9 +217,6 @@ he:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ hi:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: बैकलॉग प्रकार
@@ -124,8 +123,6 @@ hi:
label_burndown_chart: Burndown chart
label_is_done_status: स्थिति %{status_name} का अर्थ हो गया
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ hi:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: काम का पैकेज हो गया, जब
burndown:
@@ -195,19 +190,18 @@ hi:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Backlogs
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Down
label_points_burn_up: Up
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Task board
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -215,9 +209,6 @@ hi:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ hr:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Backlog tip
@@ -126,8 +125,6 @@ hr:
label_burndown_chart: Burndown chart
label_is_done_status: Status %{status_name} je završen
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -186,8 +183,6 @@ hr:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Radni zadatak je urađen, kada
burndown:
@@ -199,19 +194,18 @@ hr:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Backlogs
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Dolje
label_points_burn_up: Gore
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Upravitelj zadatcima
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -219,9 +213,6 @@ hr:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ hu:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Backlog típus
@@ -124,8 +123,6 @@ hu:
label_burndown_chart: Burndown chart
label_is_done_status: Státusz %{status_name} kész állapotot jelöl
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ hu:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: A munkacsomag készen áll, ekkor
burndown:
@@ -195,19 +190,18 @@ hu:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Backlogs
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Le
label_points_burn_up: Fel
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Task board
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -215,9 +209,6 @@ hu:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ hy:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Backlog type
@@ -124,8 +123,6 @@ hy:
label_burndown_chart: Burndown chart
label_is_done_status: Status %{status_name} means done
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ hy:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Work package is done, when
burndown:
@@ -195,19 +190,18 @@ hy:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Backlogs
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Down
label_points_burn_up: Up
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Task board
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -215,9 +209,6 @@ hy:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ id:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Jenis jaminan tersimpan
@@ -122,8 +121,6 @@ id:
label_burndown_chart: Burndown chart
label_is_done_status: Status %{status_name} berarti selesai
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -178,8 +175,6 @@ id:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Paket kerja selesai, ketika
burndown:
@@ -191,19 +186,18 @@ id:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Backlogs
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Menurun
label_points_burn_up: Naik
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Papan tugas
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -211,9 +205,6 @@ id:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ it:
in_planning: In pianificazione
active: Attivo
completed: Completato
work_packages: Macro-attività
work_package:
backlog_bucket: Bucket del backlog
backlogs_work_package_type: Tipo di backlog
@@ -124,8 +123,6 @@ it:
label_burndown_chart: Grafico Burndown
label_is_done_status: Lo stato %{status_name} vuol dire completato
label_sprint_board: Bacheca sprint
move_to_bucket_dialog_component:
title: Sposta nel bucket del backlog
move_to_sprint_dialog_component:
title: Sposta nello sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ it:
copy_url_to_clipboard: Copia URL negli appunti
copy_work_package_id: Copia ID macro-attività
move_menu: Sposta
move_to_backlog_bucket: Sposta nel bucket del backlog
move_to_inbox: Sposta in posta in arrivo
move_to_sprint: Sposta nello sprint
work_package_is_closed: Il pacchetto di lavoro è fatto, quando
burndown:
@@ -195,19 +190,18 @@ it:
upsell:
sprint_sharing:
description: Condividi gli sprint tra progetti per allineare i team e coordinare il lavoro in contesti Agile scalati (SAFe).
label_all_sprints: Tutti gli sprint
label_backlog: Backlog
label_backlogs: Backlog
label_backlog_and_sprints: Backlog e sprint
label_backlog_bucket_edit: Modifica il bucket del backlog
label_backlog_bucket_new: Nuovo bucket del backlog
label_burndown_chart: Grafico Burndown
label_inbox: Posta in arrivo
label_backlogs: Backlog
label_burndown_chart: Grafico Burndown
label_sprint_board: Bacheca sprint
label_points_burn_down: Verso il basso
label_points_burn_up: Verso l'alto
label_sprint_edit: Modifica sprint
label_sprint_new: Nuovo sprint
label_backlog_and_sprints: Backlog e sprint
label_task_board: Pannello delle attività
notice_successful_start: Lo sprint è stato avviato.
notice_successful_finish: Lo sprint è stato completato.
@@ -215,9 +209,6 @@ it:
notice_unsuccessful_start_with_reason: 'Impossibile avviare lo sprint: %{reason}'
notice_unsuccessful_finish: Impossibile completare lo sprint.
notice_unsuccessful_finish_with_reason: 'Impossibile completare lo sprint: %{reason}'
notice_work_package_invisible_after_move: 'La macro-attività è stata spostata in %{backlog}, ma non è visibile perché il suo tipo o stato è escluso dal backlog.
'
permission_create_sprints: Crea gli sprint
permission_manage_sprint_items: Gestisci gli elementi dello sprint
permission_select_backlog_types_and_statuses: Seleziona tipi e stati del backlog
+3 -12
View File
@@ -40,7 +40,6 @@ ja:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: バックログの種類
@@ -122,8 +121,6 @@ ja:
label_burndown_chart: Burndown chart
label_is_done_status: ステータス%{status_name}は完了として扱う
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -178,8 +175,6 @@ ja:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: ワークパッケージが終了するには
burndown:
@@ -191,19 +186,18 @@ ja:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: バックログ
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: バックログ
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: ダウン
label_points_burn_up: アップ
label_sprint_edit: Edit sprint
label_sprint_new: 新しいスプリント
label_backlog_and_sprints: Backlog and sprints
label_task_board: かんばん
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -211,9 +205,6 @@ ja:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ ka:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: ჩამორჩენის ტიპი
@@ -124,8 +123,6 @@ ka:
label_burndown_chart: Burndown chart
label_is_done_status: Status %{status_name} means done
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ ka:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Work package is done, when
burndown:
@@ -195,19 +190,18 @@ ka:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: შეუსრულებელი ამოცანები
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: შეუსრულებელი ამოცანები
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: ქვემოთ
label_points_burn_up: ზემოთ
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: ამოცანების დაფა
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -215,9 +209,6 @@ ka:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ kk:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Backlog type
@@ -124,8 +123,6 @@ kk:
label_burndown_chart: Burndown chart
label_is_done_status: Status %{status_name} means done
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ kk:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Work package is done, when
burndown:
@@ -195,19 +190,18 @@ kk:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Backlogs
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Down
label_points_burn_up: Up
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Task board
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -215,9 +209,6 @@ kk:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ ko:
in_planning: 계획 중
active: 활성
completed: 완료됨
work_packages: 작업 패키지
work_package:
backlog_bucket: 백로그 버킷
backlogs_work_package_type: 백로그 유형
@@ -122,8 +121,6 @@ ko:
label_burndown_chart: 번다운 차트
label_is_done_status: "%{status_name} 상태는 완료를 의미합니다."
label_sprint_board: 스프린트 보드
move_to_bucket_dialog_component:
title: 백로그 버킷으로 이동
move_to_sprint_dialog_component:
title: 스프린트로 이동
label_sprint: 스프린트
@@ -178,8 +175,6 @@ ko:
copy_url_to_clipboard: 클립보드에 URL 복사
copy_work_package_id: 작업 패키지 ID 복사
move_menu: 이동
move_to_backlog_bucket: 백로그 버킷으로 이동
move_to_inbox: 받은 편지함으로 이동
move_to_sprint: 스프린트로 이동
work_package_is_closed: 다음 경우에 작업 패키지가 완료됩니다.
burndown:
@@ -191,19 +186,18 @@ ko:
upsell:
sprint_sharing:
description: 프로젝트 간에 스프린트를 공유하여 팀을 조율하고 확장된 애자일 설정(SAFe)에서 작업을 조정합니다.
label_all_sprints: 모든 스프린트
label_backlog: 백로그
label_backlogs: 백로그
label_backlog_and_sprints: 백로그 및 스프린트
label_backlog_bucket_edit: 백로그 버킷 편집
label_backlog_bucket_new: 새로운 백로그 버킷
label_burndown_chart: 번다운 차트
label_inbox: 받은 편지함
label_backlogs: 백로그
label_burndown_chart: 번다운 차트
label_sprint_board: 스프린트 보드
label_points_burn_down: 아래
label_points_burn_up:
label_sprint_edit: 스프린트 편집
label_sprint_new: 새로운 스프린트
label_backlog_and_sprints: 백로그 및 스프린트
label_task_board: 작업 보드
notice_successful_start: 스프린트가 시작되었습니다.
notice_successful_finish: 스프린트가 완료되었습니다.
@@ -211,9 +205,6 @@ ko:
notice_unsuccessful_start_with_reason: '스프린트를 시작할 수 없습니다: %{reason}'
notice_unsuccessful_finish: 스프린트를 완료할 수 없습니다.
notice_unsuccessful_finish_with_reason: '스프린트를 완료할 수 없습니다: %{reason}'
notice_work_package_invisible_after_move: '작업 패키지가 %{backlog}(으)로 이동되었지만 해당 유형이나 상태가 백로그에서 제외되었으므로 표시되지 않습니다.
'
permission_create_sprints: 스프린트 만들기
permission_manage_sprint_items: 스프린트 항목 관리
permission_select_backlog_types_and_statuses: 백로그 유형 및 상태 선택
+3 -12
View File
@@ -40,7 +40,6 @@ lt:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Darbų sąrašo tipas
@@ -128,8 +127,6 @@ lt:
label_burndown_chart: Burndown chart
label_is_done_status: Būsena %{status_name} reiškia atlikta
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -190,8 +187,6 @@ lt:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Darbo paketas baigtas, kai
burndown:
@@ -203,19 +198,18 @@ lt:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Darbų sąrašai
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Darbų sąrašai
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Žemyn
label_points_burn_up: Aukštyn
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Užduočių lenta
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -223,9 +217,6 @@ lt:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ lv:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Produkta darbu krātuves tips
@@ -126,8 +125,6 @@ lv:
label_burndown_chart: Burndown chart
label_is_done_status: Statuss %{status_name} nozīmē, ka darbis ir pabeigts
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -186,8 +183,6 @@ lv:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: 'Darba pieteikums ir bageits, kad '
burndown:
@@ -199,19 +194,18 @@ lv:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Darbu krātuve
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Darbu krātuve
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Lejup
label_points_burn_up: Augšup
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Pieteikumu tāfele
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -219,9 +213,6 @@ lv:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ mn:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Backlog type
@@ -124,8 +123,6 @@ mn:
label_burndown_chart: Burndown chart
label_is_done_status: Төлөв %{status_name} дууссан гэсэн үг
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ mn:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Work package is done, when
burndown:
@@ -195,19 +190,18 @@ mn:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Backlogs
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Down
label_points_burn_up: Up
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Task board
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -215,9 +209,6 @@ mn:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ ms:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Jenis tunggakan kerja
@@ -122,8 +121,6 @@ ms:
label_burndown_chart: Burndown chart
label_is_done_status: Status %{status_name} bermaksud selesai
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -178,8 +175,6 @@ ms:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Pakej kerja selesai apabila
burndown:
@@ -191,19 +186,18 @@ ms:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Tunggakan
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Tunggakan
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Bawah
label_points_burn_up: Atas
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Papan tugasan
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -211,9 +205,6 @@ ms:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ ne:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Backlog type
@@ -124,8 +123,6 @@ ne:
label_burndown_chart: Burndown chart
label_is_done_status: Status %{status_name} means done
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ ne:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Work package is done, when
burndown:
@@ -195,19 +190,18 @@ ne:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Backlogs
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Down
label_points_burn_up: Up
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Task board
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -215,9 +209,6 @@ ne:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ nl:
in_planning: Wordt gepland
active: Gestart
completed: Voltooid
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Backlog type
@@ -124,8 +123,6 @@ nl:
label_burndown_chart: Burndown chart
label_is_done_status: Status van %{status_name} betekent gedaan
label_sprint_board: Sprint bord
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Verplaats naar sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ nl:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Het werkpakket is klaar wanneer
burndown:
@@ -195,19 +190,18 @@ nl:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Postvak in
label_backlogs: Backlogs
label_burndown_chart: Burndown chart
label_sprint_board: Sprint bord
label_points_burn_down: Omlaag
label_points_burn_up: Omhoog
label_sprint_edit: Sprint bewerken
label_sprint_new: Nieuwe sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Taakbord
notice_successful_start: De sprint is gestart.
notice_successful_finish: De sprint is voltooid.
@@ -215,9 +209,6 @@ nl:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Forsinkelser type
@@ -124,8 +123,6 @@
label_burndown_chart: Burndown chart
label_is_done_status: Status %{status_name} betyr fullført
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Arbeidspakke er ferdig, når
burndown:
@@ -195,19 +190,18 @@
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Forsinkelser
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Forsinkelser
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Ned
label_points_burn_up: Opp
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Oppgavetavle
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -215,9 +209,6 @@
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ pl:
in_planning: W planowaniu
active: Aktywne
completed: Ukończone
work_packages: Pakiety robocze
work_package:
backlog_bucket: Kategoria backlogu
backlogs_work_package_type: Typ backlogu
@@ -128,8 +127,6 @@ pl:
label_burndown_chart: Wykres spalania (burndown)
label_is_done_status: Status %{status_name} oznacza zrobiony
label_sprint_board: Tablica sprintu
move_to_bucket_dialog_component:
title: Przenieś do kategorii backlogu
move_to_sprint_dialog_component:
title: Przenieś do sprintu
label_sprint: Sprint
@@ -190,8 +187,6 @@ pl:
copy_url_to_clipboard: Skopiuj adres URL do schowka
copy_work_package_id: Skopiuj identyfikator pakietu roboczego
move_menu: Przenieś
move_to_backlog_bucket: Przenieś do kategorii backlogu
move_to_inbox: Przenieś do skrzynki odbiorczej
move_to_sprint: Przenieś do sprintu
work_package_is_closed: Zestaw Zadań będzie gotowy, kiedy
burndown:
@@ -203,19 +198,18 @@ pl:
upsell:
sprint_sharing:
description: Udostępnianie sprintów między projektami w celu dostosowania zespołów i koordynowania pracy w skalowanych konfiguracjach zwinnych (SAFe).
label_all_sprints: Wszystkie sprinty
label_backlog: Backlog
label_backlogs: Backlogi
label_backlog_and_sprints: Backlog i sprinty
label_backlog_bucket_edit: Edytuj kategorię backlogu
label_backlog_bucket_new: Nowa kategoria backlogu
label_burndown_chart: Wykres spalania (burndown)
label_inbox: Skrzynka odbiorcza
label_backlogs: Backlogi
label_burndown_chart: Wykres spalania (burndown)
label_sprint_board: Tablica sprintu
label_points_burn_down: W dół
label_points_burn_up: W górę
label_sprint_edit: Edytuj sprint
label_sprint_new: Nowy sprint
label_backlog_and_sprints: Backlog i sprinty
label_task_board: Panel zadań
notice_successful_start: Sprint został rozpoczęty.
notice_successful_finish: Sprint został ukończony.
@@ -223,9 +217,6 @@ pl:
notice_unsuccessful_start_with_reason: 'Nie można rozpocząć sprintu: %{reason}'
notice_unsuccessful_finish: Nie można ukończyć sprintu.
notice_unsuccessful_finish_with_reason: 'Nie można ukończyć sprintu: %{reason}'
notice_work_package_invisible_after_move: 'Pakiet roboczy został przeniesiony do %{backlog}, ale nie jest widoczny, ponieważ jego typ lub status są wykluczone z backlogu.
'
permission_create_sprints: Utwórz sprinty
permission_manage_sprint_items: Zarządzaj elementami sprintu
permission_select_backlog_types_and_statuses: Wybierz typy i statusy backlogu
@@ -40,7 +40,6 @@ pt-BR:
in_planning: Em planejamento
active: Ativa
completed: Concluída
work_packages: Pacotes de trabalho
work_package:
backlog_bucket: Grupo de backlog
backlogs_work_package_type: Tipo de backlog
@@ -124,8 +123,6 @@ pt-BR:
label_burndown_chart: Gráfico de burndown
label_is_done_status: Situação %{status_name} significa pronto
label_sprint_board: Quadro de sprints
move_to_bucket_dialog_component:
title: Mover para grupo de backlog
move_to_sprint_dialog_component:
title: Mover para sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ pt-BR:
copy_url_to_clipboard: Copiar URL para a área de transferência
copy_work_package_id: Copiar ID do pacotes de trabalho
move_menu: Mover
move_to_backlog_bucket: Mover para grupo de backlog
move_to_inbox: Mover para caixa de entrada
move_to_sprint: Mover para sprint
work_package_is_closed: Pacote de trabalho está pronto, quando
burndown:
@@ -195,19 +190,18 @@ pt-BR:
upsell:
sprint_sharing:
description: Compartilhe sprints entre projetos para alinhar equipes e coordenar o trabalho em configurações ágeis em escala (SAFe).
label_all_sprints: Todos os sprints
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Backlog e sprints
label_backlog_bucket_edit: Editar grupo de backlog
label_backlog_bucket_new: Novo grupo de backlog
label_burndown_chart: Gráfico de burndown
label_inbox: Caixa de entrada
label_backlogs: Backlogs
label_burndown_chart: Gráfico de burndown
label_sprint_board: Quadro de sprints
label_points_burn_down: Abaixo
label_points_burn_up: Acima
label_sprint_edit: Editar sprint
label_sprint_new: Nova sprint
label_backlog_and_sprints: Backlog e sprints
label_task_board: Quadro de tarefas
notice_successful_start: A sprint foi iniciada.
notice_successful_finish: A sprint foi concluída.
@@ -215,9 +209,6 @@ pt-BR:
notice_unsuccessful_start_with_reason: 'Não foi possível iniciar a sprint: %{reason}'
notice_unsuccessful_finish: Não foi possível concluir a sprint.
notice_unsuccessful_finish_with_reason: 'Não foi possível concluir a sprint: %{reason}'
notice_work_package_invisible_after_move: 'O pacote de trabalho foi movido para %{backlog}, mas não está visível porque seu tipo ou estado está excluído do backlog.
'
permission_create_sprints: Criar sprints
permission_manage_sprint_items: Gerenciar itens da sprint
permission_select_backlog_types_and_statuses: Selecionar tipos e estados do backlog
@@ -40,7 +40,6 @@ pt-PT:
in_planning: Em planeamento
active: Ativo
completed: Concluído
work_packages: Pacotes de trabalho
work_package:
backlog_bucket: Grupo de backlog
backlogs_work_package_type: Tipo de backlog
@@ -124,8 +123,6 @@ pt-PT:
label_burndown_chart: Gráfico de burndown
label_is_done_status: O estado %{status_name} significa terminado
label_sprint_board: Quadro de sprint
move_to_bucket_dialog_component:
title: Mover para o grupo de backlog
move_to_sprint_dialog_component:
title: Mover para sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ pt-PT:
copy_url_to_clipboard: Copiar URL para a área de transferência
copy_work_package_id: Copiar ID do pacote de trabalho
move_menu: Mover
move_to_backlog_bucket: Mover para o grupo de backlog
move_to_inbox: Mover para a caixa de entrada
move_to_sprint: Mover para sprint
work_package_is_closed: Pacote de trabalho está feito quando
burndown:
@@ -195,19 +190,18 @@ pt-PT:
upsell:
sprint_sharing:
description: Partilhe sprints entre projetos para alinhar as equipas e coordenar o trabalho em estruturas Agile escaláveis (SAFe).
label_all_sprints: Todos os sprints
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Backlog e sprints
label_backlog_bucket_edit: Editar grupo de backlog
label_backlog_bucket_new: Novo grupo de backlog
label_burndown_chart: Gráfico de burndown
label_inbox: Caixa de entrada
label_backlogs: Backlogs
label_burndown_chart: Gráfico de burndown
label_sprint_board: Quadro de sprint
label_points_burn_down: Abaixo
label_points_burn_up: Acima
label_sprint_edit: Editar sprint
label_sprint_new: Novo sprint
label_backlog_and_sprints: Backlog e sprints
label_task_board: Quadro de tarefas
notice_successful_start: O sprint foi iniciado.
notice_successful_finish: O sprint foi concluído.
@@ -215,9 +209,6 @@ pt-PT:
notice_unsuccessful_start_with_reason: 'Não foi possível iniciar o sprint: %{reason}'
notice_unsuccessful_finish: Não foi possível concluir o sprint.
notice_unsuccessful_finish_with_reason: 'Não foi possível concluir o sprint: %{reason}'
notice_work_package_invisible_after_move: 'O pacote de trabalho foi movido para %{backlog}, mas não é visível porque o seu tipo ou estado está excluído do backlog.
'
permission_create_sprints: Criar sprints
permission_manage_sprint_items: Gerir elementos de sprint
permission_select_backlog_types_and_statuses: Selecionar tipos e estados de backlog
+4 -13
View File
@@ -40,10 +40,9 @@ ro:
in_planning: În planificare
active: Activ
completed: Finalizat
work_packages: Pachete de lucru
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Tip restanță
backlogs_work_package_type: Tipul de restante
position: Poziție
sprint: Sprint
story_points: Puncte
@@ -126,8 +125,6 @@ ro:
label_burndown_chart: Burndown chart
label_is_done_status: Starea %{status_name} înseamnă terminat
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -186,8 +183,6 @@ ro:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Pachetul de lucru este finalizat, atunci când
burndown:
@@ -199,19 +194,18 @@ ro:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Restanțe
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Restanțe
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Jos
label_points_burn_up: Sus
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Tablă de sarcini
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -219,9 +213,6 @@ ro:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ ru:
in_planning: В планировании
active: Активен
completed: Завершён
work_packages: Пакеты работ
work_package:
backlog_bucket: Раздел бэклога
backlogs_work_package_type: Тип невыполненной работы
@@ -128,8 +127,6 @@ ru:
label_burndown_chart: Диаграмма выгорания
label_is_done_status: Статус %{status_name} означает завершение,
label_sprint_board: Доска для спринта
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Переместить в спринт
label_sprint: Спринт
@@ -190,8 +187,6 @@ ru:
copy_url_to_clipboard: Скопировать URL в буфер обмена
copy_work_package_id: Скопировать ID пакета работ
move_menu: Переместить
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Переместить в спринт
work_package_is_closed: Пакет работ завершен, когда
burndown:
@@ -203,19 +198,18 @@ ru:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Бэклог
label_backlogs: Бэклоги
label_backlog_and_sprints: Бэклог и спринты
label_backlog_bucket_edit: Редактировать раздел бэклога
label_backlog_bucket_new: Новый раздел бэклога
label_burndown_chart: Диаграмма выгорания
label_inbox: Входящие
label_backlogs: Бэклоги
label_burndown_chart: Диаграмма выгорания
label_sprint_board: Доска для спринта
label_points_burn_down: Вниз
label_points_burn_up: Вверх
label_sprint_edit: Редактировать спринт
label_sprint_new: Новый спринт
label_backlog_and_sprints: Бэклог и спринты
label_task_board: Панель задач
notice_successful_start: Спринт запущен.
notice_successful_finish: Спринт завершен.
@@ -223,9 +217,6 @@ ru:
notice_unsuccessful_start_with_reason: 'Спринт не может быть запущен: %{reason}'
notice_unsuccessful_finish: Спринт не может быть завершен.
notice_unsuccessful_finish_with_reason: 'Спринт не может быть завершён: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Создание спринтов
permission_manage_sprint_items: Управление пунктами спринта
permission_select_backlog_types_and_statuses: Выберите типы и статусы бэклога
+3 -12
View File
@@ -40,7 +40,6 @@ rw:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Backlog type
@@ -124,8 +123,6 @@ rw:
label_burndown_chart: Burndown chart
label_is_done_status: Status %{status_name} means done
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ rw:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Work package is done, when
burndown:
@@ -195,19 +190,18 @@ rw:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Backlogs
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Down
label_points_burn_up: Up
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Task board
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -215,9 +209,6 @@ rw:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ si:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: බැක්ලොග් වර්ගය
@@ -124,8 +123,6 @@ si:
label_burndown_chart: Burndown chart
label_is_done_status: තත්ත්වය %{status_name} යන්නෙන් අදහස් කරන්නේ
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ si:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: වැඩ පැකේජය සිදු කරනු ලබන්නේ කවදාද
burndown:
@@ -195,19 +190,18 @@ si:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: බැක්ලොග්ස්
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: බැක්ලොග්ස්
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: පහළට
label_points_burn_up: ඉහළට
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: කාර්ය මණ්ඩලය
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -215,9 +209,6 @@ si:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ sk:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Typ oneskorenia
@@ -128,8 +127,6 @@ sk:
label_burndown_chart: Burndown chart
label_is_done_status: Status %{status_name} znamená dokončené
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -190,8 +187,6 @@ sk:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Pracovný balík je hotový, keď
burndown:
@@ -203,19 +198,18 @@ sk:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Backlogs
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Nadol
label_points_burn_up: Nahor
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Task board
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -223,9 +217,6 @@ sk:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ sl:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Tip opravila na čakanju
@@ -128,8 +127,6 @@ sl:
label_burndown_chart: Burndown chart
label_is_done_status: Status %{status_name} pomeni zaključeno
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -190,8 +187,6 @@ sl:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Delovni paket je končan, ko
burndown:
@@ -203,19 +198,18 @@ sl:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Zaostanki
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Zaostanki
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Navzdol
label_points_burn_up: Navzgor
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Tabla opravil
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -223,9 +217,6 @@ sl:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ sr:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Tip backlog-a
@@ -126,8 +125,6 @@ sr:
label_burndown_chart: Burndown chart
label_is_done_status: Status %{status_name} znači završen
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -186,8 +183,6 @@ sr:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Radni paket je završen, kada
burndown:
@@ -199,19 +194,18 @@ sr:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Backlogs
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Down
label_points_burn_up: Up
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Task board
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -219,9 +213,6 @@ sr:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ sv:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Typ av backlogg
@@ -124,8 +123,6 @@ sv:
label_burndown_chart: Burndown chart
label_is_done_status: Status %{status_name} innebär klart
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ sv:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Arbetspaket är klart, när
burndown:
@@ -195,19 +190,18 @@ sv:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Backloggar
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Backloggar
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Ner
label_points_burn_up: Upp
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Aktivitetstavla
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -215,9 +209,6 @@ sv:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ th:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: ประเภทงานค้าง
@@ -122,8 +121,6 @@ th:
label_burndown_chart: Burndown chart
label_is_done_status: สถานะ %{status_name} หมายถึง เสร็จสิ้น
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -178,8 +175,6 @@ th:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: งานจะถือว่า เสร็จสิ้น เมื่อ
burndown:
@@ -191,19 +186,18 @@ th:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: รายการงานคงค้าง
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: รายการงานคงค้าง
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: ลง
label_points_burn_up: ขึ้น
label_sprint_edit: Edit sprint
label_sprint_new: สปรินท์ใหม่
label_backlog_and_sprints: Backlog and sprints
label_task_board: กระดานงาน
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -211,9 +205,6 @@ th:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: สร้างสปรินท์
permission_manage_sprint_items: จัดการรายการในสปรินท์
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ tr:
in_planning: Planlanıyor
active: Aktif
completed: Tamamlandı
work_packages: İş paketleri
work_package:
backlog_bucket: Birikmiş İş Havuzu
backlogs_work_package_type: Bekleme listesi türü
@@ -124,8 +123,6 @@ tr:
label_burndown_chart: Burndown grafiği
label_is_done_status: Durum %{status_name} tamamlandı anlamına geliyor
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ tr:
copy_url_to_clipboard: URL'yi panoya kopyala
copy_work_package_id: İş paketi kimliğini kopyala
move_menu: Taşı
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Sprint'e taşı
work_package_is_closed: İş paketi, ne zaman
burndown:
@@ -195,19 +190,18 @@ tr:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: İş listeleri
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown grafiği
label_inbox: Gelen Kutusu
label_backlogs: İş listeleri
label_burndown_chart: Burndown grafiği
label_sprint_board: Sprint panosu
label_points_burn_down: Aşağı
label_points_burn_up: Yukarı
label_sprint_edit: Sprint düzenle
label_sprint_new: Yeni sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Görev panosu
notice_successful_start: Sprint başladı.
notice_successful_finish: Sprint tamamlandı.
@@ -215,9 +209,6 @@ tr:
notice_unsuccessful_start_with_reason: 'Sprint başlatılamadı: %{reason}'
notice_unsuccessful_finish: Sprint tamamlanamadı.
notice_unsuccessful_finish_with_reason: 'Sprint tamamlanamadı: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Sprintler oluşturma
permission_manage_sprint_items: Sprint öğelerini yönetme
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ uk:
in_planning: На етапі планування
active: Активний
completed: Завершений
work_packages: Пакети робіт
work_package:
backlog_bucket: Сегмент беклогу
backlogs_work_package_type: Тип Backlog-у
@@ -128,8 +127,6 @@ uk:
label_burndown_chart: Діаграма згорання завдань
label_is_done_status: Стан %{status_name} означає виконано
label_sprint_board: Дошка спринту
move_to_bucket_dialog_component:
title: Перемістити в сегмент беклогу
move_to_sprint_dialog_component:
title: Перемістити в спринт
label_sprint: Спринт
@@ -190,8 +187,6 @@ uk:
copy_url_to_clipboard: Скопіювати URL-адресу в буфер обміну
copy_work_package_id: Скопіювати ідентифікатор пакета робіт
move_menu: Перемістити
move_to_backlog_bucket: Перемістити в сегмент беклогу
move_to_inbox: Перемiстити у вхідні
move_to_sprint: Перемістити в спринт
work_package_is_closed: Робочий пакет виконується, коли
burndown:
@@ -203,19 +198,18 @@ uk:
upsell:
sprint_sharing:
description: Надавайте доступ до спринтів кільком проєктам, щоб узгоджувати й координувати роботу команд у конфігураціях Масштабованої гнучкої розробки (SAFe).
label_all_sprints: Усі спринти
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Беклог і спринти
label_backlog_bucket_edit: Змінити сегмент беклогу
label_backlog_bucket_new: Новий сегмент беклогу
label_burndown_chart: Діаграма згорання завдань
label_inbox: Вхідні
label_backlogs: Backlogs
label_burndown_chart: Діаграма згорання завдань
label_sprint_board: Дошка спринту
label_points_burn_down: Вниз
label_points_burn_up: Вгору
label_sprint_edit: Редагувати спринт
label_sprint_new: Новий спринт
label_backlog_and_sprints: Беклог і спринти
label_task_board: Дошка завдань
notice_successful_start: Спринт розпочато.
notice_successful_finish: Спринт завершено.
@@ -223,9 +217,6 @@ uk:
notice_unsuccessful_start_with_reason: 'Спринт не вдалося розпочати: %{reason}'
notice_unsuccessful_finish: Спринт не вдалося завершити.
notice_unsuccessful_finish_with_reason: 'Спринт не вдалося завершити: %{reason}'
notice_work_package_invisible_after_move: 'Пакет робіт було переміщено в беклог (%{backlog}), але він там не відображається, оскільки його тип або статус виключено з беклогу.
'
permission_create_sprints: Створення спринтів
permission_manage_sprint_items: Керування елементами спринтів
permission_select_backlog_types_and_statuses: Вибір типів і статусів беклогу
+3 -12
View File
@@ -40,7 +40,6 @@ uz:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: Backlog type
@@ -124,8 +123,6 @@ uz:
label_burndown_chart: Burndown chart
label_is_done_status: Status %{status_name} means done
label_sprint_board: Sprint board
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Move to sprint
label_sprint: Sprint
@@ -182,8 +179,6 @@ uz:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: Work package is done, when
burndown:
@@ -195,19 +190,18 @@ uz:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Backlogs
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: Backlogs
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: Down
label_points_burn_up: Up
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Task board
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -215,9 +209,6 @@ uz:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
+3 -12
View File
@@ -40,7 +40,6 @@ vi:
in_planning: Đang lập kế hoạch
active: Đang hoạt động
completed: Đã hoàn thành
work_packages: Work packages
work_package:
backlog_bucket: Nhóm Backlog (Bucket)
backlogs_work_package_type: Loại Backlog
@@ -124,8 +123,6 @@ vi:
label_burndown_chart: Biểu đồ Burndown
label_is_done_status: Trạng thái %{status_name} nghĩa là đã xong
label_sprint_board: Bảng Sprint
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: Di chuyển sang Sprint
label_sprint: Sprint
@@ -180,8 +177,6 @@ vi:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy gói công việc (work package) ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Di chuyển sang Sprint
work_package_is_closed: Gói công việc được thực hiện, khi
burndown:
@@ -193,19 +188,18 @@ vi:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: Backlog
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Chỉnh sửa nhóm Backlog
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Biểu đồ Burndown
label_inbox: Hộp thư đến
label_backlogs: Backlog
label_burndown_chart: Biểu đồ Burndown
label_sprint_board: Bảng Sprint
label_points_burn_down: Xuống
label_points_burn_up: lên
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: Bảng nhiệm vụ
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -213,9 +207,6 @@ vi:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
@@ -40,7 +40,6 @@ zh-CN:
in_planning: 计划中
active: 激活
completed: 已完成
work_packages: 工作包
work_package:
backlog_bucket: 积压工作存储桶
backlogs_work_package_type: 待办清单类型
@@ -122,8 +121,6 @@ zh-CN:
label_burndown_chart: 燃尽图
label_is_done_status: 状态 %{status_name} 表示已完成
label_sprint_board: 冲刺面板
move_to_bucket_dialog_component:
title: 移至积压工作存储桶
move_to_sprint_dialog_component:
title: 移至冲刺
label_sprint: 冲刺
@@ -178,8 +175,6 @@ zh-CN:
copy_url_to_clipboard: 将 URL 复制到剪贴板
copy_work_package_id: 复制工作包 ID
move_menu: 移动
move_to_backlog_bucket: 移至积压工作存储桶
move_to_inbox: 移至收件箱
move_to_sprint: 移至冲刺
work_package_is_closed: 工作包已完成,当
burndown:
@@ -191,19 +186,18 @@ zh-CN:
upsell:
sprint_sharing:
description: 跨项目共享冲刺,以便在规模化敏捷设置 (SAFe) 中调整团队和协调工作。
label_all_sprints: 所有冲刺
label_backlog: 积压工作
label_backlogs: 待办清单
label_backlog_and_sprints: 积压工作和冲刺
label_backlog_bucket_edit: 编辑积压工作存储桶
label_backlog_bucket_new: 新建积压工作存储桶
label_burndown_chart: 燃尽图
label_inbox: 收件箱
label_backlogs: 待办清单
label_burndown_chart: 燃尽图
label_sprint_board: 冲刺面板
label_points_burn_down: 减少
label_points_burn_up: 增加
label_sprint_edit: 编辑冲刺
label_sprint_new: 新冲刺
label_backlog_and_sprints: 积压工作和冲刺
label_task_board: 任务板
notice_successful_start: 该冲刺已开始。
notice_successful_finish: 该冲刺已完成。
@@ -211,9 +205,6 @@ zh-CN:
notice_unsuccessful_start_with_reason: 无法开始该冲刺:%{reason}
notice_unsuccessful_finish: 无法完成该冲刺。
notice_unsuccessful_finish_with_reason: 无法完成该冲刺:%{reason}
notice_work_package_invisible_after_move: '工作包已移至 %{backlog} ,但不可见,因为其类型或状态已从积压工作中排除。
'
permission_create_sprints: 创建冲刺
permission_manage_sprint_items: 管理冲刺条目
permission_select_backlog_types_and_statuses: 选择积压工作类型和状态
@@ -22,7 +22,7 @@
---
zh-TW:
plugin_openproject_backlogs:
name: OpenProject辦事項
name: OpenProject辦事項
description: 此模組新增了讓敏捷團隊能夠在 Scrum 專案中使用 OpenProject 的功能。
activerecord:
attributes:
@@ -40,7 +40,6 @@ zh-TW:
in_planning: In planning
active: Active
completed: Completed
work_packages: Work packages
work_package:
backlog_bucket: Backlog Bucket
backlogs_work_package_type: 待辦事項類型
@@ -122,8 +121,6 @@ zh-TW:
label_burndown_chart: 未完成圖
label_is_done_status: 狀態 %{status_name} 表示完成
label_sprint_board: 衝刺目標
move_to_bucket_dialog_component:
title: Move to backlog bucket
move_to_sprint_dialog_component:
title: 移動到衝刺
label_sprint: 衝刺
@@ -178,8 +175,6 @@ zh-TW:
copy_url_to_clipboard: Copy URL to clipboard
copy_work_package_id: Copy work package ID
move_menu: Move
move_to_backlog_bucket: Move to backlog bucket
move_to_inbox: Move to inbox
move_to_sprint: Move to sprint
work_package_is_closed: 視為工作套件已完成
burndown:
@@ -191,19 +186,18 @@ zh-TW:
upsell:
sprint_sharing:
description: Share sprints across projects to align teams and coordinate work in scaled agile setups (SAFe).
label_all_sprints: All sprints
label_backlog: Backlog
label_backlogs: 待辦事項
label_backlog_and_sprints: Backlog and sprints
label_backlog_bucket_edit: Edit backlog bucket
label_backlog_bucket_new: New backlog bucket
label_burndown_chart: Burndown chart
label_inbox: Inbox
label_backlogs: 待辦事項
label_burndown_chart: Burndown chart
label_sprint_board: Sprint board
label_points_burn_down: 減少
label_points_burn_up: 增加
label_sprint_edit: Edit sprint
label_sprint_new: New sprint
label_backlog_and_sprints: Backlog and sprints
label_task_board: 任務看板
notice_successful_start: The sprint was started.
notice_successful_finish: The sprint was completed.
@@ -211,9 +205,6 @@ zh-TW:
notice_unsuccessful_start_with_reason: 'The sprint could not be started: %{reason}'
notice_unsuccessful_finish: The sprint could not be completed.
notice_unsuccessful_finish_with_reason: 'The sprint could not be completed: %{reason}'
notice_work_package_invisible_after_move: 'The work package was moved to %{backlog} but is not visible because its type or status is excluded from the backlog.
'
permission_create_sprints: Create sprints
permission_manage_sprint_items: Manage sprint items
permission_select_backlog_types_and_statuses: Select backlog types and statuses
@@ -73,10 +73,6 @@ af:
project_module_bim: BSF
permission_view_linked_issues: Kyk na BSF-kwessies
permission_manage_bcf: Voer en bestuur BSF-kwessies
permission_manage_bcf_explanation: |
Allows managing BCF issues, including bulk import and updates.
BCF import maps file metadata to project resources and can create or update work packages
and comments using author and timestamp values from the imported file, effectively acting on behalf of users.
permission_delete_bcf: Vee BSF-kwessies uit
oauth:
scopes:
@@ -73,10 +73,6 @@ ar:
project_module_bim: BCF
permission_view_linked_issues: لا توجد مشاكل BCF
permission_manage_bcf: استيراد وإدارة مشكلات BCF
permission_manage_bcf_explanation: |
Allows managing BCF issues, including bulk import and updates.
BCF import maps file metadata to project resources and can create or update work packages
and comments using author and timestamp values from the imported file, effectively acting on behalf of users.
permission_delete_bcf: Delete BCF issues
oauth:
scopes:
@@ -73,10 +73,6 @@ az:
project_module_bim: BCF
permission_view_linked_issues: View BCF issues
permission_manage_bcf: Import and manage BCF issues
permission_manage_bcf_explanation: |
Allows managing BCF issues, including bulk import and updates.
BCF import maps file metadata to project resources and can create or update work packages
and comments using author and timestamp values from the imported file, effectively acting on behalf of users.
permission_delete_bcf: Delete BCF issues
oauth:
scopes:
@@ -73,10 +73,6 @@ be:
project_module_bim: BCF
permission_view_linked_issues: View BCF issues
permission_manage_bcf: Import and manage BCF issues
permission_manage_bcf_explanation: |
Allows managing BCF issues, including bulk import and updates.
BCF import maps file metadata to project resources and can create or update work packages
and comments using author and timestamp values from the imported file, effectively acting on behalf of users.
permission_delete_bcf: Delete BCF issues
oauth:
scopes:
@@ -73,10 +73,6 @@ bg:
project_module_bim: BCF
permission_view_linked_issues: View BCF issues
permission_manage_bcf: Import and manage BCF issues
permission_manage_bcf_explanation: |
Allows managing BCF issues, including bulk import and updates.
BCF import maps file metadata to project resources and can create or update work packages
and comments using author and timestamp values from the imported file, effectively acting on behalf of users.
permission_delete_bcf: Delete BCF issues
oauth:
scopes:
@@ -75,10 +75,6 @@ ca:
project_module_bim: BCF
permission_view_linked_issues: Visualitza els elements de BCF
permission_manage_bcf: Importa i administra els elements de BCF
permission_manage_bcf_explanation: |
Allows managing BCF issues, including bulk import and updates.
BCF import maps file metadata to project resources and can create or update work packages
and comments using author and timestamp values from the imported file, effectively acting on behalf of users.
permission_delete_bcf: Elimina els elements de BCF
oauth:
scopes:
@@ -73,10 +73,6 @@ ckb-IR:
project_module_bim: BCF
permission_view_linked_issues: View BCF issues
permission_manage_bcf: Import and manage BCF issues
permission_manage_bcf_explanation: |
Allows managing BCF issues, including bulk import and updates.
BCF import maps file metadata to project resources and can create or update work packages
and comments using author and timestamp values from the imported file, effectively acting on behalf of users.
permission_delete_bcf: Delete BCF issues
oauth:
scopes:
@@ -73,10 +73,6 @@ cs:
project_module_bim: BCF
permission_view_linked_issues: Zobrazit problémy s BCF
permission_manage_bcf: Importovat a spravovat problémy s BCF.
permission_manage_bcf_explanation: |
Allows managing BCF issues, including bulk import and updates.
BCF import maps file metadata to project resources and can create or update work packages
and comments using author and timestamp values from the imported file, effectively acting on behalf of users.
permission_delete_bcf: Odstranit problémy BCF
oauth:
scopes:
@@ -73,10 +73,6 @@ da:
project_module_bim: BCF
permission_view_linked_issues: Vis BCF-problemer
permission_manage_bcf: Import og administrer BCF-problemer
permission_manage_bcf_explanation: |
Allows managing BCF issues, including bulk import and updates.
BCF import maps file metadata to project resources and can create or update work packages
and comments using author and timestamp values from the imported file, effectively acting on behalf of users.
permission_delete_bcf: Slet BCF sager
oauth:
scopes:
@@ -73,10 +73,6 @@ de:
project_module_bim: BCF
permission_view_linked_issues: BCF-Fälle anzeigen
permission_manage_bcf: BCF-Fälle importieren und verwalten
permission_manage_bcf_explanation: |
Allows managing BCF issues, including bulk import and updates.
BCF import maps file metadata to project resources and can create or update work packages
and comments using author and timestamp values from the imported file, effectively acting on behalf of users.
permission_delete_bcf: BCF-Fälle löschen
oauth:
scopes:
@@ -73,10 +73,6 @@ el:
project_module_bim: BCF
permission_view_linked_issues: Προβολή ζητημάτων BCF
permission_manage_bcf: Εισαγωγή και διαχείριση ζητημάτων BCF
permission_manage_bcf_explanation: |
Allows managing BCF issues, including bulk import and updates.
BCF import maps file metadata to project resources and can create or update work packages
and comments using author and timestamp values from the imported file, effectively acting on behalf of users.
permission_delete_bcf: Διαγραφή ζητημάτων BCF
oauth:
scopes:
@@ -73,10 +73,6 @@ eo:
project_module_bim: BCF
permission_view_linked_issues: View BCF issues
permission_manage_bcf: Import and manage BCF issues
permission_manage_bcf_explanation: |
Allows managing BCF issues, including bulk import and updates.
BCF import maps file metadata to project resources and can create or update work packages
and comments using author and timestamp values from the imported file, effectively acting on behalf of users.
permission_delete_bcf: Delete BCF issues
oauth:
scopes:
@@ -73,10 +73,6 @@ es:
project_module_bim: BCF
permission_view_linked_issues: Ver incidencias de BCF
permission_manage_bcf: Importar y administrar incidencias de BCF
permission_manage_bcf_explanation: |
Permite gestionar incidencias de BCF, incluyendo la importación y actualización en masa.
La importación de BCF asigna los metadatos del archivo a los recursos del proyecto y puede crear o actualizar paquetes de trabajo
y comentarios utilizando los valores de autor y marca de tiempo del archivo importado, actuando así en nombre de los usuarios.
permission_delete_bcf: Eliminar incidencias BCF
oauth:
scopes:
@@ -73,10 +73,6 @@ et:
project_module_bim: BCF
permission_view_linked_issues: View BCF issues
permission_manage_bcf: Import and manage BCF issues
permission_manage_bcf_explanation: |
Allows managing BCF issues, including bulk import and updates.
BCF import maps file metadata to project resources and can create or update work packages
and comments using author and timestamp values from the imported file, effectively acting on behalf of users.
permission_delete_bcf: Delete BCF issues
oauth:
scopes:
@@ -73,10 +73,6 @@ eu:
project_module_bim: BCF
permission_view_linked_issues: View BCF issues
permission_manage_bcf: Import and manage BCF issues
permission_manage_bcf_explanation: |
Allows managing BCF issues, including bulk import and updates.
BCF import maps file metadata to project resources and can create or update work packages
and comments using author and timestamp values from the imported file, effectively acting on behalf of users.
permission_delete_bcf: Delete BCF issues
oauth:
scopes:
@@ -75,10 +75,6 @@ fa:
project_module_bim: BCF
permission_view_linked_issues: مشاهده مشکلات BCF
permission_manage_bcf: وارد کردن و مدیریت مشکلات BCF
permission_manage_bcf_explanation: |
Allows managing BCF issues, including bulk import and updates.
BCF import maps file metadata to project resources and can create or update work packages
and comments using author and timestamp values from the imported file, effectively acting on behalf of users.
permission_delete_bcf: مشکلات حذف BCF
oauth:
scopes:
@@ -73,10 +73,6 @@ fi:
project_module_bim: BCF
permission_view_linked_issues: View BCF issues
permission_manage_bcf: Import and manage BCF issues
permission_manage_bcf_explanation: |
Allows managing BCF issues, including bulk import and updates.
BCF import maps file metadata to project resources and can create or update work packages
and comments using author and timestamp values from the imported file, effectively acting on behalf of users.
permission_delete_bcf: Delete BCF issues
oauth:
scopes:
@@ -73,10 +73,6 @@ fil:
project_module_bim: BCF
permission_view_linked_issues: View BCF issues
permission_manage_bcf: Import and manage BCF issues
permission_manage_bcf_explanation: |
Allows managing BCF issues, including bulk import and updates.
BCF import maps file metadata to project resources and can create or update work packages
and comments using author and timestamp values from the imported file, effectively acting on behalf of users.
permission_delete_bcf: Delete BCF issues
oauth:
scopes:
+1 -5
View File
@@ -61,7 +61,7 @@ fr:
perform_description: Voulez-vous importer ou mettre à jour les problèmes repris ci-dessus ?
replace_with_system_user: Les remplacer par l'utilisateur "Système"
import_as_system_user: Les importer comme utilisateur "Système".
what_to_do: Que voulez-vous faire?
what_to_do: Que voulez-vous faire?
work_package_has_newer_changes: Obsolète ! Ce sujet n'a pas été mis à jour, car les derniers changements sur le serveur étaient plus récents que la "ModifiedDate" du sujet importé. Toutefois, les commentaires sur le sujet ont été importés.
bcf_file_not_found: Impossible de localiser le fichier BCF. Veuillez recommencer le processus de téléversement.
export:
@@ -73,10 +73,6 @@ fr:
project_module_bim: BCF
permission_view_linked_issues: Voir les problèmes BCF
permission_manage_bcf: Importer et gérer les problèmes BCF
permission_manage_bcf_explanation: |
Permet de gérer les questions BCF, y compris l'importation en masse et les mises à jour.
L'importation BCF associe les métadonnées des fichiers aux ressources du projet et peut créer ou mettre à jour les work packages
et les commentaires en utilisant les valeurs d'auteur et d'horodatage du fichier importé, agissant ainsi pour le compte des utilisateurs.
permission_delete_bcf: Supprimer les problèmes BCF
oauth:
scopes:
@@ -73,10 +73,6 @@ he:
project_module_bim: BCF
permission_view_linked_issues: View BCF issues
permission_manage_bcf: Import and manage BCF issues
permission_manage_bcf_explanation: |
Allows managing BCF issues, including bulk import and updates.
BCF import maps file metadata to project resources and can create or update work packages
and comments using author and timestamp values from the imported file, effectively acting on behalf of users.
permission_delete_bcf: Delete BCF issues
oauth:
scopes:
@@ -73,10 +73,6 @@ hi:
project_module_bim: BCF
permission_view_linked_issues: View BCF issues
permission_manage_bcf: Import and manage BCF issues
permission_manage_bcf_explanation: |
Allows managing BCF issues, including bulk import and updates.
BCF import maps file metadata to project resources and can create or update work packages
and comments using author and timestamp values from the imported file, effectively acting on behalf of users.
permission_delete_bcf: Delete BCF issues
oauth:
scopes:
@@ -73,10 +73,6 @@ hr:
project_module_bim: BCF
permission_view_linked_issues: View BCF issues
permission_manage_bcf: Import and manage BCF issues
permission_manage_bcf_explanation: |
Allows managing BCF issues, including bulk import and updates.
BCF import maps file metadata to project resources and can create or update work packages
and comments using author and timestamp values from the imported file, effectively acting on behalf of users.
permission_delete_bcf: Delete BCF issues
oauth:
scopes:

Some files were not shown because too many files have changed in this diff Show More