label_work_package_note_added:"تم إضافة ملاحظة مجموعة العمل"
label_work_package_edit:"تعديل مجموعة العمل %{name}"
label_work_package_plural:"مجموعات العمل"
label_work_package_priority_updated:"تم تحديث مجموعات العمل حسب الأولوية"
label_work_package_status:"حالة مجموعة العمل"
label_work_package_status_new:"حالة جديدة"
label_work_package_status_plural:"حالات مجموعة العمل"
label_work_package_types:"أنواع مجموعة العمل"
label_work_package_updated:"تم تحديث مجموعة العمل"
label_work_package_tracking:"تتبع مجموعة العمل"
label_work_package_view_all:"عرض جميع مجموعات العمل"
label_workflow:"سير العمل"
@ -2477,6 +2475,7 @@ ar:
Set the number of days notification events for users (the source for in-app notifications) will be kept in the system. Any events older than this time will be deleted.
delay_minutes_explanation:"Email sending can be delayed to allow users with configured in app notification to confirm the notification within the application before a mail is sent out. Users who read a notification within the application will not receive an email for the already read notification."
email_digest_explanation:"Once a day, an email digest can be sent out containing a collection of all the notification users subscribed to. The setting is relative to each users configured time zone, so e.g. 8:00 will be executed at 7:00 UTC for users in UTC+1 and 9:00 UTC for those in UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
If either options "%{day_of_week_setting_name}" or "%{first_week_setting_name}" are set, the other has to be set as well to avoid inconsistencies in the frontend.
@ -2558,8 +2557,8 @@ ar:
text_work_packages_ref_in_commit_messages:"تحديد المراجع وتثبيت مجموعات العمل في رسائل commit"
text_journal_added:"%{value} %{label} أضيف"
text_journal_aggregation_time_explanation:"Individual actions of a user (e.g. updating a work package twice) are aggregated into a single action if their age difference is less than the specified timespan. They will be displayed as a single action within the application. This will also delay notifications by the same amount of time reducing the number of emails being sent."
text_journal_changed:"%{label} changed from %{old} <br/><strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} \nto %{new}"
text_journal_changed_html:"%{label} changed from %{old} %{linebreak}<strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} %{linebreak}to %{new}"
text_journal_changed_no_detail:"%{label} تم تحديثه"
text_journal_changed_with_diff:"%{label} تغير (%{link})"
label_work_package_tracking:"Проследяване на работен пакет"
label_work_package_view_all:"Покажи всички работни пакети"
label_workflow:"Работен поток"
@ -2407,6 +2405,7 @@ bg:
Set the number of days notification events for users (the source for in-app notifications) will be kept in the system. Any events older than this time will be deleted.
delay_minutes_explanation:"Email sending can be delayed to allow users with configured in app notification to confirm the notification within the application before a mail is sent out. Users who read a notification within the application will not receive an email for the already read notification."
email_digest_explanation:"Once a day, an email digest can be sent out containing a collection of all the notification users subscribed to. The setting is relative to each users configured time zone, so e.g. 8:00 will be executed at 7:00 UTC for users in UTC+1 and 9:00 UTC for those in UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
If either options "%{day_of_week_setting_name}" or "%{first_week_setting_name}" are set, the other has to be set as well to avoid inconsistencies in the frontend.
@ -2488,8 +2487,8 @@ bg:
text_work_packages_ref_in_commit_messages:"Referencing and fixing work packages in commit messages"
text_journal_added:"%{label} %{value} added"
text_journal_aggregation_time_explanation:"Individual actions of a user (e.g. updating a work package twice) are aggregated into a single action if their age difference is less than the specified timespan. They will be displayed as a single action within the application. This will also delay notifications by the same amount of time reducing the number of emails being sent."
text_journal_changed:"%{label} changed from %{old} <br/><strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} \nto %{new}"
text_journal_changed_html:"%{label} changed from %{old} %{linebreak}<strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} %{linebreak}to %{new}"
label_work_package_note_added:"Afegida nota al paquet de treball"
label_work_package_edit:"Editar paquet de treball %{name}"
label_work_package_plural:"Paquets de treball"
label_work_package_priority_updated:"Actualitzada la prioritat del paquet de treball"
label_work_package_status:"Estat del paquet de treball"
label_work_package_status_new:"Nou estat"
label_work_package_status_plural:"Estats de paquet de treball"
label_work_package_types:"Tipus de paquets de treball"
label_work_package_updated:"Paquet de treball actualitzat"
label_work_package_tracking:"Paquet de treball de seguiment"
label_work_package_view_all:"Veure tots els paquets de treball"
label_workflow:"Flux de treball"
@ -2405,6 +2403,7 @@ ca:
Set the number of days notification events for users (the source for in-app notifications) will be kept in the system. Any events older than this time will be deleted.
delay_minutes_explanation:"Email sending can be delayed to allow users with configured in app notification to confirm the notification within the application before a mail is sent out. Users who read a notification within the application will not receive an email for the already read notification."
email_digest_explanation:"Once a day, an email digest can be sent out containing a collection of all the notification users subscribed to. The setting is relative to each users configured time zone, so e.g. 8:00 will be executed at 7:00 UTC for users in UTC+1 and 9:00 UTC for those in UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
If either options "%{day_of_week_setting_name}" or "%{first_week_setting_name}" are set, the other has to be set as well to avoid inconsistencies in the frontend.
@ -2486,8 +2485,8 @@ ca:
text_work_packages_ref_in_commit_messages:"Referència i arregla els paquets de treball en els missatges dels commits"
text_journal_aggregation_time_explanation:"Individual actions of a user (e.g. updating a work package twice) are aggregated into a single action if their age difference is less than the specified timespan. They will be displayed as a single action within the application. This will also delay notifications by the same amount of time reducing the number of emails being sent."
text_journal_changed:"%{label} changed from %{old} <br/><strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} \nto %{new}"
text_journal_changed_html:"%{label} changed from %{old} %{linebreak}<strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} %{linebreak}to %{new}"
label_work_package_view_all:"Zobrazit všechny pracovní balíčky"
label_workflow:"Pracovní vrstva"
@ -2442,6 +2440,7 @@ cs:
Set the number of days notification events for users (the source for in-app notifications) will be kept in the system. Any events older than this time will be deleted.
delay_minutes_explanation:"Email sending can be delayed to allow users with configured in app notification to confirm the notification within the application before a mail is sent out. Users who read a notification within the application will not receive an email for the already read notification."
email_digest_explanation:"Once a day, an email digest can be sent out containing a collection of all the notification users subscribed to. The setting is relative to each users configured time zone, so e.g. 8:00 will be executed at 7:00 UTC for users in UTC+1 and 9:00 UTC for those in UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
If either options "%{day_of_week_setting_name}" or "%{first_week_setting_name}" are set, the other has to be set as well to avoid inconsistencies in the frontend.
@ -2523,8 +2522,8 @@ cs:
text_work_packages_ref_in_commit_messages:"Odkazování a opravování pracovních balíčků ve zprávách commitu"
text_journal_added:"%{label} %{value} přidán"
text_journal_aggregation_time_explanation:"Individual actions of a user (e.g. updating a work package twice) are aggregated into a single action if their age difference is less than the specified timespan. They will be displayed as a single action within the application. This will also delay notifications by the same amount of time reducing the number of emails being sent."
text_journal_changed:"%{label} změněn z %{old} <br/><strong>na</strong> %{new}"
text_journal_changed_plain:"%{label} změněn z %{old} \nna %{new}"
text_journal_changed_html:"%{label} changed from %{old} %{linebreak}<strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} %{linebreak}to %{new}"
label_work_package_tracking:"Sporing af arbejdspakke"
label_work_package_view_all:"Vis alle arbejdspakker"
label_workflow:"Arbejdsgang"
@ -2403,6 +2401,7 @@ da:
Set the number of days notification events for users (the source for in-app notifications) will be kept in the system. Any events older than this time will be deleted.
delay_minutes_explanation:"Email sending can be delayed to allow users with configured in app notification to confirm the notification within the application before a mail is sent out. Users who read a notification within the application will not receive an email for the already read notification."
email_digest_explanation:"Once a day, an email digest can be sent out containing a collection of all the notification users subscribed to. The setting is relative to each users configured time zone, so e.g. 8:00 will be executed at 7:00 UTC for users in UTC+1 and 9:00 UTC for those in UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
If either options "%{day_of_week_setting_name}" or "%{first_week_setting_name}" are set, the other has to be set as well to avoid inconsistencies in the frontend.
@ -2484,8 +2483,8 @@ da:
text_work_packages_ref_in_commit_messages:"Arbejdspakker håndteres i tilknyttede meddelelser"
text_journal_added:"%{label} %{value} tilføjet"
text_journal_aggregation_time_explanation:"Individual actions of a user (e.g. updating a work package twice) are aggregated into a single action if their age difference is less than the specified timespan. They will be displayed as a single action within the application. This will also delay notifications by the same amount of time reducing the number of emails being sent."
text_journal_changed:"%{label} changed from %{old} <br/><strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} \nto %{new}"
text_journal_changed_html:"%{label} changed from %{old} %{linebreak}<strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} %{linebreak}to %{new}"
Legen Sie die Anzahl der Tage fest, in denen Benachrichtigungen für Benutzer im System gehalten werden. Alle Ereignisse, die älter als diese Zeit sind, werden gelöscht und stehen nicht mehr als In-App-Benachrichtigungen zur Verfügung.
delay_minutes_explanation:"Das Senden von E-Mails kann verzögert werden, damit Benutzer Benachrichtigungen innerhalb der Anwendung bestätigen können, bevor eine E-Mail versendet wird. Benutzer, die eine Benachrichtigung innerhalb der Anwendung lesen, erhalten keine E-Mail für die bereits gelesene Benachrichtigung."
email_digest_explanation:"Einmal pro Tag kann eine E-Mail-Zusammenfassung mit allen abonnierten Benachrichtigungen verschickt werden. Die eingestellte Zeit wird für jeden Benutzer in dessen eingestellte Zeitzone umgerechnet."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
Wenn beide Optionen "%{day_of_week_setting_name}" oder "%{first_week_setting_name}" gesetzt sind der andere muss ebenfalls gesetzt werden, um Ungereimtheiten im Frontend zu vermeiden.
@ -2484,8 +2483,8 @@ de:
text_work_packages_ref_in_commit_messages:"Arbeitspaket-Beziehungen und -Status in Commit-Log-Meldungen"
text_journal_added:"%{label} %{value} wurde hinzugefügt"
text_journal_aggregation_time_explanation:"Individuelle Aktionen eines Benutzers (z. ein Arbeitspaket zweimal aktualisieren) werden zu einer einzigen Aktion zusammengefasst, wenn ihr Altersunterschied kleiner ist als der angegebene Zeitraum. Sie werden als eine einzige Aktion innerhalb der Anwendung angezeigt. Dadurch werden auch Benachrichtigungen um die gleiche Zeit verzögert, wodurch die Anzahl der gesendeten E-Mails verringert wird."
text_journal_changed:"%{label} geändert von %{old} <br/><strong>zu</strong> %{new}"
text_journal_changed_plain:"%{label} geändert von %{old} \nzu %{new}"
text_journal_changed_html:"%{label} changed from %{old} %{linebreak}<strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} %{linebreak}to %{new}"
label_work_package_view_all:"Εμφάνιση όλων των πακέτων εργασίας"
label_workflow:"Ροή εργασιών"
@ -2401,6 +2399,7 @@ el:
Set the number of days notification events for users (the source for in-app notifications) will be kept in the system. Any events older than this time will be deleted.
delay_minutes_explanation:"Email sending can be delayed to allow users with configured in app notification to confirm the notification within the application before a mail is sent out. Users who read a notification within the application will not receive an email for the already read notification."
email_digest_explanation:"Once a day, an email digest can be sent out containing a collection of all the notification users subscribed to. The setting is relative to each users configured time zone, so e.g. 8:00 will be executed at 7:00 UTC for users in UTC+1 and 9:00 UTC for those in UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
If either options "%{day_of_week_setting_name}" or "%{first_week_setting_name}" are set, the other has to be set as well to avoid inconsistencies in the frontend.
@ -2483,8 +2482,8 @@ el:
text_work_packages_ref_in_commit_messages:"Αναφορά και επιδιόρθωση πακέτων εργασίας σε μηνύματα δέσμευσης"
text_journal_added:"%{label} %{value} προστέθηκε"
text_journal_aggregation_time_explanation:"Individual actions of a user (e.g. updating a work package twice) are aggregated into a single action if their age difference is less than the specified timespan. They will be displayed as a single action within the application. This will also delay notifications by the same amount of time reducing the number of emails being sent."
text_journal_changed:"Το %{label} άλλαξε από %{old} <br/><strong>σε</strong> %{new}"
text_journal_changed_plain:"Το %{label} άλλαξε από %{old} \nσε %{new}"
text_journal_changed_html:"%{label} changed from %{old} %{linebreak}<strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} %{linebreak}to %{new}"
label_missing_or_hidden_custom_option:"(missing value or lacking permissions to access)"
label_descending:"Descendente"
label_details:"Detalles"
label_development_roadmap:"Itinerario de desarrollo"
@ -1618,7 +1622,6 @@ es:
label_none_parentheses:"(ninguno)"
label_not_contains:"no contiene"
label_not_equals:"no es"
label_notify_member_plural:"Actualizaciones por correo electrónico"
label_on:"en"
label_open_menu:"Abrir menú"
label_open_work_packages:"abierto"
@ -1738,7 +1741,6 @@ es:
label_start_to_start:"iniciar para iniciar"
label_statistics:"Estadísticas"
label_status:"Estado"
label_status_updated:"Estado del paquete de trabajo actualizado"
label_stay_logged_in:"Mantener sesión activa"
label_storage_free_space:"Espacio de disco restante"
label_storage_used_space:"Espacio de disco utilizado"
@ -1822,21 +1824,17 @@ es:
label_wiki_show_submenu_item:"Mostrar como elemento de submenú de "
label_wiki_start:"Página de inicio"
label_work_package:"Paquete de trabajo"
label_work_package_added:"Paquete de trabajo añadido"
label_work_package_attachments:"Datos adjuntos de paquete de trabajo"
label_work_package_category_new:"Nueva categoría"
label_work_package_category_plural:"Categorías de paquete de trabajo"
label_work_package_hierarchy:"Jerarquía del paquete de trabajo"
label_work_package_new:"Nuevo paquete de trabajo"
label_work_package_note_added:"Nota de paquete de trabajo añadido"
label_work_package_edit:"Editar paquete de trabajo %{name}"
label_work_package_plural:"Paquetes de trabajo"
label_work_package_priority_updated:"Prioridad de trabajo paquete actualizado"
label_work_package_status:"Estado del paquete de trabajo"
label_work_package_status_new:"Nuevo estatus"
label_work_package_status_plural:"Estatus del paquete de trabajo"
label_work_package_types:"Tipos de paquetes de trabajo"
label_work_package_updated:"Paquete de trabajo actualizado"
label_work_package_tracking:"Seguimiento de paquetes de trabajo"
label_work_package_view_all:"Ver todos los paquetes de trabajo"
label_workflow:"Flujo de trabajo"
@ -2404,6 +2402,7 @@ es:
Establecer el número de días que los eventos de notificación para los usuarios (la fuente de las notificaciones dentro de la aplicación) se mantendrá en el sistema. Cualquier evento anterior a este tiempo será eliminado.
delay_minutes_explanation:"El envío de correo electrónico puede retrasarse para permitir a los usuarios con notificaciones en la app configurada confirmar la notificación dentro de la aplicación antes de que se envíe un correo. Los usuarios que lean una notificación dentro de la aplicación no recibirán un correo electrónico para la notificación ya leída."
email_digest_explanation:"Once a day, an email digest can be sent out containing a collection of all the notification users subscribed to. The setting is relative to each users configured time zone, so e.g. 8:00 will be executed at 7:00 UTC for users in UTC+1 and 9:00 UTC for those in UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
Si se establece una de las opciones «%{day_of_week_setting_name}» o «%{first_week_setting_name}», también debe establecerse la otra para evitar incoherencias en el front-end.
@ -2485,8 +2484,8 @@ es:
text_work_packages_ref_in_commit_messages:"Referenciando y reparando paquetes de trabajo en mensajes de commit"
text_journal_added:"%{label} %{value} añadido"
text_journal_aggregation_time_explanation:"Acciones individuales de un usuario (p. ej. actualizar un paquete de trabajo dos veces) se agregan en una sola acción si su diferencia de edad es menor que el intervalo de tiempo especificado. Se mostrarán como una sola acción dentro de la aplicación. Esto también retrasará las notificaciones en la misma cantidad de tiempo reduciendo el número de correos electrónicos que se envían."
text_journal_changed:"%{label} se cambió de %{old} <br/><strong>a</strong> %{new}"
text_journal_changed_plain:"%{label} se cambió de %{old} \na %{new}"
text_journal_changed_html:"%{label} changed from %{old} %{linebreak}<strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} %{linebreak}to %{new}"
label_work_package_view_all:"Näytä kaikki tehtävät"
label_workflow:"Työnkulku"
@ -2407,6 +2405,7 @@ fi:
Set the number of days notification events for users (the source for in-app notifications) will be kept in the system. Any events older than this time will be deleted.
delay_minutes_explanation:"Email sending can be delayed to allow users with configured in app notification to confirm the notification within the application before a mail is sent out. Users who read a notification within the application will not receive an email for the already read notification."
email_digest_explanation:"Once a day, an email digest can be sent out containing a collection of all the notification users subscribed to. The setting is relative to each users configured time zone, so e.g. 8:00 will be executed at 7:00 UTC for users in UTC+1 and 9:00 UTC for those in UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
If either options "%{day_of_week_setting_name}" or "%{first_week_setting_name}" are set, the other has to be set as well to avoid inconsistencies in the frontend.
@ -2488,8 +2487,8 @@ fi:
text_work_packages_ref_in_commit_messages:"Vertailemalla ja korjaus toimia paketit sitoutua viestejä"
text_journal_added:"%{label} %{value} lisätty"
text_journal_aggregation_time_explanation:"Individual actions of a user (e.g. updating a work package twice) are aggregated into a single action if their age difference is less than the specified timespan. They will be displayed as a single action within the application. This will also delay notifications by the same amount of time reducing the number of emails being sent."
label_work_package_category_plural:"Ang mga katergorya ng work package"
label_work_package_hierarchy:"Hierarchy ng work package"
label_work_package_new:"Bagong work package"
label_work_package_note_added:"Idinagdag ang talaan ng work package"
label_work_package_edit:"I-edit ang work package %{name}"
label_work_package_plural:"Ang mga work package"
label_work_package_priority_updated:"Ang work package ay prioridad naka-update"
label_work_package_status:"Estado ng pakete ng gumagawa"
label_work_package_status_new:"Bagong estado"
label_work_package_status_plural:"Ang mga estado ng work package"
label_work_package_types:"Ang mga uri ng work package"
label_work_package_updated:"Naka-update na work package"
label_work_package_tracking:"Ang pagtra-track ng work package"
label_work_package_view_all:"Tanawin lahat ang mga package"
label_workflow:"Daloy ng trabaho"
@ -2405,6 +2403,7 @@ fil:
Set the number of days notification events for users (the source for in-app notifications) will be kept in the system. Any events older than this time will be deleted.
delay_minutes_explanation:"Email sending can be delayed to allow users with configured in app notification to confirm the notification within the application before a mail is sent out. Users who read a notification within the application will not receive an email for the already read notification."
email_digest_explanation:"Once a day, an email digest can be sent out containing a collection of all the notification users subscribed to. The setting is relative to each users configured time zone, so e.g. 8:00 will be executed at 7:00 UTC for users in UTC+1 and 9:00 UTC for those in UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
If either options "%{day_of_week_setting_name}" or "%{first_week_setting_name}" are set, the other has to be set as well to avoid inconsistencies in the frontend.
@ -2486,8 +2485,8 @@ fil:
text_work_packages_ref_in_commit_messages:"Pagsangguni at pagsaayos ng work package sa mga isinagawang mensahe"
text_journal_added:"%{label}%{value} idinagdag"
text_journal_aggregation_time_explanation:"Individual actions of a user (e.g. updating a work package twice) are aggregated into a single action if their age difference is less than the specified timespan. They will be displayed as a single action within the application. This will also delay notifications by the same amount of time reducing the number of emails being sent."
text_journal_changed:"%{label} changed from %{old} <br/><strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} \nto %{new}"
text_journal_changed_html:"%{label} changed from %{old} %{linebreak}<strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} %{linebreak}to %{new}"
text_journal_changed_no_detail:"%{label} ay naka-update"
label_work_package_category_plural:"Catégories de Lots de Travaux"
label_work_package_hierarchy:"Hiérarchie du lot de travaux"
label_work_package_new:"Nouveau Lot de Travaux"
label_work_package_note_added:"Note de Lot de Travaux ajoutée"
label_work_package_edit:"Éditer le lot de travaux %{name}"
label_work_package_plural:"Lots de Travaux"
label_work_package_priority_updated:"Priorité du lot de travaux mise à jour"
label_work_package_status:"Statut du lot de travaux"
label_work_package_status_new:"Nouveau statut"
label_work_package_status_plural:"Statuts du lot de travaux"
label_work_package_types:"Types de lots de travaux"
label_work_package_updated:"Lot de Travaux mis à jour"
label_work_package_tracking:"Suivi des lots de travaux"
label_work_package_view_all:"Afficher tous les lots de travaux"
label_workflow:"Flux de travail"
@ -2406,6 +2404,7 @@ fr:
Set the number of days notification events for users (the source for in-app notifications) will be kept in the system. Any events older than this time will be deleted.
delay_minutes_explanation:"Email sending can be delayed to allow users with configured in app notification to confirm the notification within the application before a mail is sent out. Users who read a notification within the application will not receive an email for the already read notification."
email_digest_explanation:"Once a day, an email digest can be sent out containing a collection of all the notification users subscribed to. The setting is relative to each users configured time zone, so e.g. 8:00 will be executed at 7:00 UTC for users in UTC+1 and 9:00 UTC for those in UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
Si une des options « %{day_of_week_setting_name} » ou « %{first_week_setting_name} » sont définies, l'autre doit être réglé aussi bien pour éviter les incohérences dans le frontend.
@ -2487,8 +2486,8 @@ fr:
text_work_packages_ref_in_commit_messages:"Referencer et réparer les Lot(s) de Travaux dans les messages « commit »"
text_journal_added:"%{label} %{value} ajouté"
text_journal_aggregation_time_explanation:"Individual actions of a user (e.g. updating a work package twice) are aggregated into a single action if their age difference is less than the specified timespan. They will be displayed as a single action within the application. This will also delay notifications by the same amount of time reducing the number of emails being sent."
text_journal_changed:"%{label} a changé de %{old} <br/><strong>à</strong> %{new}"
text_journal_changed_plain:"%{label} changé de %{old} à %{new}"
text_journal_changed_html:"%{label} changed from %{old} %{linebreak}<strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} %{linebreak}to %{new}"
text_journal_changed_no_detail:"%{label} mis à jour"
If CORS is enabled, these are the origins that are allowed to access OpenProject API. <br/> Please check the <a href="%{origin_link}" target="_blank">Documentation on the Origin header</a> on how to specify the expected values.
setting_apiv3_docs:"Documentation"
setting_apiv3_docs:"Dokumentacija"
setting_apiv3_docs_enabled:"Enable docs page"
setting_apiv3_docs_enabled_instructions_html:>
If the docs page is enabled you can get an interactive view of the APIv3 documentation under <a href="%{link}" target="_blank">%{link}</a>.
@ -2425,6 +2423,7 @@ hr:
Set the number of days notification events for users (the source for in-app notifications) will be kept in the system. Any events older than this time will be deleted.
delay_minutes_explanation:"Email sending can be delayed to allow users with configured in app notification to confirm the notification within the application before a mail is sent out. Users who read a notification within the application will not receive an email for the already read notification."
email_digest_explanation:"Once a day, an email digest can be sent out containing a collection of all the notification users subscribed to. The setting is relative to each users configured time zone, so e.g. 8:00 will be executed at 7:00 UTC for users in UTC+1 and 9:00 UTC for those in UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
If either options "%{day_of_week_setting_name}" or "%{first_week_setting_name}" are set, the other has to be set as well to avoid inconsistencies in the frontend.
@ -2506,8 +2505,8 @@ hr:
text_work_packages_ref_in_commit_messages:"Referencing and fixing work packages in commit messages"
text_journal_added:"%{label}%{value} dodana"
text_journal_aggregation_time_explanation:"Individual actions of a user (e.g. updating a work package twice) are aggregated into a single action if their age difference is less than the specified timespan. They will be displayed as a single action within the application. This will also delay notifications by the same amount of time reducing the number of emails being sent."
text_journal_changed:"%{label} changed from %{old} <br/><strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} \nto %{new}"
text_journal_changed_html:"%{label} changed from %{old} %{linebreak}<strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} %{linebreak}to %{new}"
label_token_users:"The following users have active backup tokens"
reset_token:
action_create:Létrehoz
action_reset:Visszaállít, reset
heading_reset:"Reset backup token"
heading_reset:"Visszaállítási kulcs törlése"
heading_create:"Visszaállítási kulcs létrehozása"
implications:>
Enabling backups will allow any user with the required permissions and this backup token to download a backup containing all data of this OpenProject installation. This includes the data of all other users.
@ -957,17 +959,17 @@ hu:
text_update_consent_time:Jelölje be ezt a négyzetet, ha újra kérni szeretné a felhasználók beleegyezését. Engedélyezem, ha megváltoztatta a fenti jóváhagyási jogi információt.
started:"Projekt másolása elindult a \"%{source_project_name}\" nevű projektből a \"%{target_project_name}\" projektbe. E-mailben értesítjük, amint \"%{target_project_name}\" elérhető."
failed:"Nem lehet másolni a %{source_project_name} projektet "
failed_internal:"Copying failed due to an internal error."
failed_internal:"Sikertelen másolás egy belső hiba miatt."
succeeded:"A %{target_project_name} projekt létrehozva "
errors:"Hiba"
project_custom_fields:'Projekt egyéni mezői'
x_objects_of_this_type:
zero:'No objects of this type'
one:'One object of this type'
other:'%{count} objects of this type'
zero:'Nincs ilyen fajta objektum'
one:'Egy ilyen fajta objektum'
other:'%{count} ilyen fajta objektum'
text:
failed:"Nem lehet másolni a \"%{source_project_name}\" projektet a \"%{target_project_name}\" projektbe."
succeeded:"A \"%{source_project_name}\" projekt átmásolva a \"%{target_project_name}\" projektbe."
@ -1113,7 +1115,7 @@ hu:
default_role_anonymous:"Anonymous"
default_role_developer:"Fejlesztő"
default_role_project_admin:"Projekt admin"
default_role_project_creator_and_staff_manager:"Staff and projects manager"
default_role_project_creator_and_staff_manager:"A vezetőség és a projekt menedzser"
default_role_non_member:"Nem tag"
default_role_reader:"Olvasó"
default_role_member:"Tag"
@ -1214,7 +1216,7 @@ hu:
error_menu_item_not_saved:Menüelem nem menthető
error_wiki_root_menu_item_conflict:>
Nem lehet átnevezni "%{old_name}", mert "%{new_name}" menü egy már létező menüvel "%{existing_caption}" (%{existing_identifier}) ütközik.
error_external_authentication_failed:"An error occurred during external authentication. Please try again."
error_external_authentication_failed:"Hiba történt a külső hitelesítés során. Kérjük, próbálja meg újra."
error_attribute_not_highlightable:"Tulajdonság(ok) nem kiemelhetők: %{attributes}"
setting_feeds_limit:"Tartalom szintjének a korlátja"
@ -2347,7 +2345,7 @@ hu:
setting_mail_handler_api_key:"API-kulcs"
setting_mail_handler_body_delimiters:"E-mailek csonkolása e sorok után"
setting_mail_handler_body_delimiter_regex:"E-mailek csonkítása a megegyező kifejezéssel"
setting_mail_handler_ignore_filenames:"Ignored mail attachments"
setting_mail_handler_ignore_filenames:"Összes melléklet figyelmen kívül hagyva"
setting_new_project_user_role_id:"Szerepkör a nem admin felhasználónak, aki létrehoz egy projektet,"
setting_password_active_rules:"Választható karakter típusok"
setting_password_count_former_banned:"A legutóbb használt jelszavak száma, ezeket tilos újra felhasználni"
@ -2403,13 +2401,14 @@ hu:
Set the number of days notification events for users (the source for in-app notifications) will be kept in the system. Any events older than this time will be deleted.
delay_minutes_explanation:"Email sending can be delayed to allow users with configured in app notification to confirm the notification within the application before a mail is sent out. Users who read a notification within the application will not receive an email for the already read notification."
email_digest_explanation:"Once a day, an email digest can be sent out containing a collection of all the notification users subscribed to. The setting is relative to each users configured time zone, so e.g. 8:00 will be executed at 7:00 UTC for users in UTC+1 and 9:00 UTC for those in UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
If either options "%{day_of_week_setting_name}" or "%{first_week_setting_name}" are set, the other has to be set as well to avoid inconsistencies in the frontend.
first_week_of_year_text:>
Select the date of January that is contained in the first week of the year. This value together with first day of the week determines the total number of weeks in a year.
projects:
section_new_projects:"Settings for new projects"
section_new_projects:"Új projekt beállításai"
section_project_overview:"Settings for project overview list"
text_work_packages_ref_in_commit_messages:"Viszonyítandó és elintézendő feladatcsoportok a véglegesítési üzenetekben"
text_journal_added:"%{label} %{value} hozzáadva"
text_journal_aggregation_time_explanation:"Individual actions of a user (e.g. updating a work package twice) are aggregated into a single action if their age difference is less than the specified timespan. They will be displayed as a single action within the application. This will also delay notifications by the same amount of time reducing the number of emails being sent."
text_regexp_multiline:'A reguláris kifejezés többsoros módban legyen alkalmazva. pld. ^---\s+'
text_repository_usernames_mapping:"Jelölje be, vagy frissítse az alkalmazás felhasználóit, minden felhasználónév eltárolva, megtalálhatóak a csomagtároló naplóban. A felhasználók ugyanazzal az alkalmazási és csomagtárolói felhasználó névvel vagy email címmel automatikusan tárolódnak."
text_select_notifications:"Select actions for which notifications should be sent."
text_select_notifications:"Válassza ki a tevékenységeket, amelyekről e-mail értesítést kell küldeni."
text_table_difference_description:"Ebben a táblázatban látható az egyszeri %{entries}. Megtekintheti a két bejegyzés közötti különbséget azáltal, hogy először kiválasztja a megfelelő jelölőnégyzeteket a táblázatban. A táblázat alatti gombra kattintva a különbségek jelennek meg."
label_work_package_view_all:"Lihat semua Paket-Penugasan"
label_workflow:"Workflow"
@ -2386,6 +2384,7 @@ id:
Set the number of days notification events for users (the source for in-app notifications) will be kept in the system. Any events older than this time will be deleted.
delay_minutes_explanation:"Email sending can be delayed to allow users with configured in app notification to confirm the notification within the application before a mail is sent out. Users who read a notification within the application will not receive an email for the already read notification."
email_digest_explanation:"Once a day, an email digest can be sent out containing a collection of all the notification users subscribed to. The setting is relative to each users configured time zone, so e.g. 8:00 will be executed at 7:00 UTC for users in UTC+1 and 9:00 UTC for those in UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
If either options "%{day_of_week_setting_name}" or "%{first_week_setting_name}" are set, the other has to be set as well to avoid inconsistencies in the frontend.
@ -2467,8 +2466,8 @@ id:
text_work_packages_ref_in_commit_messages:"Referencing & fixing Paket-Penugasan di pesan terkirim"
text_journal_aggregation_time_explanation:"Individual actions of a user (e.g. updating a work package twice) are aggregated into a single action if their age difference is less than the specified timespan. They will be displayed as a single action within the application. This will also delay notifications by the same amount of time reducing the number of emails being sent."
text_journal_changed:"%{label} changed from %{old} <br/><strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} \nto %{new}"
text_journal_changed_html:"%{label} changed from %{old} %{linebreak}<strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} %{linebreak}to %{new}"
text_journal_changed_no_detail:"%{label} telah diupdate"
text_journal_changed_with_diff:"%{label} dirubah menjadi (%{link})"
text_journal_deleted:"%{label} telah dihapus (%{old})"
label_work_package_view_all:"Vedi tutte le macro-attività"
label_workflow:"Flusso di lavoro"
@ -2403,6 +2401,7 @@ it:
Impostare il numero di giorni di notifica per gli utenti (la fonte per le notifiche in-app) sarà mantenuto nel sistema. Eventuali eventi più vecchi verranno eliminati.
delay_minutes_explanation:"L'invio di e-mail può essere ritardato per consentire agli utenti con la notifica in-app configurata di confermare la notifica all'interno dell'applicazione prima che la mail venga inviata. Gli utenti che leggono una notifica all'interno dell'applicazione non riceveranno un'email per la notifica già letta."
email_digest_explanation:"Once a day, an email digest can be sent out containing a collection of all the notification users subscribed to. The setting is relative to each users configured time zone, so e.g. 8:00 will be executed at 7:00 UTC for users in UTC+1 and 9:00 UTC for those in UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
Se le opzioni "%{day_of_week_setting_name}" o "%{first_week_setting_name}" sono impostate, dev'esser impostata anche l'altra per evitare incoerenze in vetrina.
@ -2484,8 +2483,8 @@ it:
text_work_packages_ref_in_commit_messages:"Macro-attivita che sono correlate e/o modificate nei messaggi di conferma"
text_journal_added:"%{label} %{value} aggiunto"
text_journal_aggregation_time_explanation:"Le azioni individuali di un utente (ad es. l'aggiornamento di un pacchetto di lavoro due volte) sono aggregati in un'unica azione se la loro differenza di età è inferiore al periodo di tempo specificato. Verranno visualizzate come un'unica azione all'interno dell'applicazione. Questo ritarderà anche le notifiche della stessa quantità di tempo, riducendo il numero di e-mail inviate."
text_journal_changed:"modificato da %{old} <br/><strong>a</strong> %{new} %{label}"
text_journal_changed_plain:"%{label} cambiato da %{old} \na %{new}"
text_journal_changed_html:"%{label} changed from %{old} %{linebreak}<strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} %{linebreak}to %{new}"
Set the number of days notification events for users (the source for in-app notifications) will be kept in the system. Any events older than this time will be deleted.
delay_minutes_explanation:"Email sending can be delayed to allow users with configured in app notification to confirm the notification within the application before a mail is sent out. Users who read a notification within the application will not receive an email for the already read notification."
email_digest_explanation:"Once a day, an email digest can be sent out containing a collection of all the notification users subscribed to. The setting is relative to each users configured time zone, so e.g. 8:00 will be executed at 7:00 UTC for users in UTC+1 and 9:00 UTC for those in UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
text_journal_aggregation_time_explanation:"Individual actions of a user (e.g. updating a work package twice) are aggregated into a single action if their age difference is less than the specified timespan. They will be displayed as a single action within the application. This will also delay notifications by the same amount of time reducing the number of emails being sent."
wiki:'Within the <b>wiki</b> you can document and share knowledge together with your team.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'To see your <b>task board</b>, open the sprint drop-down...'
task_board_select:'...and select the <b>task board</b> entry.'
task_board:"The task board visualizes the <b>progress for this sprint</b>. Click on the plus (+) icon next to a user story to add new tasks or impediments. <br> The status can be updated by drag and drop."
@ -528,6 +528,11 @@ ar:
involved:'I am involved'
mentioned:'I was mentioned'
watched:'I am watching'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
wiki:'Within the <b>wiki</b> you can document and share knowledge together with your team.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'To see your <b>task board</b>, open the sprint drop-down...'
task_board_select:'...and select the <b>task board</b> entry.'
task_board:"The task board visualizes the <b>progress for this sprint</b>. Click on the plus (+) icon next to a user story to add new tasks or impediments. <br> The status can be updated by drag and drop."
@ -528,6 +528,11 @@ bg:
involved:'I am involved'
mentioned:'I was mentioned'
watched:'I am watching'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
wiki:'Within the <b>wiki</b> you can document and share knowledge together with your team.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'To see your <b>task board</b>, open the sprint drop-down...'
task_board_select:'...and select the <b>task board</b> entry.'
task_board:"The task board visualizes the <b>progress for this sprint</b>. Click on the plus (+) icon next to a user story to add new tasks or impediments. <br> The status can be updated by drag and drop."
@ -528,6 +528,11 @@ ca:
involved:'I am involved'
mentioned:'I was mentioned'
watched:'I am watching'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
wiki:'Within the <b>wiki</b> you can document and share knowledge together with your team.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'To see your <b>task board</b>, open the sprint drop-down...'
task_board_select:'...and select the <b>task board</b> entry.'
task_board:"The task board visualizes the <b>progress for this sprint</b>. Click on the plus (+) icon next to a user story to add new tasks or impediments. <br> The status can be updated by drag and drop."
@ -528,6 +528,11 @@ cs:
involved:'I am involved'
mentioned:'I was mentioned'
watched:'I am watching'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
wiki:'Within the <b>wiki</b> you can document and share knowledge together with your team.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'To see your <b>task board</b>, open the sprint drop-down...'
task_board_select:'...and select the <b>task board</b> entry.'
task_board:"The task board visualizes the <b>progress for this sprint</b>. Click on the plus (+) icon next to a user story to add new tasks or impediments. <br> The status can be updated by drag and drop."
@ -527,6 +527,11 @@ da:
involved:'I am involved'
mentioned:'I was mentioned'
watched:'I am watching'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
wiki:'Im <b>Wiki</b> können Sie gemeinsam mit dem Team Informationen dokumentieren und eine Wissensdatenbank aufbauen.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'Um das <b>Taskboard</b> zu sehen, öffnen Sie das Sprint Drop-down Menü...'
task_board_select:'… und wählen Sie den Menüpunkt <b>Taskboard</b>.'
task_board:"Das Aufgabenfeld visualisiert den <b>Fortschritt für diesen Sprint</b>. Klicken Sie auf das Plus (+) Symbol neben einer User Story, um neue Aufgaben oder Hindernisse hinzuzufügen. <br> Der Status kann per Drag & Drop aktualisiert werden."
@ -527,6 +527,11 @@ de:
involved:'Ich bin beteiligt'
mentioned:'Ich wurde erwähnt'
watched:'Ich beobachte'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
wiki:'Within the <b>wiki</b> you can document and share knowledge together with your team.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'To see your <b>task board</b>, open the sprint drop-down...'
task_board_select:'...and select the <b>task board</b> entry.'
task_board:"The task board visualizes the <b>progress for this sprint</b>. Click on the plus (+) icon next to a user story to add new tasks or impediments. <br> The status can be updated by drag and drop."
@ -527,6 +527,11 @@ el:
involved:'I am involved'
mentioned:'I was mentioned'
watched:'I am watching'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
wiki:'Within the <b>wiki</b> you can document and share knowledge together with your team.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'To see your <b>task board</b>, open the sprint drop-down...'
task_board_select:'...and select the <b>task board</b> entry.'
task_board:"The task board visualizes the <b>progress for this sprint</b>. Click on the plus (+) icon next to a user story to add new tasks or impediments. <br> The status can be updated by drag and drop."
@ -528,6 +528,11 @@ es:
involved:'Estoy involucrado'
mentioned:'He sido mencionado'
watched:'Estoy viendo'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
wiki:'Within the <b>wiki</b> you can document and share knowledge together with your team.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'To see your <b>task board</b>, open the sprint drop-down...'
task_board_select:'...and select the <b>task board</b> entry.'
task_board:"The task board visualizes the <b>progress for this sprint</b>. Click on the plus (+) icon next to a user story to add new tasks or impediments. <br> The status can be updated by drag and drop."
@ -528,6 +528,11 @@ fi:
involved:'I am involved'
mentioned:'I was mentioned'
watched:'I am watching'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
wiki:'Within the <b>wiki</b> you can document and share knowledge together with your team.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'To see your <b>task board</b>, open the sprint drop-down...'
task_board_select:'...and select the <b>task board</b> entry.'
task_board:"The task board visualizes the <b>progress for this sprint</b>. Click on the plus (+) icon next to a user story to add new tasks or impediments. <br> The status can be updated by drag and drop."
@ -528,6 +528,11 @@ fil:
involved:'I am involved'
mentioned:'I was mentioned'
watched:'I am watching'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
wiki:'Within the <b>wiki</b> you can document and share knowledge together with your team.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'To see your <b>task board</b>, open the sprint drop-down...'
task_board_select:'...and select the <b>task board</b> entry.'
task_board:"The task board visualizes the <b>progress for this sprint</b>. Click on the plus (+) icon next to a user story to add new tasks or impediments. <br> The status can be updated by drag and drop."
@ -528,6 +528,11 @@ fr:
involved:'I am involved'
mentioned:'I was mentioned'
watched:'I am watching'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
wiki:'Within the <b>wiki</b> you can document and share knowledge together with your team.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'To see your <b>task board</b>, open the sprint drop-down...'
task_board_select:'...and select the <b>task board</b> entry.'
task_board:"The task board visualizes the <b>progress for this sprint</b>. Click on the plus (+) icon next to a user story to add new tasks or impediments. <br> The status can be updated by drag and drop."
@ -528,6 +528,11 @@ hr:
involved:'I am involved'
mentioned:'I was mentioned'
watched:'I am watching'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
test_ee:"Tesztelje az Enterprise Verziót 14 napig ingyen"
quick_overview:"Gyors áttekintés a projekt menedzsmentről és csapatmunkáról az OpenProjecttel."
upsale:
become_hero:"Legyél egy hős!"
benefits:
description:"What are the benefits of the Enterprise on-premises Edition?"
high_security:"Security features"
high_security:"Biztonsági szolgáltatások"
high_security_text:"Single sign on (SAML, OpenID Connect, CAS), two-factor authentication and automatic sync of LDAP groups."
installation:"Installation support"
installation:"Telepítési támogatás"
installation_text:"Experienced software engineers guide you through the complete installation and setup process in your own infrastructure."
premium_features:"Prémium funkciók"
premium_features_text:"Agile boards, custom theme and logo, graphs, intelligent workflows with custom actions, full text search for work package attachments and multi-select custom fields."
@ -236,7 +236,7 @@ hu:
text:>
The OpenProject Enterprise Edition builds on top of the Community Edition. It includes premium features and professional support mainly aimed at organizations with more than 10 users that manage business critical projects with OpenProject.
unlimited:"Korlátlan"
you_contribute:"Developers need to pay their bills, too. With the Enterprise Edition, you substantially contribute to this Open Source community effort."
you_contribute:"A fejlesztőknek is fizetni kell a számláikat. A vállalati verzióval jelentősen hozzájárulsz a nyílt forráskódú közösség erőfeszítéseihez."
custom_actions:
date:
specific:'be'
@ -280,7 +280,7 @@ hu:
homescreen:
blocks:
new_features:
text_new_features:"Read about new features and product updates."
text_new_features:"Itt találhatóak az új funkciók és a frissítések"
label_files_to_upload:"Ezek a fájlok kerülnek feltöltésre:"
label_rejected_files:"Ezeket a fájlokat nem lehet felölteni:"
label_rejected_files_reason:"Ezeket a fájlokat nem lehet feltölteni, mert a méretük nagyobb, mint %{maximumFilesize}"
@ -479,17 +479,17 @@ hu:
got_it:'Rendben'
steps:
help_menu:'The Help (?) menu provides <b>additional help resources</b>. Here you can find a user guide and helpful how-to videos and more. <br> Enjoy your work with OpenProject!'
members:'Invite new <b>members</b> to join your project.'
project_selection:'Please click on one of the demo projects that we have prepared. Demo data is currently only available in English. <br> The general <b>demo project</b> suits best for classical project management, while the <b>Scrum project</b> is better for agile project management.'
quick_add_button:'Click on the plus (+) icon in the header navigation to <b>create a new project</b> or to <b>invite coworkers</b>.'
sidebar_arrow:"Use the return arrow in the top left corner to return to the project’s <b>main menu</b>."
members:'Új <b>tagok</b> meghívása, hogy a projekthez csatlakozzanak.'
project_selection:'Kérjük, válasszon egyet a projektek közül, amelyek használható példa adatokat tartalmaznak az induláshoz. <br> A <b> Demo projekt </b> a legjobban megfelel a klasszikus projektmenedzsmentnek, míg a <b> Scrum projekt </b> jobb az agilis projektmenedzsment számára.'
quick_add_button:'Kattintson a fejlécben található (+) ikonra hogy <b>create a new project</b> vagy <b>invite coworkers</b>.'
sidebar_arrow:"Használja a vissza nyilat bal felül hogy visszatérjen a projektekhez <b>main menu</b>.."
welcome:'Áldozzon három percet erre a bemutatóra, hogy megismerje a <b>legfontosabb szolgáltatásokat</b><br> Javasoljuk, hogy végezze el a lépéseket egészen a végéig. A túra bármikor újraindítható.'
wiki:'Within the <b>wiki</b> you can document and share knowledge together with your team.'
wiki:'A <b>Wiki</b> modulban tudását dokumentálhatja és megoszthatja a csapatával.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
task_board_arrow:'To see your <b>task board</b>, open the sprint drop-down...'
task_board_select:'...and select the <b>task board</b> entry.'
overview:"Munka kezelése a <b>backlogs</b> nézetben"
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'A <b>Feladatlap</b> megjelenítéséhez nyissa meg a Sprint legördülő listát...'
task_board_select:'... és válassza ki a <b>Feladatlap</b> bejegyzést.'
task_board:"The task board visualizes the <b>progress for this sprint</b>. Click on the plus (+) icon next to a user story to add new tasks or impediments. <br> The status can be updated by drag and drop."
boards:
overview:'Select <b>boards</b> to shift the view and manage your project using the agile boards view.'
@ -497,17 +497,17 @@ hu:
add:'Click on the plus (+) icon to <b>create a new card</b> or <b>add an existing card</b> to the list on the board.'
drag:'Drag and drop your cards within a given list to reorder them, or to move them to another list. <br> You can click the info (i) icon in the upper right-hand corner or double-click a card to open its details.'
wp:
toggler:"Now let's have a look at the <b>work package</b> section, which gives you a more detailed view of your work."
toggler:"Most vessünk egy pillantást a <b>Feladatcsoport</b> kiválasztására, amely részletesebb képet ad a munkáról."
list:'This <b>work</b> package overview provides a list of all the work in your project, such as tasks, milestones, phases, and more. <br> Work packages can be created and edited directly from this view. To access the details of a particular work package, simply double-click its row.'
full_view:'The <b>work package details</b> view provides all the relevant information pertaining to a given work package, such as its description, status, priority, activities, dependencies, and comments.'
back_button:'Use the return arrow in the top left corner to exit and return to the work package list.'
create_button:'The <b>+ Create</b> button will add a new work package to your project.'
timeline_button:'You can activate the <b>Gantt chart</b> view to create a timeline for your project.'
create_button:'A <b>Létrehoz</b> gombbal tudsz új feladatot hozzáadni a projekthez.'
timeline_button:'Aktiválhatja a <b>Gantt-diagramot</b>, hogy létrehozzon egy idővonalat a projekthez.'
timeline:'Here you can <b>edit your project plan</b>, create new work packages, such as tasks, milestones, phases, and more, as well as <b>add dependencies</b>. All team members can see and update the latest plan at any time.'
already_selected:'A projekt már ki lett választva'
remove_projects:'Remove notifications for projects'
remove_projects:'Értesítések kikapcsolása a projektekhez'
title:"Értesítési beállítások"
self_notify:"Értesítés küldése a saját magam által által végrehajtott módosításokról"
password_confirmation:
@ -560,15 +565,15 @@ hu:
autocompleter:
label:'Projektnevek automatikus kiegészítése'
text_are_you_sure:"Biztos vagy benne?"
text_data_lost:"All entered data will be lost."
text_data_lost:"Az összes adat elveszhet"
types:
attribute_groups:
error_duplicate_group_name:"A %{group} név már használatban van. A csoport névnek egyedinek kell lennie."
error_no_table_configured:"Please configure a table for %{group}."
error_no_table_configured:"Kérem konfigurálja a táblát a %{group}"
reset_title:"Űrlap konfiguráció visszaállítása"
confirm_reset:>
Figyelmeztetés:Biztosan visszaállítja az alap űrlap beállítást? Az attribútumok az alapértelmezett csoportba kerülnek, a láthatósági beállítások elvesznek és MINDEN egyéni mező deaktiválódik.
upgrade_to_ee:"Upgrade to Enterprise on-premises Edition"
upgrade_to_ee:"Frissítés a Vállalati Verzióra"
upgrade_to_ee_text:"Hűha! Ha erre a funkcióra szükséged van, profi vagy! Támogatna minket, \"nyiltforrású\" fejlesztőket azzal, hogy Enterprise Edition ügyfelünk legyen?"
label_error_loading:Hiba történt a megfigyelők betöltése közben
@ -1032,8 +1037,8 @@ hu:
lacking_permission:'Please select a different project since you lack permissions to assign users to the currently selected.'
lacking_permission_info:'You lack the permission to assign users to the project you are currently in. You need to select a different one.'
next_button:'Következő'
no_results:'No projects were found'
no_invite_rights:'You are not allowed to invite members to this project'
no_results:'Egyetlen projekt sem található'
no_invite_rights:'Nincs jogosultságod meghívni felhasználókat ehhez a projekthez'
type:
required:'Please select the type to be invited'
user:
@ -1063,15 +1068,15 @@ hu:
placeholder:'Please select a placeholder'
group:'Válaszd ki a csoportot'
role:
label:'Role in %{project}'
label:'Szerepek a %{project}'
no_roles_found:'Nem található szerepkör.'
description:'This is the role that %{principal} will receive when they join your project. The role defines which actions they are allowed to take and which information they are allowed to see. <a href="https://docs.openproject.org/system-admin-guide/users-permissions/roles-permissions/#roles-and-permissions" target="_blank"> Learn more about roles and permissions. </a>'
required:'Please select a role'
required:'Kérjük, válasszon szerepet'
next_button:'Következő'
message:
label:'Invitation message'
label:'Meghívó üzenet'
description:'We will send an email to %{principal}, to which you can add a personal message here. An explanation for the invitation could be useful, or perhaps a bit of information regarding the project to help them get started.'
next_button:'Review invitation'
next_button:'Meghívó ellenőrzése'
summary:
next_button:'Meghívó küldése'
success:
@ -1082,7 +1087,7 @@ hu:
group:'The group is now a part of %{project}. Meanwhile you can already plan with that group and assign work packages for instance.'
next_button:'Folytatás'
forms:
submit_success_message:'The form was successfully submitted'
submit_success_message:'Jelentés sikeresen elküldve'
load_error_message:'There was an error loading the form'
validation_error_message:'Please fix the errors present in the form'
wiki:'Within the <b>wiki</b> you can document and share knowledge together with your team.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'To see your <b>task board</b>, open the sprint drop-down...'
task_board_select:'...and select the <b>task board</b> entry.'
task_board:"The task board visualizes the <b>progress for this sprint</b>. Click on the plus (+) icon next to a user story to add new tasks or impediments. <br> The status can be updated by drag and drop."
@ -528,6 +528,11 @@ id:
involved:'I am involved'
mentioned:'I was mentioned'
watched:'I am watching'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
wiki:'Within the <b>wiki</b> you can document and share knowledge together with your team.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'To see your <b>task board</b>, open the sprint drop-down...'
task_board_select:'...and select the <b>task board</b> entry.'
task_board:"The task board visualizes the <b>progress for this sprint</b>. Click on the plus (+) icon next to a user story to add new tasks or impediments. <br> The status can be updated by drag and drop."
@ -528,6 +528,11 @@ it:
involved:'Sono coinvolto'
mentioned:'Sono stato menzionato'
watched:'Sto guardando'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
wiki:'Within the <b>wiki</b> you can document and share knowledge together with your team.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'To see your <b>task board</b>, open the sprint drop-down...'
task_board_select:'...and select the <b>task board</b> entry.'
task_board:"The task board visualizes the <b>progress for this sprint</b>. Click on the plus (+) icon next to a user story to add new tasks or impediments. <br> The status can be updated by drag and drop."
@ -529,6 +529,11 @@ ja:
involved:'I am involved'
mentioned:'I was mentioned'
watched:'I am watching'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
wiki:'Within the <b>wiki</b> you can document and share knowledge together with your team.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'To see your <b>task board</b>, open the sprint drop-down...'
task_board_select:'...and select the <b>task board</b> entry.'
task_board:"The task board visualizes the <b>progress for this sprint</b>. Click on the plus (+) icon next to a user story to add new tasks or impediments. <br> The status can be updated by drag and drop."
@ -528,6 +528,11 @@ ko:
involved:'내가 참여된'
mentioned:'내가 멘션 된'
watched:'내가 지켜보는 중'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
wiki:'<b>Wiki</b>''yje galite dokumentuoti ir dalintis žiniomis su savo komandos nariais.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"Kairėje jūs matote produkto darbų sąrašą ir klaidų darbų sąrašą, dešinėje -- atitinkamus sprintus. Čia jūs galite kurti <b>epics, user stories ir bugs</b>, prioretizuoti vilkdami į reikiamą vietą ir priskirti sprintui."
task_board_arrow:'Norėdami matyti jūsų <b>užduočių lentą</b>, atverkite sprinto iškrentantį meniu...'
task_board_select:'... ir pasirinkite <b>task board</b> elementą.'
task_board:"Užduočių lenta vizualizuoja <b>sprinto progresą</b>. Nuspauskite pliuso (+) ženklą prie user story norėdami pridėti naujas užduotis arba trukdžius. <br> Būsena gali būti pakeista nuvelkant į reikiamą vietą."
@ -508,7 +508,7 @@ lt:
notifications:
title:"Pranešimai"
channel:"Kanalas"
no_unread:"No unread notifications"
no_unread:"Nėra neperskaitytų pranešimų"
channels:
in_app:"Programoje"
mail:"El. paštas"
@ -528,9 +528,14 @@ lt:
involved:'Aš įtrauktas'
mentioned:'Aš buvau paminėtas'
watched:'Aš stebiu'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
wiki:'Within the <b>wiki</b> you can document and share knowledge together with your team.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'To see your <b>task board</b>, open the sprint drop-down...'
task_board_select:'...and select the <b>task board</b> entry.'
task_board:"The task board visualizes the <b>progress for this sprint</b>. Click on the plus (+) icon next to a user story to add new tasks or impediments. <br> The status can be updated by drag and drop."
@ -528,6 +528,11 @@ nl:
involved:'I am involved'
mentioned:'I was mentioned'
watched:'I am watching'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
wiki:'Within the <b>wiki</b> you can document and share knowledge together with your team.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'To see your <b>task board</b>, open the sprint drop-down...'
task_board_select:'...and select the <b>task board</b> entry.'
task_board:"The task board visualizes the <b>progress for this sprint</b>. Click on the plus (+) icon next to a user story to add new tasks or impediments. <br> The status can be updated by drag and drop."
@ -528,6 +528,11 @@
involved:'I am involved'
mentioned:'I was mentioned'
watched:'I am watching'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
wiki:'Within the <b>wiki</b> you can document and share knowledge together with your team.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'To see your <b>task board</b>, open the sprint drop-down...'
task_board_select:'...and select the <b>task board</b> entry.'
task_board:"The task board visualizes the <b>progress for this sprint</b>. Click on the plus (+) icon next to a user story to add new tasks or impediments. <br> The status can be updated by drag and drop."
@ -528,6 +528,11 @@ pl:
involved:'I am involved'
mentioned:'I was mentioned'
watched:'I am watching'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
welcome:'Acompanhe um tour de apresentação de 3 minutos para descobrir mais <b>recursos importantes</b>.<br> Recomendamos que você conclua as etapas até o final. Você pode reiniciar o tour a qualquer momento.'
wiki:'No <b>wiki</b>, você pode documentar e compartilhar conhecimento junto com sua equipe. '
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
overview:"Gerencie seu trabalho na exibição de <b>backlogs</b>."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'Para ver o seu <b>quadro de tarefas</b>, abra o menu suspenso de sprint ... '
task_board_select:'... e selecione a entrada <b>quadro de tarefas</b>. '
task_board:"O painel de tarefas visualiza o progresso de <b>para este sprint</b>. Clique no ícone mais (+) ao lado de uma história de usuário para adicionar novas tarefas ou impedimentos. <br> O status pode ser atualizado arrastando e soltando."
@ -507,7 +507,7 @@ pt:
notifications:
title:"Notificações"
channel:"Canal"
no_unread:"No unread notifications"
no_unread:"Nenhuma notificação não lida"
channels:
in_app:"No aplicativo"
mail:"E-mail"
@ -527,6 +527,11 @@ pt:
involved:'Estou envolvido'
mentioned:'Eu fui mencionado'
watched:'Estou assistindo'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
wiki:'Within the <b>wiki</b> you can document and share knowledge together with your team.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'To see your <b>task board</b>, open the sprint drop-down...'
task_board_select:'...and select the <b>task board</b> entry.'
task_board:"The task board visualizes the <b>progress for this sprint</b>. Click on the plus (+) icon next to a user story to add new tasks or impediments. <br> The status can be updated by drag and drop."
@ -527,6 +527,11 @@ ro:
involved:'I am involved'
mentioned:'I was mentioned'
watched:'I am watching'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
welcome:'Совершите вводный трехминутный тур для знакомства с наиболее <b>важными особенностями</b>. <br>Рекомендуем пройти все шаги до конца. Пройти вводный тур повторно можно в любое время.'
wiki:'В пределах <b>вики</b> возможно документирование и обмен знаниями в вашей команде.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
overview:"Управляйте своей работой в представлении <b>backlogs</b>."
sprints:"Справа у вас есть бэклог продукта и бэклог ошибок, слева — соответствующие спринты. Здесь вы можете создать <b>, пользовательские истории и ошибки</b>, управлять приоритетом перетаскиванием и добавить их в спринт."
task_board_arrow:'Чтобы увидеть вашу <b>панель задач</b>, откройте выпадающий спринт...'
task_board_select:'... и выберите строку <b>Панель задач</b>.'
task_board:"Панель задач визуализирует прогресс <b>для этого спринта</b>. Нажмите на значок плюс (+) рядом с пользовательской историей, чтобы добавить новые задачи или препятствия. <br> Статус можно обновить перетаскиванием."
@ -507,7 +507,7 @@ ru:
notifications:
title:"Уведомления"
channel:"Канал"
no_unread:"No unread notifications"
no_unread:"Нет непрочитанных уведомлений"
channels:
in_app:"Встроенное"
mail:"Электронная почта"
@ -527,6 +527,11 @@ ru:
involved:'Я участвую'
mentioned:'Я был упомянут'
watched:'Я смотрю'
work_package_commented:'Пакет работ прокомментирован'
work_package_created:'Пакет работ создан'
work_package_processed:'Статус пакета работ изменен'
work_package_prioritized:'Приоритет пакета работ изменен'
wiki:'Within the <b>wiki</b> you can document and share knowledge together with your team.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'To see your <b>task board</b>, open the sprint drop-down...'
task_board_select:'...and select the <b>task board</b> entry.'
task_board:"The task board visualizes the <b>progress for this sprint</b>. Click on the plus (+) icon next to a user story to add new tasks or impediments. <br> The status can be updated by drag and drop."
@ -528,6 +528,11 @@ sk:
involved:'I am involved'
mentioned:'I was mentioned'
watched:'I am watching'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
wiki:'Within the <b>wiki</b> you can document and share knowledge together with your team.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'To see your <b>task board</b>, open the sprint drop-down...'
task_board_select:'...and select the <b>task board</b> entry.'
task_board:"The task board visualizes the <b>progress for this sprint</b>. Click on the plus (+) icon next to a user story to add new tasks or impediments. <br> The status can be updated by drag and drop."
@ -527,6 +527,11 @@ sl:
involved:'I am involved'
mentioned:'I was mentioned'
watched:'I am watching'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
wiki:'Within the <b>wiki</b> you can document and share knowledge together with your team.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'To see your <b>task board</b>, open the sprint drop-down...'
task_board_select:'...and select the <b>task board</b> entry.'
task_board:"The task board visualizes the <b>progress for this sprint</b>. Click on the plus (+) icon next to a user story to add new tasks or impediments. <br> The status can be updated by drag and drop."
@ -527,6 +527,11 @@ sv:
involved:'I am involved'
mentioned:'I was mentioned'
watched:'I am watching'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
wiki:'Within the <b>wiki</b> you can document and share knowledge together with your team.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'To see your <b>task board</b>, open the sprint drop-down...'
task_board_select:'...and select the <b>task board</b> entry.'
task_board:"The task board visualizes the <b>progress for this sprint</b>. Click on the plus (+) icon next to a user story to add new tasks or impediments. <br> The status can be updated by drag and drop."
@ -528,6 +528,11 @@ tr:
involved:'I am involved'
mentioned:'I was mentioned'
watched:'I am watching'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
wiki:'Within the <b>wiki</b> you can document and share knowledge together with your team.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'To see your <b>task board</b>, open the sprint drop-down...'
task_board_select:'...and select the <b>task board</b> entry.'
task_board:"The task board visualizes the <b>progress for this sprint</b>. Click on the plus (+) icon next to a user story to add new tasks or impediments. <br> The status can be updated by drag and drop."
@ -528,6 +528,11 @@ uk:
involved:'I am involved'
mentioned:'I was mentioned'
watched:'I am watching'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
wiki:'Within the <b>wiki</b> you can document and share knowledge together with your team.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'To see your <b>task board</b>, open the sprint drop-down...'
task_board_select:'...and select the <b>task board</b> entry.'
task_board:"The task board visualizes the <b>progress for this sprint</b>. Click on the plus (+) icon next to a user story to add new tasks or impediments. <br> The status can be updated by drag and drop."
@ -527,6 +527,11 @@ vi:
involved:'I am involved'
mentioned:'I was mentioned'
watched:'I am watching'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
wiki:'Within the <b>wiki</b> you can document and share knowledge together with your team.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'To see your <b>task board</b>, open the sprint drop-down...'
task_board_select:'...and select the <b>task board</b> entry.'
task_board:"The task board visualizes the <b>progress for this sprint</b>. Click on the plus (+) icon next to a user story to add new tasks or impediments. <br> The status can be updated by drag and drop."
@ -528,6 +528,11 @@ zh-CN:
involved:'I am involved'
mentioned:'I was mentioned'
watched:'I am watching'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
wiki:'Within the <b>wiki</b> you can document and share knowledge together with your team.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'To see your <b>task board</b>, open the sprint drop-down...'
task_board_select:'...and select the <b>task board</b> entry.'
task_board:"The task board visualizes the <b>progress for this sprint</b>. Click on the plus (+) icon next to a user story to add new tasks or impediments. <br> The status can be updated by drag and drop."
@ -527,6 +527,11 @@ zh-TW:
involved:'I am involved'
mentioned:'I was mentioned'
watched:'I am watching'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
error_enterprise_only:"- OpenProject Enterprise Edition에서만 사용할 수 있습니다"
error_unauthorized:"액세스하지 못할 수 있습니다."
error_readonly:"- 쓰려고 했지만 쓸 수 없습니다."
email:"is not a valid email address."
empty:"비워둘 수 없습니다."
even:"에 짝수를 입력해 주세요"
exclusion:"예약됨"
@ -699,6 +700,7 @@ ko:
not_start_date:"마일스톤에서 요구하지만, 시작 날짜가 없음"
parent:
cannot_be_milestone:"마일스톤에 포함될 수 없음"
cannot_be_self_assigned:"cannot be assigned to itself."
cannot_be_in_another_project:"다른 프로젝트에 포함될 수 없음"
not_a_valid_parent:"은(는) 올바르지 않은 값입니다"
start_date:
@ -1294,6 +1296,7 @@ ko:
expiration:"만료"
indefinite_expiration:"사용 안 함"
notifications:
send_notifications:"Send notifications for this action"
work_packages:
subject:
created:"The work package was created."
@ -1430,6 +1433,7 @@ ko:
label_deleted:"삭제됨"
label_deleted_custom_field:"(삭제된 사용자 지정 필드)"
label_deleted_custom_option:"(삭제된 옵션)"
label_missing_or_hidden_custom_option:"(missing value or lacking permissions to access)"
label_descending:"내림차순"
label_details:"세부 정보"
label_development_roadmap:"개발 로드맵"
@ -1603,7 +1607,6 @@ ko:
label_none_parentheses:"(없음)"
label_not_contains:"포함하지 않음"
label_not_equals:"일치하지 않음"
label_notify_member_plural:"이메일 업데이트"
label_on:"에"
label_open_menu:"메뉴 열기"
label_open_work_packages:"열기"
@ -1723,7 +1726,6 @@ ko:
label_start_to_start:"시작 - 시작"
label_statistics:"통계"
label_status:"상태"
label_status_updated:"작업 패키지 상태 업데이트됨"
label_stay_logged_in:"로그인 상태 유지"
label_storage_free_space:"남은 디스크 공간"
label_storage_used_space:"사용 중 디스크 공간"
@ -1807,21 +1809,17 @@ ko:
label_wiki_show_submenu_item:"다음의 하위 메뉴 항목으로 표시: "
label_wiki_start:"시작 페이지"
label_work_package:"작업 패키지"
label_work_package_added:"작업 패키지 추가됨"
label_work_package_attachments:"작업 패키지 첨부 파일"
label_work_package_category_new:"새 카테고리"
label_work_package_category_plural:"작업 패키지 카테고리"
label_work_package_hierarchy:"작업 패키지 계층 구조"
label_work_package_new:"새 작업 패키지"
label_work_package_note_added:"작업 패키지 메모 추가됨"
label_work_package_edit:"작업 패키지 %{name} 편집"
label_work_package_plural:"작업 패키지"
label_work_package_priority_updated:"작업 패키지 우선 순위 업데이트됨"
label_work_package_status:"작업 패키지 상태"
label_work_package_status_new:"새 상태"
label_work_package_status_plural:"작업 패키지 상태"
label_work_package_types:"작업 패키지 유형"
label_work_package_updated:"작업 패키지 업데이트됨"
label_work_package_tracking:"작업 패키지 추적"
label_work_package_view_all:"모든 작업 패키지 보기"
label_workflow:"워크플로"
@ -2386,6 +2384,7 @@ ko:
사용자에 대한 알림 이벤트(앱 내 알림에 대해서)가 시스템에 보관되는 일 수를 설정합니다. 이 시간보다 오래된 모든 이벤트는 삭제됩니다.
delay_minutes_explanation:"앱 내 알림이 구성된 사용자가 메일이 발송되기 전에 애플리케이션 내에서 알림을 확인할 수 있도록 이메일 전송이 지연될 수 있습니다. 애플리케이션 내에서 알림을 읽은 사용자는 이미 읽은 알림에 대한 이메일을 받지 않습니다."
email_digest_explanation:"Once a day, an email digest can be sent out containing a collection of all the notification users subscribed to. The setting is relative to each users configured time zone, so e.g. 8:00 will be executed at 7:00 UTC for users in UTC+1 and 9:00 UTC for those in UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
"%{day_of_week_setting_name}"이나 "%{first_week_setting_name}" 중 하나가 설정되었다면, 프론트엔드 충돌을 방지하기 위해 나머지 하나도 설정되어야 합니다.
@ -2467,8 +2466,8 @@ ko:
text_work_packages_ref_in_commit_messages:"커밋 메시지의 작업 패키지 참조 또는 수정"
text_journal_added:"%{label} %{value} 추가됨"
text_journal_aggregation_time_explanation:"사용자의 개별 작업(예: 작업 패키지를 두 번 업데이트)은 연령 차이가 지정된 기간 미만인 경우 단일 작업으로 집계됩니다. 애플리케이션 내에서 단일 작업으로 표시됩니다. 이것은 또한 전송되는 이메일의 수를 줄이는 동일한 시간만큼 알림을 지연시킵니다."
label_work_package_view_all:"Peržiūrėti visus darbų paketus"
label_workflow:"Darbų eiga"
@ -2437,6 +2435,7 @@ lt:
Nustatykite kiek dienų saugoti pranešimų įvykius sistemoje (tuos, kurie bus rodomi kaip programos pranešimai). Visi įvykiai, senesni nei šis laikas bus pašalinti.
delay_minutes_explanation:"El.laiškų siuntimas gali būti užlaikytas vartotojams, kurie yra susikonfigūravę gauti pranešimus tiesiai programoje ir gali patvirtinti pranešimą prieš tai, kai jis bus išsiųstas el. paštu. Vartotojai, kurie perskaito pranešimus programoje negaus tų laiškų, kuriuos pranešimus perskaitys."
email_digest_explanation:"El.pašto santrauka su visais vartotojo prenumeruojamais pranešimais gali būti išsiųsta vieną kartą per dieną. Šis nustatymas atsižvelgia į vartotojo laiko zoną, t.y. 8:00 reikš, kad išsiųsta bus 7:00 UTC vartotojams iš UTC+1 zonos, ir 9:00 UTC tiems, kurie nustatę UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
Jei vienas iš „%{day_of_week_setting_name}“ ir „%{first_week_setting_name}“ yra nustatytas, tai kitas taip pat turi būti nustatytas vengiant netikslumų vartotojo sąsajoje.
@ -2518,8 +2517,8 @@ lt:
text_work_packages_ref_in_commit_messages:"Darbų paketų susiejimas ir taisymas pavedimų žinutėse"
text_journal_added:"%{label} %{value} pridėtas"
text_journal_aggregation_time_explanation:"Visi atskiri vartotojo veiksmai (t.y. darbų paketo atnaujinimas du kartus) yra sugrupuojami į vieną veiksmą, jei laiko tarpas tarp jų yra mažesnis už šį nustatymą. Programoje jie bus rodomi kaip vienas veiksmas. Tiek pat bus pavėlinti ir pranešimai. Dėl to sumažės siunčiamų el.laiškų skaičius."
text_journal_changed:"%{label} pakeista iš %{old} <br/><strong>į</strong> %{new}"
text_journal_changed_plain:"%{label} pakeista iš %{old} \nį %{new}"
text_journal_changed_html:"%{label} pakeista iš %{old} %{linebreak}<strong>į</strong> %{new}"
text_journal_changed_plain:"%{label} pakeista iš %{old} %{linebreak}į %{new}"
label_work_package_view_all:"Bekijk alle werkpakketten"
label_workflow:"Werkstroom"
@ -2406,6 +2404,7 @@ nl:
Set the number of days notification events for users (the source for in-app notifications) will be kept in the system. Any events older than this time will be deleted.
delay_minutes_explanation:"Email sending can be delayed to allow users with configured in app notification to confirm the notification within the application before a mail is sent out. Users who read a notification within the application will not receive an email for the already read notification."
email_digest_explanation:"Once a day, an email digest can be sent out containing a collection of all the notification users subscribed to. The setting is relative to each users configured time zone, so e.g. 8:00 will be executed at 7:00 UTC for users in UTC+1 and 9:00 UTC for those in UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
If either options "%{day_of_week_setting_name}" or "%{first_week_setting_name}" are set, the other has to be set as well to avoid inconsistencies in the frontend.
@ -2487,8 +2486,8 @@ nl:
text_work_packages_ref_in_commit_messages:"Verwijzen naar en herstellen van de werkpakketten in commit berichten"
text_journal_added:"%{label} %{value} toegevoegd"
text_journal_aggregation_time_explanation:"Individual actions of a user (e.g. updating a work package twice) are aggregated into a single action if their age difference is less than the specified timespan. They will be displayed as a single action within the application. This will also delay notifications by the same amount of time reducing the number of emails being sent."
text_journal_changed:"%{label} gewijzigd van %{old} <br/><strong>naar</strong> %{new}"
text_journal_changed_plain:"%{label} gewijzigd van %{old} naar %{new}"
text_journal_changed_html:"%{label} changed from %{old} %{linebreak}<strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} %{linebreak}to %{new}"
label_work_package_tracking:"Sporing av arbeidspakke"
label_work_package_view_all:"Vis alle arbeidspakker"
label_workflow:"Arbeidsflyt"
@ -2407,6 +2405,7 @@
Set the number of days notification events for users (the source for in-app notifications) will be kept in the system. Any events older than this time will be deleted.
delay_minutes_explanation:"Email sending can be delayed to allow users with configured in app notification to confirm the notification within the application before a mail is sent out. Users who read a notification within the application will not receive an email for the already read notification."
email_digest_explanation:"Once a day, an email digest can be sent out containing a collection of all the notification users subscribed to. The setting is relative to each users configured time zone, so e.g. 8:00 will be executed at 7:00 UTC for users in UTC+1 and 9:00 UTC for those in UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
If either options "%{day_of_week_setting_name}" or "%{first_week_setting_name}" are set, the other has to be set as well to avoid inconsistencies in the frontend.
@ -2488,8 +2487,8 @@
text_work_packages_ref_in_commit_messages:"Referèring og retting av arbeidspakker i innsendingsmeldinger"
text_journal_added:"%{label} %{value} lagt til"
text_journal_aggregation_time_explanation:"Individual actions of a user (e.g. updating a work package twice) are aggregated into a single action if their age difference is less than the specified timespan. They will be displayed as a single action within the application. This will also delay notifications by the same amount of time reducing the number of emails being sent."
text_journal_changed:"%{label} changed from %{old} <br/><strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} \nto %{new}"
text_journal_changed_html:"%{label} changed from %{old} %{linebreak}<strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} %{linebreak}to %{new}"
label_work_package_view_all:"Pokaż wszystkie pakiety robocze"
label_workflow:"Przepływ pracy"
@ -2437,6 +2435,7 @@ pl:
Set the number of days notification events for users (the source for in-app notifications) will be kept in the system. Any events older than this time will be deleted.
delay_minutes_explanation:"Email sending can be delayed to allow users with configured in app notification to confirm the notification within the application before a mail is sent out. Users who read a notification within the application will not receive an email for the already read notification."
email_digest_explanation:"Once a day, an email digest can be sent out containing a collection of all the notification users subscribed to. The setting is relative to each users configured time zone, so e.g. 8:00 will be executed at 7:00 UTC for users in UTC+1 and 9:00 UTC for those in UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
Jeśli ustawiona jest opcja „%{day_of_week_setting_name}” albo „%{first_week_setting_name}”, druga musi zostać ustawiona w taki sposób, aby uniknąć niespójności we frontendzie.
@ -2518,8 +2517,8 @@ pl:
text_work_packages_ref_in_commit_messages:"Odwołania i poprawki do pakietów roboczych w wiadomościach o zmianach"
text_journal_added:"%{label} %{value} added"
text_journal_aggregation_time_explanation:"Individual actions of a user (e.g. updating a work package twice) are aggregated into a single action if their age difference is less than the specified timespan. They will be displayed as a single action within the application. This will also delay notifications by the same amount of time reducing the number of emails being sent."
text_journal_changed:"%{label} zmieniono z %{old} <br/><strong>na</strong> %{new}"
text_journal_changed_plain:"%{label} zmieniono z %{old} \nna %{new}"
text_journal_changed_html:"%{label} changed from %{old} %{linebreak}<strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} %{linebreak}to %{new}"
label_missing_or_hidden_custom_option:"(missing value or lacking permissions to access)"
label_descending:"Decrescente"
label_details:"Detalhes"
label_development_roadmap:"Planejamento do desenvolvimento"
@ -1619,7 +1623,6 @@ pt:
label_none_parentheses:"(nenhum)"
label_not_contains:"não contém"
label_not_equals:"não é"
label_notify_member_plural:"Emails atualizados"
label_on:"ligado"
label_open_menu:"Abrir menu"
label_open_work_packages:"aberto"
@ -1739,7 +1742,6 @@ pt:
label_start_to_start:"início à início"
label_statistics:"Estatísticas"
label_status:"Status"
label_status_updated:"Situação de pacote de trabalho atualizada"
label_stay_logged_in:"Permanecer conectado"
label_storage_free_space:"Espaço em disco restante"
label_storage_used_space:"Espaço em disco utilizado"
@ -1823,21 +1825,17 @@ pt:
label_wiki_show_submenu_item:"Mostrar como item do submenu de "
label_wiki_start:"Página inicial"
label_work_package:"Pacote de trabalho"
label_work_package_added:"Pacote de trabalho adicionado"
label_work_package_attachments:"Anexos de pacote de trabalho"
label_work_package_category_new:"Nova categoria"
label_work_package_category_plural:"Categorias de pacote de trabalho"
label_work_package_hierarchy:"Hierarquia de pacotes de trabalho"
label_work_package_new:"Novo pacote de trabalho"
label_work_package_note_added:"Anotação acrescentada ao pacote de trabalho"
label_work_package_edit:"Editar pacote de trabalho %{name}"
label_work_package_plural:"Pacotes de trabalho"
label_work_package_priority_updated:"Prioridade do pacote de trabalho atualizada"
label_work_package_status:"Situação do pacote de trabalho"
label_work_package_status_new:"Nova situação"
label_work_package_status_plural:"Situações do Pacote de Trabalho"
label_work_package_types:"Tipos de pacote de trabalho"
label_work_package_updated:"Pacote de trabalho atualizado"
label_work_package_tracking:"Controle de pacote de trabalho"
label_work_package_view_all:"Exibir todos os pacotes de trabalho"
label_workflow:"Fluxo de Trabalho"
@ -2404,6 +2402,7 @@ pt:
Defina o número de dias em que os eventos de notificação para usuários (a fonte para notificações no aplicativo) serão mantidos no sistema. Todos os eventos anteriores a esse horário serão excluídos.
delay_minutes_explanation:"O envio de e-mail pode ser atrasado para permitir que os usuários com notificação configurada no aplicativo confirmem a notificação no aplicativo antes que um e-mail seja enviado. Os usuários que lerem uma notificação no aplicativo não receberão um e-mail com a notificação já lida. "
email_digest_explanation:"Uma vez por dia, um e-mail resumo pode ser enviado contendo uma coleção de todas as notificações que os usuários assinaram. A configuração é relativa ao fuso horário de cada usuário configurado, por exemplo, 8:00 será executado às 7:00 UTC para usuários em UTC + 1 e 9:00 UTC para aqueles em UTC-1. "
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
Se as opções "%{day_of_week_setting_name}" ou "%{first_week_setting_name}" forem definidas, a outra também deve ser definida, para evitar inconsistências no front-end.
@ -2485,8 +2484,8 @@ pt:
text_work_packages_ref_in_commit_messages:"Referenciando e corrigindo pacotes de trabalho nas mensagens de commit"
text_journal_added:"%{label} %{value} adicionado"
text_journal_aggregation_time_explanation:"As ações individuais de um usuário (por exemplo, atualizar um pacote de trabalho duas vezes) são agregadas em uma única ação se a diferença de idade for menor que o intervalo de tempo especificado. Eles serão exibidos como uma única ação no aplicativo. Isso também atrasará as notificações na mesma quantidade de tempo, reduzindo o número de e-mails enviados. "
text_journal_changed:"%{label} alterado de %{old} <br/><strong>para</strong> %{new}"
text_journal_changed_plain:"%{label} alterado de %{old} \npara %{new}"
text_journal_changed_html:"%{label} modificado de %{old} %{linebreak}<strong>para</strong> %{new}"
text_journal_changed_plain:"%{label} alterado de %{old} %{linebreak}para %{new}"
label_missing_or_hidden_custom_option:"(missing value or lacking permissions to access)"
label_descending:"Descrescător"
label_details:"Detalii"
label_development_roadmap:"Plan de lucru pentru dezvoltare"
@ -1638,7 +1642,6 @@ ro:
label_none_parentheses:"(nimic)"
label_not_contains:"nu conține"
label_not_equals:"nu este"
label_notify_member_plural:"Actualizări prin e-mail"
label_on:"pe"
label_open_menu:"Deschidere meniu"
label_open_work_packages:"deschise"
@ -1758,7 +1761,6 @@ ro:
label_start_to_start:"început la început"
label_statistics:"Statistici"
label_status:"Stare"
label_status_updated:"Stare pachet de lucru actualizată"
label_stay_logged_in:"Rămâneți conectat"
label_storage_free_space:"Spațiu pe disc rămas"
label_storage_used_space:"Spațiu pe disc folosit"
@ -1842,21 +1844,17 @@ ro:
label_wiki_show_submenu_item:"Afișare ca submeniu pentru "
label_wiki_start:"Pagină de start"
label_work_package:"Pachet de lucru"
label_work_package_added:"Pachet de lucru adăugat"
label_work_package_attachments:"Anexe la pachetul de lucru"
label_work_package_category_new:"Categorie nouă"
label_work_package_category_plural:"Categorii de pachete de lucru"
label_work_package_hierarchy:"Ierarhia pachetelor de lucru"
label_work_package_new:"Pachet de lucru nou"
label_work_package_note_added:"Notă adăugată la pachetul de lucru"
label_work_package_edit:"Editare pachet de lucru %{name}"
label_work_package_plural:"Pachete de lucru"
label_work_package_priority_updated:"Prioritate pachet de lucru actualizată"
label_work_package_status:"Stare pachet de lucru"
label_work_package_status_new:"Stare nouă"
label_work_package_status_plural:"Stări pachete de lucru"
label_work_package_types:"Tipuri de pachete de lucru"
label_work_package_updated:"Pachet de lucru actualizat"
label_work_package_tracking:"Urmărire pachete de lucru"
label_work_package_view_all:"Toate pachetele de lucru"
label_workflow:"Flux de lucru"
@ -2424,6 +2422,7 @@ ro:
Set the number of days notification events for users (the source for in-app notifications) will be kept in the system. Any events older than this time will be deleted.
delay_minutes_explanation:"Email sending can be delayed to allow users with configured in app notification to confirm the notification within the application before a mail is sent out. Users who read a notification within the application will not receive an email for the already read notification."
email_digest_explanation:"Once a day, an email digest can be sent out containing a collection of all the notification users subscribed to. The setting is relative to each users configured time zone, so e.g. 8:00 will be executed at 7:00 UTC for users in UTC+1 and 9:00 UTC for those in UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
If either options "%{day_of_week_setting_name}" or "%{first_week_setting_name}" are set, the other has to be set as well to avoid inconsistencies in the frontend.
@ -2505,8 +2504,8 @@ ro:
text_work_packages_ref_in_commit_messages:"Referențiere și rezolvare a pachetelor de lucru în mesajele de încărcare"
text_journal_added:"%{label} %{value} adăugat"
text_journal_aggregation_time_explanation:"Individual actions of a user (e.g. updating a work package twice) are aggregated into a single action if their age difference is less than the specified timespan. They will be displayed as a single action within the application. This will also delay notifications by the same amount of time reducing the number of emails being sent."
text_journal_changed:"%{label} a fost schimbat din %{old} <br/><strong>în</strong> %{new}"
text_journal_changed_plain:"%{label} schimbat de la %{old}\nla %{new}"
text_journal_changed_html:"%{label} changed from %{old} %{linebreak}<strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} %{linebreak}to %{new}"
label_work_package_view_all:"Посмотреть все пакеты работ"
label_workflow:"Рабочий поток"
@ -2439,6 +2437,7 @@ ru:
Количество дней в системе уведомлений для пользователей (источник уведомлений в приложении). Все события, старше этого времени будут удалены.
delay_minutes_explanation:"Отправка электронной почты может быть отложена, чтобы разрешить пользователям с настроенными в уведомлениях приложения, чтобы подтвердить уведомление внутри приложения до отправки почты. Пользователи, которые прочитали уведомление в приложении, не будут получать по электронной почте уже прочитанное уведомление."
email_digest_explanation:"Раз в сутки может быть отправлен дайджест с подборкой всех подписчиков на уведомления. Параметр относителен к каждому пользователю, настроенному часовой пояс, так что напр. 8:00 будет выполнено в 7:00 UTC для пользователей в UTC+1 и 9:00 UTC для пользователей в UTC-1."
events_explanation:'Регулирует, по каким событиям отправляется письмо. Пакеты работ исключаются из этого списка, поскольку уведомления для них могут быть настроены специально для каждого пользователя.'
display:
first_date_of_week_and_year_set:>
Если параметры "%{day_of_week_setting_name}" или "%{first_week_setting_name}" заданы, должны быть заданы и другие тоже во избежание несоответствий в интерфейсе.
@ -2520,8 +2519,8 @@ ru:
text_work_packages_ref_in_commit_messages:"Привязка и фиксация пакетов работ в сообщениях коммитов"
text_journal_added:"%{label} %{value} добавлено"
text_journal_aggregation_time_explanation:"Личные действия пользователя (напр. обновление пакета работ дважды) агрегируются в одно действие, если их разница в возрасте меньше указанного промежутка времени. Они будут отображаться как одно действие внутри приложения. Это также задерживает уведомления на то же количество времени, уменьшая количество отправляемых сообщений."
text_journal_changed:"%{label} изменено с %{old} <br/><strong>на</strong> %{new}"
text_journal_changed_plain:"%{label} изменено с %{old} на %{new}"
text_journal_changed_html:"%{label} изменено с %{old} %{linebreak}<strong>на</strong> %{new}"
text_journal_changed_plain:"%{label} изменено с %{old} %{linebreak}на %{new}"
label_work_package_view_all:"Zobraziť všetky pracovné balíčky"
label_workflow:"Pracovný postup"
@ -2442,6 +2440,7 @@ sk:
Set the number of days notification events for users (the source for in-app notifications) will be kept in the system. Any events older than this time will be deleted.
delay_minutes_explanation:"Email sending can be delayed to allow users with configured in app notification to confirm the notification within the application before a mail is sent out. Users who read a notification within the application will not receive an email for the already read notification."
email_digest_explanation:"Once a day, an email digest can be sent out containing a collection of all the notification users subscribed to. The setting is relative to each users configured time zone, so e.g. 8:00 will be executed at 7:00 UTC for users in UTC+1 and 9:00 UTC for those in UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
If either options "%{day_of_week_setting_name}" or "%{first_week_setting_name}" are set, the other has to be set as well to avoid inconsistencies in the frontend.
@ -2523,8 +2522,8 @@ sk:
text_work_packages_ref_in_commit_messages:"Odkazovanie a oprava pracovných balíčkov v podrobnejšom vysvetľujúcom texte"
text_journal_added:"%{label} %{value} pridaných"
text_journal_aggregation_time_explanation:"Individual actions of a user (e.g. updating a work package twice) are aggregated into a single action if their age difference is less than the specified timespan. They will be displayed as a single action within the application. This will also delay notifications by the same amount of time reducing the number of emails being sent."
text_journal_changed:"%{label} zmenený z %{old} <br/><strong>na</strong> %{new}"
text_journal_changed_plain:"%{label} zmenený z %{old} \nna %{new}"
text_journal_changed_html:"%{label} changed from %{old} %{linebreak}<strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} %{linebreak}to %{new}"
label_work_package_view_all:"Oglejte si vse delovne pakete"
label_workflow:"Potek dela"
@ -2440,6 +2438,7 @@ sl:
Set the number of days notification events for users (the source for in-app notifications) will be kept in the system. Any events older than this time will be deleted.
delay_minutes_explanation:"Email sending can be delayed to allow users with configured in app notification to confirm the notification within the application before a mail is sent out. Users who read a notification within the application will not receive an email for the already read notification."
email_digest_explanation:"Once a day, an email digest can be sent out containing a collection of all the notification users subscribed to. The setting is relative to each users configured time zone, so e.g. 8:00 will be executed at 7:00 UTC for users in UTC+1 and 9:00 UTC for those in UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
If either options "%{day_of_week_setting_name}" or "%{first_week_setting_name}" are set, the other has to be set as well to avoid inconsistencies in the frontend.
@ -2521,8 +2520,8 @@ sl:
text_work_packages_ref_in_commit_messages:"Sklicevanje in popravljanje delovnih paketov v sporočilih"
text_journal_added:"%{label} %{value} dodan"
text_journal_aggregation_time_explanation:"Individual actions of a user (e.g. updating a work package twice) are aggregated into a single action if their age difference is less than the specified timespan. They will be displayed as a single action within the application. This will also delay notifications by the same amount of time reducing the number of emails being sent."
text_journal_changed:"%{label} se je spremenila iz %{old} <br/><strong>v</strong>%{new}"
text_journal_changed_plain:"%{label} se je spremenil iz %{old}\nv %{new}"
text_journal_changed_html:"%{label} changed from %{old} %{linebreak}<strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} %{linebreak}to %{new}"
label_work_package_view_all:"Visa alla arbetspaket"
label_workflow:"Arbetsflöde"
@ -2404,6 +2402,7 @@ sv:
Set the number of days notification events for users (the source for in-app notifications) will be kept in the system. Any events older than this time will be deleted.
delay_minutes_explanation:"Email sending can be delayed to allow users with configured in app notification to confirm the notification within the application before a mail is sent out. Users who read a notification within the application will not receive an email for the already read notification."
email_digest_explanation:"Once a day, an email digest can be sent out containing a collection of all the notification users subscribed to. The setting is relative to each users configured time zone, so e.g. 8:00 will be executed at 7:00 UTC for users in UTC+1 and 9:00 UTC for those in UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
If either options "%{day_of_week_setting_name}" or "%{first_week_setting_name}" are set, the other has to be set as well to avoid inconsistencies in the frontend.
@ -2485,8 +2484,8 @@ sv:
text_work_packages_ref_in_commit_messages:"Referenser och fixande av arbetspaket i incheckningsmeddelanden"
text_journal_added:"%{label} %{value} lades till"
text_journal_aggregation_time_explanation:"Individual actions of a user (e.g. updating a work package twice) are aggregated into a single action if their age difference is less than the specified timespan. They will be displayed as a single action within the application. This will also delay notifications by the same amount of time reducing the number of emails being sent."
text_journal_changed:"%{label} ändrade från %{old} <br/><strong>till</strong> %{new}"
text_journal_changed_plain:"%{label} ändrade från %{old} \ntill %{new}"
text_journal_changed_html:"%{label} changed from %{old} %{linebreak}<strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} %{linebreak}to %{new}"
label_work_package_view_all:"Tüm iş paketleri görüntüle"
label_workflow:"İş akışı"
@ -2407,6 +2405,7 @@ tr:
Set the number of days notification events for users (the source for in-app notifications) will be kept in the system. Any events older than this time will be deleted.
delay_minutes_explanation:"Email sending can be delayed to allow users with configured in app notification to confirm the notification within the application before a mail is sent out. Users who read a notification within the application will not receive an email for the already read notification."
email_digest_explanation:"Once a day, an email digest can be sent out containing a collection of all the notification users subscribed to. The setting is relative to each users configured time zone, so e.g. 8:00 will be executed at 7:00 UTC for users in UTC+1 and 9:00 UTC for those in UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
Eğer %{day_of_week_setting_name} veya %{first_week_setting_name} seçeneklerinden biri ayarlanmışsa, ön uçta tutarsızlık yaşanmaması için diğer seçeneğin de ayarlanması gerekir.
@ -2488,8 +2487,8 @@ tr:
text_work_packages_ref_in_commit_messages:"İş paketlerini taahhüt mesajlarında referans ve sabitleme"
text_journal_added:"%{value} %{label} eklendi"
text_journal_aggregation_time_explanation:"Individual actions of a user (e.g. updating a work package twice) are aggregated into a single action if their age difference is less than the specified timespan. They will be displayed as a single action within the application. This will also delay notifications by the same amount of time reducing the number of emails being sent."
text_journal_changed:"%{label} %{old} -> <strong>%{new}</strong> olarak güncellendi"
text_journal_changed_plain:"%{label} %{old} den değiştirildi\n%{new} 'e"
text_journal_changed_html:"%{label} changed from %{old} %{linebreak}<strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} %{linebreak}to %{new}"
label_work_package_view_all:"Переглянути всі робочі пакети"
label_workflow:"Робочий процес"
@ -2443,6 +2441,7 @@ uk:
Set the number of days notification events for users (the source for in-app notifications) will be kept in the system. Any events older than this time will be deleted.
delay_minutes_explanation:"Email sending can be delayed to allow users with configured in app notification to confirm the notification within the application before a mail is sent out. Users who read a notification within the application will not receive an email for the already read notification."
email_digest_explanation:"Once a day, an email digest can be sent out containing a collection of all the notification users subscribed to. The setting is relative to each users configured time zone, so e.g. 8:00 will be executed at 7:00 UTC for users in UTC+1 and 9:00 UTC for those in UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
If either options "%{day_of_week_setting_name}" or "%{first_week_setting_name}" are set, the other has to be set as well to avoid inconsistencies in the frontend.
@ -2524,8 +2523,8 @@ uk:
text_work_packages_ref_in_commit_messages:"Посилання та фіксація робочих пакетів у повідомленнях комітів"
text_journal_added:"%{label} %{value} доданий"
text_journal_aggregation_time_explanation:"Individual actions of a user (e.g. updating a work package twice) are aggregated into a single action if their age difference is less than the specified timespan. They will be displayed as a single action within the application. This will also delay notifications by the same amount of time reducing the number of emails being sent."
text_journal_changed:"%{label} змінено з %{old} <br/><strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} змінено з %{old} в %{new}"
text_journal_changed_html:"%{label} changed from %{old} %{linebreak}<strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} %{linebreak}to %{new}"
error_enterprise_only:"is only available in the OpenProject Enterprise Edition"
error_unauthorized:"Có thể không được truy cập."
error_readonly:"was attempted to be written but is not writable."
email:"is not a valid email address."
empty:"không thể để trống"
even:"must be even."
exclusion:"được bảo lưu."
@ -702,6 +703,7 @@ vi:
not_start_date:"không phải ngày bắt đầu, mặc dù điều này là cần thiết cho các mốc quan trọng."
parent:
cannot_be_milestone:"không thể là một cột mốc."
cannot_be_self_assigned:"cannot be assigned to itself."
cannot_be_in_another_project:"không thể có trong một dự án khác."
not_a_valid_parent:"không hợp lệ"
start_date:
@ -1297,6 +1299,7 @@ vi:
expiration:"Hết hạn"
indefinite_expiration:"Không bao giờ"
notifications:
send_notifications:"Send notifications for this action"
work_packages:
subject:
created:"The work package was created."
@ -1433,6 +1436,7 @@ vi:
label_deleted:"đã xóa"
label_deleted_custom_field:"(đã xóa các mục tùy chỉnh)"
label_deleted_custom_option:"(tùy chọn đã xóa)"
label_missing_or_hidden_custom_option:"(missing value or lacking permissions to access)"
label_descending:"Giảm dần"
label_details:"Chi tiết"
label_development_roadmap:"Lộ trình phát triển"
@ -1606,7 +1610,6 @@ vi:
label_none_parentheses:"(trống)"
label_not_contains:"không chứa"
label_not_equals:"không là"
label_notify_member_plural:"Cập nhật thư"
label_on:"lúc"
label_open_menu:"Mở trình đơn"
label_open_work_packages:"mở"
@ -1726,7 +1729,6 @@ vi:
label_start_to_start:"bắt đầu đến bắt đầu"
label_statistics:"Số liệu thống kê"
label_status:"Trạng thái"
label_status_updated:"Tình trạng Work package đã cập nhật"
label_stay_logged_in:"Duy trì đăng nhập"
label_storage_free_space:"Dung lượng đĩa còn lại"
label_storage_used_space:"Dung lượng đĩa đã sử dụng"
@ -1810,21 +1812,17 @@ vi:
label_wiki_show_submenu_item:"Hiển thị dưới dạng mục menu con của"
label_wiki_start:"Trang bắt đầu"
label_work_package:"Work Package"
label_work_package_added:"Đã thêm work package"
label_work_package_attachments:"Phần đính kèm công việc"
label_work_package_category_new:"Danh mục mới"
label_work_package_category_plural:"Các thể loại work package"
label_work_package_hierarchy:"Phân cấp công việc"
label_work_package_new:"Work package mới"
label_work_package_note_added:"Đã thêm ghi chú của work package"
label_work_package_edit:"Chỉnh sửa work package %{name}"
label_work_package_plural:"Work Packages"
label_work_package_priority_updated:"Đã cập nhật độ ưu tiên của work package"
label_work_package_status:"Tình trạng work package"
label_work_package_status_new:"Trạng thái mới"
label_work_package_status_plural:"Tình trạng work package"
label_work_package_types:"Kiểu công việc"
label_work_package_updated:"đã cập nhật work package"
label_work_package_tracking:"Theo dõi work package"
label_work_package_view_all:"Xem tất cả các work package"
label_workflow:"Quy trình làm việc"
@ -2391,6 +2389,7 @@ vi:
Set the number of days notification events for users (the source for in-app notifications) will be kept in the system. Any events older than this time will be deleted.
delay_minutes_explanation:"Email sending can be delayed to allow users with configured in app notification to confirm the notification within the application before a mail is sent out. Users who read a notification within the application will not receive an email for the already read notification."
email_digest_explanation:"Once a day, an email digest can be sent out containing a collection of all the notification users subscribed to. The setting is relative to each users configured time zone, so e.g. 8:00 will be executed at 7:00 UTC for users in UTC+1 and 9:00 UTC for those in UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
If either options "%{day_of_week_setting_name}" or "%{first_week_setting_name}" are set, the other has to be set as well to avoid inconsistencies in the frontend.
@ -2472,8 +2471,8 @@ vi:
text_work_packages_ref_in_commit_messages:"Referencing and fixing work packages in commit messages"
text_journal_added:"%{label} %{value} added"
text_journal_aggregation_time_explanation:"Individual actions of a user (e.g. updating a work package twice) are aggregated into a single action if their age difference is less than the specified timespan. They will be displayed as a single action within the application. This will also delay notifications by the same amount of time reducing the number of emails being sent."
text_journal_changed:"%{label} được sửa từ %{old} <br/><strong>thành</strong> %{new}"
text_journal_changed_plain:"%{label} thay đổi %{old} thành %{new}"
text_journal_changed_html:"%{label} changed from %{old} %{linebreak}<strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} %{linebreak}to %{new}"
cannot_be_self_assigned:"cannot be assigned to itself."
cannot_be_in_another_project:"不能在另一个项目中。"
not_a_valid_parent:"是无效的。"
start_date:
@ -1291,6 +1293,7 @@ zh-CN:
expiration:"过期"
indefinite_expiration:"永不"
notifications:
send_notifications:"Send notifications for this action"
work_packages:
subject:
created:"The work package was created."
@ -1427,6 +1430,7 @@ zh-CN:
label_deleted:"已删除"
label_deleted_custom_field:"（删除自定义字段）"
label_deleted_custom_option:"（删除的选项）"
label_missing_or_hidden_custom_option:"(missing value or lacking permissions to access)"
label_descending:"降序"
label_details:"详细信息"
label_development_roadmap:"发展蓝图"
@ -1600,7 +1604,6 @@ zh-CN:
label_none_parentheses:"(无)"
label_not_contains:"不包含"
label_not_equals:"不是"
label_notify_member_plural:"电子邮件更新"
label_on:"于"
label_open_menu:"打开菜单"
label_open_work_packages:"打开"
@ -1720,7 +1723,6 @@ zh-CN:
label_start_to_start:"开始开始"
label_statistics:"统计数据"
label_status:"状态"
label_status_updated:"工作包状态更新"
label_stay_logged_in:"保持登录状态"
label_storage_free_space:"剩余磁盘空间"
label_storage_used_space:"已使用磁盘空间"
@ -1804,21 +1806,17 @@ zh-CN:
label_wiki_show_submenu_item:"显示为子菜单项"
label_wiki_start:"起始页"
label_work_package:"工作包"
label_work_package_added:"添加工作包"
label_work_package_attachments:"工作包附件"
label_work_package_category_new:"新的类别"
label_work_package_category_plural:"工作包类别"
label_work_package_hierarchy:"工作包的层次结构"
label_work_package_new:"新工作包"
label_work_package_note_added:"添加工作包注释"
label_work_package_edit:"编辑工作包 %{name}"
label_work_package_plural:"工作包"
label_work_package_priority_updated:"更新工作包优先级"
label_work_package_status:"工作包状态"
label_work_package_status_new:"新状态"
label_work_package_status_plural:"工作包状态"
label_work_package_types:"工作包类型"
label_work_package_updated:"工作包更新"
label_work_package_tracking:"工作包跟踪"
label_work_package_view_all:"查看所有工作包"
label_workflow:"工作流"
@ -2381,6 +2379,7 @@ zh-CN:
Set the number of days notification events for users (the source for in-app notifications) will be kept in the system. Any events older than this time will be deleted.
delay_minutes_explanation:"Email sending can be delayed to allow users with configured in app notification to confirm the notification within the application before a mail is sent out. Users who read a notification within the application will not receive an email for the already read notification."
email_digest_explanation:"Once a day, an email digest can be sent out containing a collection of all the notification users subscribed to. The setting is relative to each users configured time zone, so e.g. 8:00 will be executed at 7:00 UTC for users in UTC+1 and 9:00 UTC for those in UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
text_journal_aggregation_time_explanation:"Individual actions of a user (e.g. updating a work package twice) are aggregated into a single action if their age difference is less than the specified timespan. They will be displayed as a single action within the application. This will also delay notifications by the same amount of time reducing the number of emails being sent."
error_enterprise_only:"is only available in the OpenProject Enterprise Edition"
error_unauthorized:"無法被存取。"
error_readonly:"被嘗試寫入但是無法寫入。"
email:"is not a valid email address."
empty:"不可為空"
even:"必須是偶數"
exclusion:"已保留"
@ -700,6 +701,7 @@ zh-TW:
not_start_date:"不在開始的日期，儘管它是里程碑所必需的。"
parent:
cannot_be_milestone:"不可以成為一個里程碑"
cannot_be_self_assigned:"cannot be assigned to itself."
cannot_be_in_another_project:"不可以存在於另外一個專案中"
not_a_valid_parent:"不正確。"
start_date:
@ -1295,6 +1297,7 @@ zh-TW:
expiration:"過期"
indefinite_expiration:"永不"
notifications:
send_notifications:"Send notifications for this action"
work_packages:
subject:
created:"The work package was created."
@ -1431,6 +1434,7 @@ zh-TW:
label_deleted:"刪除線"
label_deleted_custom_field:"(已刪除的自訂欄位)"
label_deleted_custom_option:"(deleted option)"
label_missing_or_hidden_custom_option:"(missing value or lacking permissions to access)"
label_descending:"降冪"
label_details:"詳細資料"
label_development_roadmap:"發展路徑圖"
@ -1604,7 +1608,6 @@ zh-TW:
label_none_parentheses:"（無）"
label_not_contains:"不包含"
label_not_equals:"不是"
label_notify_member_plural:"電子郵件通知"
label_on:"開啟"
label_open_menu:"開啟選單"
label_open_work_packages:"打開"
@ -1724,7 +1727,6 @@ zh-TW:
label_start_to_start:"開始到開始"
label_statistics:"統計"
label_status:"狀態"
label_status_updated:"工作項目狀態已更新"
label_stay_logged_in:"保持登入"
label_storage_free_space:"剩餘磁碟空間"
label_storage_used_space:"已用磁碟空間"
@ -1808,21 +1810,17 @@ zh-TW:
label_wiki_show_submenu_item:"呈現於子功能表的 "
label_wiki_start:"開始頁面"
label_work_package:"工作項目"
label_work_package_added:"工作項目已新增"
label_work_package_attachments:"工作項目附件"
label_work_package_category_new:"新增類別"
label_work_package_category_plural:"工作項目類別"
label_work_package_hierarchy:"工作包層次結構"
label_work_package_new:"新增工作項目"
label_work_package_note_added:"工作項目註記已新增"
label_work_package_edit:"編輯工作項目 %{name}"
label_work_package_plural:"工作項目"
label_work_package_priority_updated:"工作項目優先等級已更新"
label_work_package_status:"工作項目狀態"
label_work_package_status_new:"新狀態"
label_work_package_status_plural:"工作項目狀態"
label_work_package_types:"工作項目類型"
label_work_package_updated:"工作項目已更新"
label_work_package_tracking:"工作項目追蹤"
label_work_package_view_all:"檢視所有工作項目"
label_workflow:"工作流程"
@ -2388,6 +2386,7 @@ zh-TW:
Set the number of days notification events for users (the source for in-app notifications) will be kept in the system. Any events older than this time will be deleted.
delay_minutes_explanation:"Email sending can be delayed to allow users with configured in app notification to confirm the notification within the application before a mail is sent out. Users who read a notification within the application will not receive an email for the already read notification."
email_digest_explanation:"Once a day, an email digest can be sent out containing a collection of all the notification users subscribed to. The setting is relative to each users configured time zone, so e.g. 8:00 will be executed at 7:00 UTC for users in UTC+1 and 9:00 UTC for those in UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
If either options "%{day_of_week_setting_name}" or "%{first_week_setting_name}" are set, the other has to be set as well to avoid inconsistencies in the frontend.
text_journal_aggregation_time_explanation:"Individual actions of a user (e.g. updating a work package twice) are aggregated into a single action if their age difference is less than the specified timespan. They will be displayed as a single action within the application. This will also delay notifications by the same amount of time reducing the number of emails being sent."
label_work_package_view_all:"View all work packages"
label_workflow:"Workflow"
@ -2510,6 +2508,7 @@ en:
will be kept in the system. Any events older than this time will be deleted.
delay_minutes_explanation:"Email sending can be delayed to allow users with configured in app notification to confirm the notification within the application before a mail is sent out. Users who read a notification within the application will not receive an email for the already read notification."
email_digest_explanation:"Once a day, an email digest can be sent out containing a collection of all the notification users subscribed to. The setting is relative to each users configured time zone, so e.g. 8:00 will be executed at 7:00 UTC for users in UTC+1 and 9:00 UTC for those in UTC-1."
events_explanation:'Governs for which event an email is sent out. Work packages are excluded from this list as the notifications for them can be configured specifically for every user.'
display:
first_date_of_week_and_year_set:>
If either options "%{day_of_week_setting_name}" or "%{first_week_setting_name}" are set,
@ -2608,8 +2607,8 @@ en:
text_work_packages_ref_in_commit_messages:"Referencing and fixing work packages in commit messages"
text_journal_added:"%{label} %{value} added"
text_journal_aggregation_time_explanation:"Individual actions of a user (e.g. updating a work package twice) are aggregated into a single action if their age difference is less than the specified timespan. They will be displayed as a single action within the application. This will also delay notifications by the same amount of time reducing the number of emails being sent."
text_journal_changed:"%{label} changed from %{old} <br/><strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} \nto %{new}"
text_journal_changed_html:"%{label} changed from %{old} %{linebreak}<strong>to</strong> %{new}"
text_journal_changed_plain:"%{label} changed from %{old} %{linebreak}to %{new}"
wiki:'Within the <b>wiki</b> you can document and share knowledge together with your team.'
backlogs:
overview:"Manage your work in the <b>backlogs</b> view."
sprints:"On the right you have the product backlog or a bug backlog, on the left you will have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag and drop and add them to a sprint."
sprints:"On the right you have the product backlog and the bug backlog, on the left you have the respective sprints. Here you can create <b>epics, user stories, and bugs</b>, prioritize via drag drop and add them to a sprint."
task_board_arrow:'To see your <b>task board</b>, open the sprint drop-down...'
task_board_select:'...and select the <b>task board</b> entry.'
task_board:"The task board visualizes the <b>progress for this sprint</b>. Click on the plus (+) icon next to a user story to add new tasks or impediments. <br> The status can be updated by drag and drop."
@ -582,6 +582,11 @@ en:
involved:'I am involved'
mentioned:'I was mentioned'
watched:'I am watching'
work_package_commented:'Work package commented'
work_package_created:'Work package created'
work_package_processed:'Work package status changed'
description: Overview of the OpenProject documentation
robots: index, follow
keywords: contribution, documentation, documentation process
---
# Contribute to the OpenProject documentation
## What does the OpenProject documentation entail?
The OpenProject documentation makes available user guides, system admin, installation and operation, API as well as development guides and release notes.
Current and future users of the application find instructions for the set up and configuration of OpenProject in the documentation. Furthermore, it contains use cases and usage instructions for all OpenProject features and the use of OpenProject with other applications.
This documentation evolves continuously with new features and improvements to achieve clarity, accuracy, and completeness.
## Where to find the OpenProject documentation?
The documentation for OpenProject is published on https://www.openproject.org/docs/. You can also access the documentation from your OpenProject application under user guides and API documentation below the question mark at the top right in the header menu.
## Who can contribute to the documentation?
Being proudly open source, we invite anyone in our community to contribute to our software as well as the documentation to improve it even further.
## What can you contribute to the documentation?
Documentation improvements and changes apply to the documentation described in the section above. Documentation changes are **not** changes or additions to the code of the OpenProject application. For contributions to the code, see our [product development guide](../product-development-handbook/#openproject-product-development-handbook).
We are looking forward to receiving the following contributions from you:
- Eliminating errors and working on other improvements in the existing documentation. This could be missing content, e.g. descriptions or step-by-step guides for features.
- Adding use cases.
- Adding visuals, e.g. screenshots, to complement descriptions.
- Fixing of spelling, grammar, punctuation mistakes.
- Fixing of internal and external links that are not working or are incorrect.
- Translations into your mother tongue (coming soon).
| [Documentation process](documentation-process) | A step-by-step guide on how to contribute to the documentation. |
| [Documentation style guide](documentation-style-guide) | What are the styles and other requirements to follow when contributing to the documentation? |
| [Contribution support](contribution-support) | What to do if you need help regarding your contribution to the documentation? |
With this guide for contributing to the OpenProject documentation we followed and took inspiration from the [Contribute to GitLab guide](https://about.gitlab.com/community/contribute/).
If you have any questions on the contribution process or encounter problems with your contribution to the OpenProject documentation, please open a ticket. We will then get in touch with you via the ticket.
1. Login to or register at the [OpenProject community platform](https://community.openproject.org/login). It’s fast and free.
2. Open a new [documentation work package]( https://community.openproject.org/projects/openproject/work_packages/new?type=69).
3. Add a precise subject.
4. Add a detailed description about your issue and how we could help.
5. Attach a screen-shot or log-file (optional).
6. Press **Save**.
Some files were not shown because too many files have changed in this diff
Show More
Behrokh Satarnejad
3 years ago
committed by
GitHub