@activepieces/piece-jira-cloud 0.3.3 → 0.3.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,12 +1,12 @@
1
1
  {
2
2
  "name": "@activepieces/piece-jira-cloud",
3
- "version": "0.3.3",
3
+ "version": "0.3.4",
4
4
  "main": "./src/index.js",
5
5
  "types": "./src/index.d.ts",
6
6
  "dependencies": {
7
7
  "@activepieces/pieces-common": "0.12.3",
8
- "@activepieces/pieces-framework": "0.28.0",
9
- "@activepieces/shared": "0.67.1",
8
+ "@activepieces/pieces-framework": "0.29.0",
9
+ "@activepieces/shared": "0.82.0",
10
10
  "@atlaskit/adf-schema": "50.4.0",
11
11
  "@atlaskit/editor-json-transformer": "8.27.2",
12
12
  "@atlaskit/editor-markdown-transformer": "5.16.6",
package/src/i18n/de.json CHANGED
@@ -22,6 +22,7 @@
22
22
  "Delete Issue Comment": "Ticket-Kommentar löschen",
23
23
  "Markdown to Jira format": "Markdown zum Jira-Format",
24
24
  "Get Issue": "Problem abrufen",
25
+ "Transition Issue": "Übergangsproblem",
25
26
  "Custom API Call": "Eigener API-Aufruf",
26
27
  "Creates a new issue in a project.": "Erstellt ein neues Problem in einem Projekt.",
27
28
  "Updates an existing issue.": "Aktualisiert ein existierendes Problem.",
@@ -38,6 +39,7 @@
38
39
  "Deletes a comment on a specific issue.": "Löscht einen Kommentar zu einem bestimmten Thema.",
39
40
  "Convert Markdown-formatted text to Jira's ADF syntax for use in comments and descriptions etc": "Konvertieren Sie Markdown-formatierten Text in Jiras ADF-Syntax für Kommentare und Beschreibungen usw.",
40
41
  "Get issue data.": "Ticket-Daten abrufen.",
42
+ "Moves an issue to a new status by executing a workflow transition.": "Verschiebt ein Problem auf einen neuen Status, indem ein Workflow-Übergang ausgeführt wird.",
41
43
  "Make a custom API call to a specific endpoint": "Einen benutzerdefinierten API-Aufruf an einen bestimmten Endpunkt machen",
42
44
  "Project ID or Key": "Projekt-ID oder Schlüssel",
43
45
  "Issue Type": "Ticket-Typ",
@@ -46,7 +48,10 @@
46
48
  "Issue ID or Key": "Ticket-ID oder Schlüssel",
47
49
  "Status": "Status",
48
50
  "Keyword": "Keyword",
51
+ "Markdown": "Markdown",
49
52
  "JQL": "JQL",
53
+ "Fields to Return": "Felder zum Zurückgeben",
54
+ "Map Field Names": "Kartenfeldnamen",
50
55
  "Max Results": "Maximale Ergebnisse",
51
56
  "Sanitize JQL": "JQL sanitizen",
52
57
  "Assignee": "Assignee",
@@ -63,8 +68,8 @@
63
68
  "Limit": "Limit",
64
69
  "Markdown text": "Markdown Text",
65
70
  "Expand": "Erweitern",
66
- "Map Field Names": "Kartenfeldnamen",
67
71
  "Map Transition Names": "Kartenübergangsnamen",
72
+ "Transition": "Übergang",
68
73
  "Method": "Methode",
69
74
  "Headers": "Kopfzeilen",
70
75
  "Query Parameters": "Abfrageparameter",
@@ -75,7 +80,10 @@
75
80
  "Timeout (in seconds)": "Timeout (in Sekunden)",
76
81
  "Follow redirects": "Weiterleitungen folgen",
77
82
  "https://developer.atlassian.com/cloud/jira/platform/apis/document/structure": "https://developer.atlassian.com/cloud/jira/platform/apis/document/structure",
78
- "The JQL query to use in the search": "Die JQL-Abfrage für die Suche",
83
+ "Fetching a large number of issues without specifying **Fields to Return** may exceed your flow's memory limits. Use field selection to reduce payload size.": "Das Abrufen einer großen Anzahl von Problemen ohne Angabe von **Fields to Return** kann die Speichergrenze deines Fusses überschreiten. Benutze die Feldauswahl um die Payload-Größe zu reduzieren.",
84
+ "The JQL query to use in search (Tip: Use single quotes for strings/dates)": "Die JQL-Abfrage für die Suche (Tipp: Benutze einfache Anführungszeichen für Zeichenketten/Datum)",
85
+ "List of exact Jira Field IDs to return (e.g., 'summary', 'customfield_10016').\nSpecial commands:\n- Use *all for every field.\n- Use *navigable for standard fields (default).\n- Prefix with a minus to exclude (e.g., -description).\nExample: *all and -comment returns everything except comments.": "Liste der exakten Jira-Feld-IDs, die zurückgegeben werden sollen (z.B. 'summary', 'customfield_10016').\nSpezielle Befehle:\n- Verwenden Sie *alle für jedes Feld.\n- *navigierbar für Standardfelder verwenden (Standard).\n- Präfix mit einem Minus zum Ausschalten (e.\nBeispiel: *All and -comment returns everything except comments.",
86
+ "Map human readable names to Fields in the output.\nNotes:\n- If there are fields with the same name, they may be overridden.": "Map human readable names to Fields in the output.\n:\n- If there are fields with the same name, they may be overridden.",
79
87
  "Maximum number of results": "Maximale Anzahl der Ergebnisse",
80
88
  "Include additional information about the issue in the response": "Fügen Sie zusätzliche Informationen über das Problem in die Antwort ein",
81
89
  "Map human readable names to Fields, Rendered Fields, Schema and Edit Meta.\nNotes:\n- This would implicitly add \"names\" to the expand field\n- If there are fields with the same name, they may be overridden": "Ordnen Sie Namen zu Feldern, gerenderten Feldern, Schema und Bearbeiten von Meta zu.\nAnmerkungen:\n- Dies würde implizit \"Names\" in das Feld\nhinzufügen - Wenn es Felder mit dem gleichen Namen gibt sie können überschrieben werden",
@@ -103,8 +111,24 @@
103
111
  "New Issue": "Neuer Fall",
104
112
  "Updated Issue": "Aktualisierter Fall",
105
113
  "Updated Issue Status": "Aktualisierter Ticket Status",
114
+ "New Comment": "Neuer Kommentar",
115
+ "Issue Assigned": "Ticket zugewiesen",
116
+ "New Attachment on Issue": "Neuer Anhang im Fall",
106
117
  "Triggers when a new issue is created": "Wird ausgelöst, wenn ein neues Problem erstellt wird",
107
118
  "Triggers when an issue is updated": "Wird ausgelöst, wenn ein Problem aktualisiert wird",
108
119
  "Triggers when an issue status is updated": "Wird ausgelöst, wenn ein Ticket Status aktualisiert wird",
109
- "Use to filter issues watched": "Verwende es, um beobachtete Probleme zu filtern"
120
+ "Fires whenever someone adds a new comment to a Jira issue. Great for getting notified in Slack or Teams, syncing customer replies, or reacting to feedback automatically.": "Feuer, wenn jemand einen neuen Kommentar zu einem Jira-Problem hinzufügt. Ideal um in Slack oder Teams benachrichtigt zu werden, Kundenantworten zu synchronisieren oder automatisch auf Feedback zu reagieren.",
121
+ "Fires when a Jira issue is assigned to someone. Use it to ping people in Slack/Teams the moment work lands on them, auto-create a to-do when tickets hit your queue, or track hand-offs between teammates.": "Feuer, wenn eine Jira-Ausgabe einer Person zugewiesen wird. Benutze es um Leute in Slack/Teams zu pingen automatisches Erstellen eines To-Dos, wenn Tickets auf Ihre Warteschlange drücken oder Hand-Offs zwischen Teammitgliedern verfolgen.",
122
+ "Fires when a file is attached to a Jira issue. Great for auto-saving screenshots to Google Drive, forwarding customer uploads to support tools, or archiving documents in S3.": "Feuer, wenn eine Datei an ein Jira-Problem angehängt wird. Hervorragend für automatisches Speichern von Screenshots in Google Drive, Weiterleitung von Kunden-Uploads an Unterstützungswerkzeuge oder Archivieren von Dokumenten in S3.",
123
+ "Only watch these issues (optional)": "Nur diese Fälle beobachten (optional)",
124
+ "Auto-fix the filter": "Filter automatisch reparieren",
125
+ "Only when assigned to me": "Nur wenn mir zugewiesen",
126
+ "Assignee (optional)": "Beauftragter (optional)",
127
+ "Use to filter issues watched": "Verwende es, um beobachtete Probleme zu filtern",
128
+ "Leave empty to watch comments on **every** issue in your Jira.\n\nTo narrow it down, paste a Jira filter here. A few ready-to-use examples:\n\n- `project = \"SUPPORT\"` — only issues in the Support project\n- `assignee = currentUser()` — only issues assigned to you\n- `status != Done` — skip closed issues\n- `labels = \"vip\"` — only issues tagged `vip`\n- `project = \"SUPPORT\" AND priority = High` — combine conditions with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build the filter visually, ": "Lassen Sie leer, um Kommentare zu **allen** Thema in Ihrem Jira zu sehen.\n\nUm es einzugrenzen, fügen Sie hier einen Jira-Filter ein. Ein paar einsatzbereite Beispiele:\n\n- `project = \"SUPPORT\"` — nur Probleme im Support-Projekt\n- `assignee = currentUser()` — nur Probleme, die dir\n- `status zugewiesen sind! Done` — geschlossene Tickets\n- `labels = \"vip\"` — nur Tickets mit dem Tag `vip`\n- `project = \"SUPPORT\" AND priority = High` — kombinieren Sie Bedingungen mit `AND`\n\nNicht sicher was Sie schreiben sollen? Öffnen Sie Jira → Filter → Erweiterte Suche, erstellen Sie den Filter visuell, dann kopieren Sie die Abfrage hierher.",
129
+ "Keep this on. If your filter references something you can't access (a private project, a deleted field), Jira will automatically clean it up instead of erroring.": "Daran festhalten. Wenn Ihr Filter auf etwas verweist, auf das Sie nicht zugreifen können (ein privates Projekt, ein gelöschtes Feld) wird Jira es automatisch bereinigen, anstatt Fehler zu beheben.",
130
+ "Only trigger when the issue is assigned to the user who set up this connection. Overrides the Assignee field below.": "Wird nur ausgelöst, wenn das Problem dem Benutzer zugewiesen wird, der diese Verbindung eingerichtet hat. Überschreibt das Feld \"Zuweisend\" unten.",
131
+ "Pick a teammate to watch. Leave empty to trigger on assignments to anyone. Ignored if \"Only when assigned to me\" is checked.": "Wähle einen Teamkollegen zum Beobachten. Leer lassen um Aufträge für jeden auszulösen. Ignoriert, wenn \"Nur wenn mir zugewiesen\" ausgewählt ist.",
132
+ "Narrow down which issues to watch. Leave empty to watch every issue in your Jira.\n\nReady-to-use examples:\n\n- `project = \"SUPPORT\"` — only the Support project\n- `priority = High` — only high-priority issues\n- `labels = \"vip\"` — only issues tagged `vip`\n- `project = \"SUPPORT\" AND status != Done` — combine with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build a filter visually, then copy the query here.": "Beschneiden, welche Probleme beobachtet werden sollen. Lassen Sie leer, um jeden Fall in Ihrem Jira zu beobachten.\n\nReady-to-use examples:\n\n- `project = \"SUPPORT\"` — nur das Supportprojekt\n- `priority = High` — nur Probleme mit hoher Priorität\n- `labels = \"vip\"` — nur Probleme mit dem Namen `vip`\n- `project = \"SUPPORT\" UND Status ! Done` — kombinieren Sie mit `AND`\n\nNicht sicher, was Sie schreiben sollen? Öffnen Sie Jira → Filter → Erweiterte Suche, erstellen Sie einen Filter visuell, dann kopieren Sie die Abfrage hier.",
133
+ "Narrow down which issues to watch. Leave empty to watch every issue in your Jira.\n\nReady-to-use examples:\n\n- `project = \"SUPPORT\"` — only the Support project\n- `issuetype = Bug` — only bugs\n- `labels = \"screenshot-needed\"` — only issues tagged `screenshot-needed`\n- `project = \"SUPPORT\" AND status != Done` — combine with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build a filter visually, then copy the query here.": "Beschneiden, welche Probleme beobachtet werden sollen. Lassen Sie leer, um jeden Fall in Ihrem Jira zu beobachten.\n\nReady-to-use examples:\n\n- `project = \"SUPPORT\"` — nur das Supportprojekt\n- `issuetype = Bug` — nur Bugs\n- `labels = \"screenshot-needed\"` — es wurden nur `screenshot-needed`\n- `project = \"SUPPORT\" UND Status markiert! Done` — kombinieren Sie mit `AND`\n\nNicht sicher, was Sie schreiben sollen? Öffnen Sie Jira → Filter → Erweiterte Suche, erstellen Sie einen Filter visuell, dann kopieren Sie die Abfrage hier."
110
134
  }
package/src/i18n/es.json CHANGED
@@ -22,6 +22,7 @@
22
22
  "Delete Issue Comment": "Eliminar Comentario del Problema",
23
23
  "Markdown to Jira format": "Formato Markdown a Jira",
24
24
  "Get Issue": "Obtener problema",
25
+ "Transition Issue": "Problema de transición",
25
26
  "Custom API Call": "Llamada API personalizada",
26
27
  "Creates a new issue in a project.": "Crea un nuevo asunto en un proyecto.",
27
28
  "Updates an existing issue.": "Actualiza un problema existente.",
@@ -38,6 +39,7 @@
38
39
  "Deletes a comment on a specific issue.": "Elimina un comentario sobre un asunto específico.",
39
40
  "Convert Markdown-formatted text to Jira's ADF syntax for use in comments and descriptions etc": "Convierte el texto con formato Markdown a la sintaxis ADF de Jira para usarlo en comentarios y descripciones, etc.",
40
41
  "Get issue data.": "Obtener datos del problema.",
42
+ "Moves an issue to a new status by executing a workflow transition.": "Mueve un problema a un nuevo estado ejecutando una transición de flujo de trabajo.",
41
43
  "Make a custom API call to a specific endpoint": "Hacer una llamada API personalizada a un extremo específico",
42
44
  "Project ID or Key": "ID o clave del proyecto",
43
45
  "Issue Type": "Tipo de asunto",
@@ -46,7 +48,10 @@
46
48
  "Issue ID or Key": "Emitir ID o Clave",
47
49
  "Status": "Estado",
48
50
  "Keyword": "Keyword",
51
+ "Markdown": "Markdown",
49
52
  "JQL": "JQL",
53
+ "Fields to Return": "Campos a devolver",
54
+ "Map Field Names": "Mapa de nombres de campos",
50
55
  "Max Results": "Resultados máximos",
51
56
  "Sanitize JQL": "Sanitizar JQL",
52
57
  "Assignee": "Assignee",
@@ -63,8 +68,8 @@
63
68
  "Limit": "Límite",
64
69
  "Markdown text": "Texto Markdown",
65
70
  "Expand": "Expandir",
66
- "Map Field Names": "Mapa de nombres de campos",
67
71
  "Map Transition Names": "Mapear nombres de transición",
72
+ "Transition": "Transición",
68
73
  "Method": "Método",
69
74
  "Headers": "Encabezados",
70
75
  "Query Parameters": "Parámetros de consulta",
@@ -75,7 +80,10 @@
75
80
  "Timeout (in seconds)": "Tiempo de espera (en segundos)",
76
81
  "Follow redirects": "Seguir redirecciones",
77
82
  "https://developer.atlassian.com/cloud/jira/platform/apis/document/structure": "https://developer.atlassian.com/cloud/jira/platform/apis/document/structure",
78
- "The JQL query to use in the search": "La consulta JQL a usar en la búsqueda",
83
+ "Fetching a large number of issues without specifying **Fields to Return** may exceed your flow's memory limits. Use field selection to reduce payload size.": "Obtener un gran número de problemas sin especificar **Campos a Retorno** puede exceder los límites de memoria de tu flujo. Usa la selección de campo para reducir el tamaño de la carga útil.",
84
+ "The JQL query to use in search (Tip: Use single quotes for strings/dates)": "La consulta JQL a usar en la búsqueda (Consejo: Usar comillas simples para cadenas/fechas)",
85
+ "List of exact Jira Field IDs to return (e.g., 'summary', 'customfield_10016').\nSpecial commands:\n- Use *all for every field.\n- Use *navigable for standard fields (default).\n- Prefix with a minus to exclude (e.g., -description).\nExample: *all and -comment returns everything except comments.": "List of exact Jira Field IDs to return (e.g., 'summary', 'customfield_10016').\nSpecial commands:\n- Use *all for every field.\n- Use *navigable for standard fields (default).\n- Prefix with a minus to exclude (e.g., -description).\nExample: *all and -comment returns everything except comments.",
86
+ "Map human readable names to Fields in the output.\nNotes:\n- If there are fields with the same name, they may be overridden.": "Mapear nombres legibles a campos en la salida.\nNotas:\n- Si hay campos con el mismo nombre, pueden ser anulados.",
79
87
  "Maximum number of results": "Número máximo de resultados",
80
88
  "Include additional information about the issue in the response": "Incluye información adicional sobre el problema en la respuesta",
81
89
  "Map human readable names to Fields, Rendered Fields, Schema and Edit Meta.\nNotes:\n- This would implicitly add \"names\" to the expand field\n- If there are fields with the same name, they may be overridden": "Mapea nombres humanos legibles a Campos, Campos Renderizados, Esquema y Editar Meta.\nhabitación:\n- This would implicitly add \"names\" to the expand field\n- If there are fields with the same name, pueden ser anulados",
@@ -103,8 +111,24 @@
103
111
  "New Issue": "Nuevo problema",
104
112
  "Updated Issue": "Problema actualizado",
105
113
  "Updated Issue Status": "Estado del asunto actualizado",
114
+ "New Comment": "Nuevo comentario",
115
+ "Issue Assigned": "Petición asignada",
116
+ "New Attachment on Issue": "Nuevo adjunto en el problema",
106
117
  "Triggers when a new issue is created": "Desencadena cuando se crea un nuevo problema",
107
118
  "Triggers when an issue is updated": "Dispara cuando se actualiza un problema",
108
119
  "Triggers when an issue status is updated": "Dispara cuando se actualiza el estado de una incidencia",
109
- "Use to filter issues watched": "Utilizar para filtrar problemas vistos"
120
+ "Fires whenever someone adds a new comment to a Jira issue. Great for getting notified in Slack or Teams, syncing customer replies, or reacting to feedback automatically.": "Dispara cada vez que alguien agrega un nuevo comentario a una edición de Jira. Ideal para ser notificado en Slack o equipos, sincronizando respuestas de los clientes o reaccionando a comentarios automáticamente.",
121
+ "Fires when a Jira issue is assigned to someone. Use it to ping people in Slack/Teams the moment work lands on them, auto-create a to-do when tickets hit your queue, or track hand-offs between teammates.": "Dispara cuando una incidencia de Jira es asignada a alguien. Úsalo para hacer ping a la gente en Slack/Equipos en el momento en que trabaje sobre ellos, crear auto-hacer cuando los tickets golpean la cola, o rastrear las manos entre compañeros de equipo.",
122
+ "Fires when a file is attached to a Jira issue. Great for auto-saving screenshots to Google Drive, forwarding customer uploads to support tools, or archiving documents in S3.": "Dispara cuando un archivo está adjunto a un problema de Jira. Ideal para guardar automáticamente las capturas de pantalla a Google Drive, reenviar las cargas de los clientes para apoyar herramientas o archivar documentos en S3.",
123
+ "Only watch these issues (optional)": "Sólo ver estos problemas (opcional)",
124
+ "Auto-fix the filter": "Autocorregir el filtro",
125
+ "Only when assigned to me": "Sólo cuando se me asigna",
126
+ "Assignee (optional)": "Asignado (opcional)",
127
+ "Use to filter issues watched": "Utilizar para filtrar problemas vistos",
128
+ "Leave empty to watch comments on **every** issue in your Jira.\n\nTo narrow it down, paste a Jira filter here. A few ready-to-use examples:\n\n- `project = \"SUPPORT\"` — only issues in the Support project\n- `assignee = currentUser()` — only issues assigned to you\n- `status != Done` — skip closed issues\n- `labels = \"vip\"` — only issues tagged `vip`\n- `project = \"SUPPORT\" AND priority = High` — combine conditions with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build the filter visually, ": "Deja vacío para ver comentarios sobre **cada** problema en tu Jira.\n\nPara reducirlo, pega un filtro de Jira aquí. Algunos ejemplos listos para usar:\n\n- `project = \"SUPPORT\"` — sólo problemas en el proyecto de Soporte\n- `assignee = currentUser()` — sólo asuntos asignados a usted\n- `status ! Done` — omitir asuntos cerrados\n- `labels = \"vip\"` — sólo asuntos etiquetados `vip`\n- `project = \"SUPPORT\" AND priority = High` — combinar condiciones con `AND`\n\n¿No está seguro de qué escribir? Abra Jira → Filtros → Búsqueda avanzada, construya el filtro visualmente, luego copie la consulta aquí.",
129
+ "Keep this on. If your filter references something you can't access (a private project, a deleted field), Jira will automatically clean it up instead of erroring.": "Mantenga esto encendido. Si su filtro hace referencia a algo a lo que no puede acceder (un proyecto privado, un campo eliminado), Jira lo limpiará automáticamente en lugar de realizar un error.",
130
+ "Only trigger when the issue is assigned to the user who set up this connection. Overrides the Assignee field below.": "Sólo se activa cuando el problema está asignado al usuario que configuró esta conexión. Reemplaza el campo Asignado a continuación.",
131
+ "Pick a teammate to watch. Leave empty to trigger on assignments to anyone. Ignored if \"Only when assigned to me\" is checked.": "Escoge un compañero de equipo para ver. Déjalo vacío para activarlo en las asignaciones a cualquiera. Ignorado si \"Sólo cuando se me asigna\" está marcado.",
132
+ "Narrow down which issues to watch. Leave empty to watch every issue in your Jira.\n\nReady-to-use examples:\n\n- `project = \"SUPPORT\"` — only the Support project\n- `priority = High` — only high-priority issues\n- `labels = \"vip\"` — only issues tagged `vip`\n- `project = \"SUPPORT\" AND status != Done` — combine with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build a filter visually, then copy the query here.": "Narrow down which issues to watch. Leave empty to watch every issue in your Jira.\n\nReady-to-use examples:\n\n- `project = \"SUPPORT\"` — only the Support project\n- `priority = High` — only high-priority issues\n- `labels = \"vip\"` — only issues tagged `vip`\n- `project = \"SUPPORT\" AND status != Done` — combine with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build a filter visually, then copy the query here.",
133
+ "Narrow down which issues to watch. Leave empty to watch every issue in your Jira.\n\nReady-to-use examples:\n\n- `project = \"SUPPORT\"` — only the Support project\n- `issuetype = Bug` — only bugs\n- `labels = \"screenshot-needed\"` — only issues tagged `screenshot-needed`\n- `project = \"SUPPORT\" AND status != Done` — combine with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build a filter visually, then copy the query here.": "Desplácese hacia abajo que problemas observar. Deje vacío para ver todos los problemas de su Jira.\n\nEjemplos listos para usar:\n\n- `project = \"SUPPORT\"` — sólo el proyecto de soporte\n- `issuetype = Bug` — solo bugs\n- `labels = \"screenshot-needed\"` — solo emite `screenshot-needed`\n- `project = \"SUPPORT\" AND status ! Hecho` — combinar con `AND`\n\n¿No estás seguro de qué escribir? Abra Jira → Filtros → Búsqueda avanzada, construya un filtro visualmente, luego copie la consulta aquí."
110
134
  }
package/src/i18n/fr.json CHANGED
@@ -22,6 +22,7 @@
22
22
  "Delete Issue Comment": "Supprimer le commentaire du problème",
23
23
  "Markdown to Jira format": "Format Markdown vers Jira",
24
24
  "Get Issue": "Obtenir un problème",
25
+ "Transition Issue": "Problème de transition",
25
26
  "Custom API Call": "Appel API personnalisé",
26
27
  "Creates a new issue in a project.": "Crée un nouveau ticket dans un projet.",
27
28
  "Updates an existing issue.": "Met à jour un ticket existant.",
@@ -38,6 +39,7 @@
38
39
  "Deletes a comment on a specific issue.": "Supprime un commentaire sur un problème spécifique.",
39
40
  "Convert Markdown-formatted text to Jira's ADF syntax for use in comments and descriptions etc": "Convertir le texte formaté par Markdown en syntaxe ADF de Jira pour l'utiliser dans les commentaires et descriptions etc",
40
41
  "Get issue data.": "Récupérer les données du ticket.",
42
+ "Moves an issue to a new status by executing a workflow transition.": "Déplace un ticket vers un nouveau statut en exécutant une transition de workflow.",
41
43
  "Make a custom API call to a specific endpoint": "Passez un appel API personnalisé à un point de terminaison spécifique",
42
44
  "Project ID or Key": "ID ou clé du projet",
43
45
  "Issue Type": "Type de problème",
@@ -46,7 +48,10 @@
46
48
  "Issue ID or Key": "ID du ticket ou clé",
47
49
  "Status": "Statut",
48
50
  "Keyword": "Keyword",
51
+ "Markdown": "Markdown",
49
52
  "JQL": "JQL",
53
+ "Fields to Return": "Champs à retourner",
54
+ "Map Field Names": "Noms des champs de la carte",
50
55
  "Max Results": "Nombre maximum de résultats",
51
56
  "Sanitize JQL": "Assainissement JQL",
52
57
  "Assignee": "Assignee",
@@ -63,8 +68,8 @@
63
68
  "Limit": "Limite",
64
69
  "Markdown text": "Texte Markdown",
65
70
  "Expand": "Agrandir",
66
- "Map Field Names": "Noms des champs de la carte",
67
71
  "Map Transition Names": "Noms de transition de la carte",
72
+ "Transition": "Transition",
68
73
  "Method": "Méthode",
69
74
  "Headers": "En-têtes",
70
75
  "Query Parameters": "Paramètres de requête",
@@ -75,7 +80,10 @@
75
80
  "Timeout (in seconds)": "Délai d'attente (en secondes)",
76
81
  "Follow redirects": "Suivre les redirections",
77
82
  "https://developer.atlassian.com/cloud/jira/platform/apis/document/structure": "https://developer.atlassian.com/cloud/jira/platform/apis/document/structure",
78
- "The JQL query to use in the search": "La requête JQL à utiliser dans la recherche",
83
+ "Fetching a large number of issues without specifying **Fields to Return** may exceed your flow's memory limits. Use field selection to reduce payload size.": "Récupérer un grand nombre de problèmes sans spécifier **Fields to Return** peut dépasser les limites de mémoire de votre flux. Utilisez la sélection de champ pour réduire la taille de la charge utile.",
84
+ "The JQL query to use in search (Tip: Use single quotes for strings/dates)": "La requête JQL à utiliser dans la recherche (Astuce: Utiliser des guillemets simples pour les chaînes/dates)",
85
+ "List of exact Jira Field IDs to return (e.g., 'summary', 'customfield_10016').\nSpecial commands:\n- Use *all for every field.\n- Use *navigable for standard fields (default).\n- Prefix with a minus to exclude (e.g., -description).\nExample: *all and -comment returns everything except comments.": "List of exact Jira Field IDs to return (e.g., 'summary', 'customfield_10016').\nSpecial commands:\n- Use *all for every field.\n- Use *navigable for standard fields (default).\n- Prefix with a minus to exclude (e.g., -description).\nExample: *all and -comment returns everything except comments.",
86
+ "Map human readable names to Fields in the output.\nNotes:\n- If there are fields with the same name, they may be overridden.": "Map human readable names to Fields in the output.\nNotes:\n- If there are fields with the same name, they may be overridden.",
79
87
  "Maximum number of results": "Nombre maximum de résultats",
80
88
  "Include additional information about the issue in the response": "Inclure des informations supplémentaires sur le problème dans la réponse",
81
89
  "Map human readable names to Fields, Rendered Fields, Schema and Edit Meta.\nNotes:\n- This would implicitly add \"names\" to the expand field\n- If there are fields with the same name, they may be overridden": "Mappez les noms lisibles des champs, des champs rendus, du schéma et de la méta d'édition.\nNotes :\n- Ceci ajouterait implicitement \"names\" au champ d'extension\n- Si il y a des champs avec le même nom, ils peuvent être remplacés",
@@ -103,8 +111,24 @@
103
111
  "New Issue": "Nouveau problème",
104
112
  "Updated Issue": "Problème mis à jour",
105
113
  "Updated Issue Status": "Statut du problème mis à jour",
114
+ "New Comment": "Nouveau commentaire",
115
+ "Issue Assigned": "Question assignée",
116
+ "New Attachment on Issue": "Nouvelle pièce jointe sur le problème",
106
117
  "Triggers when a new issue is created": "Déclenche quand un nouveau ticket est créé",
107
118
  "Triggers when an issue is updated": "Déclenche quand un problème est mis à jour",
108
119
  "Triggers when an issue status is updated": "Déclenche quand un statut de ticket est mis à jour",
109
- "Use to filter issues watched": "Utiliser pour filtrer les problèmes vus"
120
+ "Fires whenever someone adds a new comment to a Jira issue. Great for getting notified in Slack or Teams, syncing customer replies, or reacting to feedback automatically.": "Incendie chaque fois que quelqu'un ajoute un nouveau commentaire à un problème Jira. Idéal pour être notifié dans Slack ou Teams, synchroniser les réponses des clients ou réagir automatiquement aux commentaires.",
121
+ "Fires when a Jira issue is assigned to someone. Use it to ping people in Slack/Teams the moment work lands on them, auto-create a to-do when tickets hit your queue, or track hand-offs between teammates.": "Tire quand un ticket Jira est assigné à quelqu'un. Utilisez-le pour le ping des gens dans Slack/Teams au moment où ils travaillent sur eux, créer automatiquement une tâche à faire lorsque les tickets arrivent dans votre file d’attente ou suivre les hand-offs entre les coéquipiers.",
122
+ "Fires when a file is attached to a Jira issue. Great for auto-saving screenshots to Google Drive, forwarding customer uploads to support tools, or archiving documents in S3.": "Se déclenche lorsqu'un fichier est attaché à un problème Jira. Idéal pour enregistrer automatiquement des captures d'écran sur Google Drive, pour transférer des téléchargements vers des outils de support ou pour archiver des documents dans S3.",
123
+ "Only watch these issues (optional)": "Voir uniquement ces tickets (facultatif)",
124
+ "Auto-fix the filter": "Corriger automatiquement le filtre",
125
+ "Only when assigned to me": "Uniquement en cas d'assignation",
126
+ "Assignee (optional)": "Destinataire (optionnel)",
127
+ "Use to filter issues watched": "Utiliser pour filtrer les problèmes vus",
128
+ "Leave empty to watch comments on **every** issue in your Jira.\n\nTo narrow it down, paste a Jira filter here. A few ready-to-use examples:\n\n- `project = \"SUPPORT\"` — only issues in the Support project\n- `assignee = currentUser()` — only issues assigned to you\n- `status != Done` — skip closed issues\n- `labels = \"vip\"` — only issues tagged `vip`\n- `project = \"SUPPORT\" AND priority = High` — combine conditions with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build the filter visually, ": "Laissez vide pour regarder les commentaires sur **chaque** problème dans votre Jira.\n\nPour le réduire, collez un filtre Jira ici. Quelques exemples prêts à être utilisés :\n\n- `project = \"SUPPORT\"` - seulement les problèmes dans le projet de support\n- `assignee = currentUser()` - seulement les problèmes qui vous sont assignés\n- `status ! Terminé ` - saute les demandes fermées\n- `labels = \"vip\"` - seulement les problèmes taggés `vip`\n- `project = \"SUPPORT\" AND priority = High` - combine les conditions avec `AND`\n\nVous ne savez pas quoi écrire ? Ouvrez Jira → Filtres → Recherche avancée, construisez le filtre visuellement, puis copiez la requête ici.",
129
+ "Keep this on. If your filter references something you can't access (a private project, a deleted field), Jira will automatically clean it up instead of erroring.": "Garder cela activé. Si votre filtre référence quelque chose que vous ne pouvez pas accéder (un projet privé, un champ supprimé), Jira le nettoie automatiquement au lieu d'erreurs.",
130
+ "Only trigger when the issue is assigned to the user who set up this connection. Overrides the Assignee field below.": "Ne se déclenche que lorsque le ticket est assigné à l'utilisateur qui a configuré cette connexion. Remplace le champ assigné ci-dessous.",
131
+ "Pick a teammate to watch. Leave empty to trigger on assignments to anyone. Ignored if \"Only when assigned to me\" is checked.": "Choisissez un coéquipier à surveiller. Laissez vide pour déclencher les affectations à quiconque. Ignoré si « Seulement en cas d'affectation» est coché.",
132
+ "Narrow down which issues to watch. Leave empty to watch every issue in your Jira.\n\nReady-to-use examples:\n\n- `project = \"SUPPORT\"` — only the Support project\n- `priority = High` — only high-priority issues\n- `labels = \"vip\"` — only issues tagged `vip`\n- `project = \"SUPPORT\" AND status != Done` — combine with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build a filter visually, then copy the query here.": "Rétrécissez les problèmes à surveiller. Laissez vide pour regarder chaque problème dans votre Jira.\n\nExemples prêts à être utilisés :\n\n- `project = \"SUPPORT\"` - seulement le projet de support\n- `priority = High` - seulement les problèmes prioritaires\n- `labels = \"vip\"` - seulement les problèmes taggés `vip`\n- `project = \"SUPPORT\" ET statut ! Terminé ` — combiné avec `AND`\n\nVous ne savez pas quoi écrire ? Ouvrez Jira → Filtres → Recherche avancée, construisez un filtre visuellement, puis copiez la requête ici.",
133
+ "Narrow down which issues to watch. Leave empty to watch every issue in your Jira.\n\nReady-to-use examples:\n\n- `project = \"SUPPORT\"` — only the Support project\n- `issuetype = Bug` — only bugs\n- `labels = \"screenshot-needed\"` — only issues tagged `screenshot-needed`\n- `project = \"SUPPORT\" AND status != Done` — combine with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build a filter visually, then copy the query here.": "Rétrécissez les problèmes à surveiller. Laissez vide pour regarder chaque problème dans votre Jira.\n\nExemples prêt-à-utiliser :\n\n- `project = \"SUPPORT\"` - seulement le projet de support\n- `issuetype = Bug` - seulement bugs\n- `labels = \"screenshot-needed\"` - seulement les problèmes taggés `screenshot-needed`\n- `project = \"SUPPORT\" ET statut ! Terminé ` — combiné avec `AND`\n\nVous ne savez pas quoi écrire ? Ouvrez Jira → Filtres → Recherche avancée, construisez un filtre visuellement, puis copiez la requête ici."
110
134
  }
package/src/i18n/ja.json CHANGED
@@ -22,6 +22,7 @@
22
22
  "Delete Issue Comment": "課題のコメントを削除",
23
23
  "Markdown to Jira format": "Markdown to Jira format",
24
24
  "Get Issue": "問題を取得",
25
+ "Transition Issue": "トランジションの問題",
25
26
  "Custom API Call": "カスタムAPI通話",
26
27
  "Creates a new issue in a project.": "プロジェクトで新しい課題を作成します。",
27
28
  "Updates an existing issue.": "既存の問題を更新します。",
@@ -38,6 +39,7 @@
38
39
  "Deletes a comment on a specific issue.": "特定の課題に関するコメントを削除します。",
39
40
  "Convert Markdown-formatted text to Jira's ADF syntax for use in comments and descriptions etc": "コメントや説明などに使用するために、Markdown形式のテキストをJiraのADF構文に変換する",
40
41
  "Get issue data.": "課題データを取得します。",
42
+ "Moves an issue to a new status by executing a workflow transition.": "ワークフローの移行を実行して、課題を新しい状態に移動します。",
41
43
  "Make a custom API call to a specific endpoint": "特定のエンドポイントへのカスタム API コールを実行します。",
42
44
  "Project ID or Key": "プロジェクト ID またはキー",
43
45
  "Issue Type": "課題の種類",
@@ -46,7 +48,10 @@
46
48
  "Issue ID or Key": "課題 ID またはキー",
47
49
  "Status": "ステータス",
48
50
  "Keyword": "Keyword",
51
+ "Markdown": "Markdown",
49
52
  "JQL": "JQL",
53
+ "Fields to Return": "Fields to Return",
54
+ "Map Field Names": "マップフィールド名",
50
55
  "Max Results": "最大結果",
51
56
  "Sanitize JQL": "JQL サニタイズ",
52
57
  "Assignee": "Assignee",
@@ -63,8 +68,8 @@
63
68
  "Limit": "制限",
64
69
  "Markdown text": "Markdown テキスト",
65
70
  "Expand": "展開",
66
- "Map Field Names": "マップフィールド名",
67
71
  "Map Transition Names": "マップのトランジション名",
72
+ "Transition": "トランジション",
68
73
  "Method": "方法",
69
74
  "Headers": "ヘッダー",
70
75
  "Query Parameters": "クエリパラメータ",
@@ -75,7 +80,10 @@
75
80
  "Timeout (in seconds)": "タイムアウト(秒)",
76
81
  "Follow redirects": "リダイレクトをフォローする",
77
82
  "https://developer.atlassian.com/cloud/jira/platform/apis/document/structure": "https://developer.atlassian.com/cloud/jira/platform/apis/document/structure",
78
- "The JQL query to use in the search": "検索で使用する JQL クエリ",
83
+ "Fetching a large number of issues without specifying **Fields to Return** may exceed your flow's memory limits. Use field selection to reduce payload size.": "**Fields to Return** を指定せずに多数の問題を取得すると、フローのメモリ制限を超える可能性があります。フィールド選択を使用してペイロードのサイズを小さくします。",
84
+ "The JQL query to use in search (Tip: Use single quotes for strings/dates)": "検索で使用する JQL クエリ (ヒント: 文字列/日付に単一引用符を使用)",
85
+ "List of exact Jira Field IDs to return (e.g., 'summary', 'customfield_10016').\nSpecial commands:\n- Use *all for every field.\n- Use *navigable for standard fields (default).\n- Prefix with a minus to exclude (e.g., -description).\nExample: *all and -comment returns everything except comments.": "List of exact Jira Field IDs to return (e.g., 'summary', 'customfield_10016').\nSpecial commands:\n- Use *all for every field.\n- Use *navigable for standard fields (default).\n- Prefix with a minus to exclude (e.g., -description).\nExample: *all and -comment returns everything except comments.",
86
+ "Map human readable names to Fields in the output.\nNotes:\n- If there are fields with the same name, they may be overridden.": "出力のフィールドに人間が読める名前をマップします。\n注意事項:\n- 同じ名前のフィールドがある場合、上書きされる可能性があります。",
79
87
  "Maximum number of results": "結果の最大数",
80
88
  "Include additional information about the issue in the response": "問題に関する追加情報を返信に含める",
81
89
  "Map human readable names to Fields, Rendered Fields, Schema and Edit Meta.\nNotes:\n- This would implicitly add \"names\" to the expand field\n- If there are fields with the same name, they may be overridden": "人間が読める名前をフィールド、レンダリングされたフィールド、スキーマ、およびメタの編集にマップします。\n備考:\n- 拡張フィールド\n- 同じ名前のフィールドがある場合、暗黙的に「名前」を追加します。 彼らはオーバーライドされるかもしれません",
@@ -103,8 +111,24 @@
103
111
  "New Issue": "新しい課題",
104
112
  "Updated Issue": "更新された課題",
105
113
  "Updated Issue Status": "更新された課題ステータス",
114
+ "New Comment": "新しいコメント",
115
+ "Issue Assigned": "割り当てられた課題",
116
+ "New Attachment on Issue": "問題に関する新しい添付ファイル",
106
117
  "Triggers when a new issue is created": "新しい課題が作成されたときにトリガーする",
107
118
  "Triggers when an issue is updated": "課題が更新されたときに発生する",
108
119
  "Triggers when an issue status is updated": "課題の状態が更新されたときに発行されます",
109
- "Use to filter issues watched": "監視されている課題をフィルタリングするために使用します"
120
+ "Fires whenever someone adds a new comment to a Jira issue. Great for getting notified in Slack or Teams, syncing customer replies, or reacting to feedback automatically.": "誰かがJira問題に新しいコメントを追加するたびに発生します。 Slack やチームで通知を受け取ったり、顧客からの返信を同期したり、フィードバックに自動的に反応したりするのに最適です。",
121
+ "Fires when a Jira issue is assigned to someone. Use it to ping people in Slack/Teams the moment work lands on them, auto-create a to-do when tickets hit your queue, or track hand-offs between teammates.": "Jiraの問題が誰かに割り当てられたときに発生します。 Slack/Teams の人々の作業が彼らに着陸する瞬間にpingにそれを使用してください チケットがキューにヒットしたときに自動的にTo-doを作成するか、チームメイト間のハンドオフを追跡します。",
122
+ "Fires when a file is attached to a Jira issue. Great for auto-saving screenshots to Google Drive, forwarding customer uploads to support tools, or archiving documents in S3.": "Jira問題にファイルが添付されたときに発生します。 Google ドライブへのスクリーンショットの自動保存、サポートツールへの顧客のアップロード、S3内のドキュメントのアーカイブなどに便利です。",
123
+ "Only watch these issues (optional)": "これらの課題のみを見る (オプション)",
124
+ "Auto-fix the filter": "フィルターを自動修正",
125
+ "Only when assigned to me": "自分に割り当てられた時のみ",
126
+ "Assignee (optional)": "担当者(任意)",
127
+ "Use to filter issues watched": "監視されている課題をフィルタリングするために使用します",
128
+ "Leave empty to watch comments on **every** issue in your Jira.\n\nTo narrow it down, paste a Jira filter here. A few ready-to-use examples:\n\n- `project = \"SUPPORT\"` — only issues in the Support project\n- `assignee = currentUser()` — only issues assigned to you\n- `status != Done` — skip closed issues\n- `labels = \"vip\"` — only issues tagged `vip`\n- `project = \"SUPPORT\" AND priority = High` — combine conditions with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build the filter visually, ": "Leave empty to watch comments on **every** issue in your Jira.\n\nTo narrow it down, paste a Jira filter here. A few ready-to-use examples:\n\n- `project = \"SUPPORT\"` — only issues in the Support project\n- `assignee = currentUser()` — only issues assigned to you\n- `status != Done` — skip closed issues\n- `labels = \"vip\"` — only issues tagged `vip`\n- `project = \"SUPPORT\" AND priority = High` — combine conditions with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build the filter visually, then copy the query here.",
129
+ "Keep this on. If your filter references something you can't access (a private project, a deleted field), Jira will automatically clean it up instead of erroring.": "これをつけておきなさい。 フィルタがアクセスできないもの(プライベートプロジェクト、削除されたフィールド)を参照している場合、Jira はエラーではなく自動的にクリーンアップします。",
130
+ "Only trigger when the issue is assigned to the user who set up this connection. Overrides the Assignee field below.": "この接続を設定したユーザーに課題が割り当てられている場合にのみトリガします。以下の担当者フィールドを上書きします。",
131
+ "Pick a teammate to watch. Leave empty to trigger on assignments to anyone. Ignored if \"Only when assigned to me\" is checked.": "見るチームメイトを選択します。空のままにすると、誰にでも割り当てられます。「自分に割り当てられたときのみ」がチェックされている場合は無視されます。",
132
+ "Narrow down which issues to watch. Leave empty to watch every issue in your Jira.\n\nReady-to-use examples:\n\n- `project = \"SUPPORT\"` — only the Support project\n- `priority = High` — only high-priority issues\n- `labels = \"vip\"` — only issues tagged `vip`\n- `project = \"SUPPORT\" AND status != Done` — combine with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build a filter visually, then copy the query here.": "Narrow down which issues to watch. Leave empty to watch every issue in your Jira.\n\nReady-to-use examples:\n\n- `project = \"SUPPORT\"` — only the Support project\n- `priority = High` — only high-priority issues\n- `labels = \"vip\"` — only issues tagged `vip`\n- `project = \"SUPPORT\" AND status != Done` — combine with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build a filter visually, then copy the query here.",
133
+ "Narrow down which issues to watch. Leave empty to watch every issue in your Jira.\n\nReady-to-use examples:\n\n- `project = \"SUPPORT\"` — only the Support project\n- `issuetype = Bug` — only bugs\n- `labels = \"screenshot-needed\"` — only issues tagged `screenshot-needed`\n- `project = \"SUPPORT\" AND status != Done` — combine with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build a filter visually, then copy the query here.": "Narrow down which issues to watch. Leave empty to watch every issue in your Jira.\n\nReady-to-use examples:\n\n- `project = \"SUPPORT\"` — only the Support project\n- `issuetype = Bug` — only bugs\n- `labels = \"screenshot-needed\"` — only issues tagged `screenshot-needed`\n- `project = \"SUPPORT\" AND status != Done` — combine with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build a filter visually, then copy the query here."
110
134
  }
package/src/i18n/nl.json CHANGED
@@ -22,6 +22,7 @@
22
22
  "Delete Issue Comment": "Issue Opmerking verwijderen",
23
23
  "Markdown to Jira format": "Markdown naar Jira formaat",
24
24
  "Get Issue": "Probleem ophalen",
25
+ "Transition Issue": "Transitie probleem",
25
26
  "Custom API Call": "Custom API Call",
26
27
  "Creates a new issue in a project.": "Maakt een nieuw issue aan in een project.",
27
28
  "Updates an existing issue.": "Werkt een bestaand probleem bij.",
@@ -38,6 +39,7 @@
38
39
  "Deletes a comment on a specific issue.": "Verwijdert een reactie op een specifiek probleem.",
39
40
  "Convert Markdown-formatted text to Jira's ADF syntax for use in comments and descriptions etc": "Converteer markdown-geformatteerde tekst naar Jira's ADF-syntaxis voor gebruik in commentaren en beschrijvingen enz",
40
41
  "Get issue data.": "Haal probleemgegevens op.",
42
+ "Moves an issue to a new status by executing a workflow transition.": "Verplaatst een probleem naar een nieuwe status door een transitie van workflow uit te voeren.",
41
43
  "Make a custom API call to a specific endpoint": "Maak een aangepaste API call naar een specifiek eindpunt",
42
44
  "Project ID or Key": "Project ID of sleutel",
43
45
  "Issue Type": "Type probleem",
@@ -46,7 +48,10 @@
46
48
  "Issue ID or Key": "Issue ID of sleutel",
47
49
  "Status": "status",
48
50
  "Keyword": "Keyword",
51
+ "Markdown": "Markdown",
49
52
  "JQL": "JQL",
53
+ "Fields to Return": "Velden om te retourneren",
54
+ "Map Field Names": "Map veldnamen",
50
55
  "Max Results": "Max. aantal resultaten",
51
56
  "Sanitize JQL": "Sanitiseer JQL",
52
57
  "Assignee": "Assignee",
@@ -63,8 +68,8 @@
63
68
  "Limit": "Limiet",
64
69
  "Markdown text": "Markdown tekst",
65
70
  "Expand": "Uitklappen",
66
- "Map Field Names": "Map veldnamen",
67
71
  "Map Transition Names": "Kaart overgangsnamen",
72
+ "Transition": "Transitie",
68
73
  "Method": "Methode",
69
74
  "Headers": "Kopteksten",
70
75
  "Query Parameters": "Query parameters",
@@ -75,7 +80,10 @@
75
80
  "Timeout (in seconds)": "Time-out (in seconden)",
76
81
  "Follow redirects": "Volg omleidingen",
77
82
  "https://developer.atlassian.com/cloud/jira/platform/apis/document/structure": "https://developer.atlassian.com/cloud/jira/platform/apis/document/structuur",
78
- "The JQL query to use in the search": "De JQL query te gebruiken in de zoekopdracht",
83
+ "Fetching a large number of issues without specifying **Fields to Return** may exceed your flow's memory limits. Use field selection to reduce payload size.": "Het ophalen van een groot aantal problemen zonder het opgeven van **Velden om terug te sturen** kan de geheugenlimiet van uw flow's overschrijden. Gebruik veld selectie om de payload grootte te verminderen.",
84
+ "The JQL query to use in search (Tip: Use single quotes for strings/dates)": "De JQL query in zoekopdracht (Tip: Gebruik enkele aanhalingstekens voor tekenreeksen/datums)",
85
+ "List of exact Jira Field IDs to return (e.g., 'summary', 'customfield_10016').\nSpecial commands:\n- Use *all for every field.\n- Use *navigable for standard fields (default).\n- Prefix with a minus to exclude (e.g., -description).\nExample: *all and -comment returns everything except comments.": "Lijst met exacte Jira veld IDs om terug te keren (bijv. 'samenvatting', 'customfield_10016').\nSpeciale commando's:\n- Gebruik *all voor elk veld.\n- Gebruik *navigeerbaar voor standaard velden (standaard).\n- Voorvoegsel met een min om uit te sluiten (e. ., -description).\nVoorbeeld: *all en -comment geeft alles behalve commentaren terug.",
86
+ "Map human readable names to Fields in the output.\nNotes:\n- If there are fields with the same name, they may be overridden.": "Kaart menselijke leesbare namen aan velden in de uitvoer.\nnotities:\n- Als er velden met dezelfde naam zijn, kunnen ze worden overschreven.",
79
87
  "Maximum number of results": "Maximum aantal resultaten",
80
88
  "Include additional information about the issue in the response": "Voeg aanvullende informatie over het probleem toe in de reactie",
81
89
  "Map human readable names to Fields, Rendered Fields, Schema and Edit Meta.\nNotes:\n- This would implicitly add \"names\" to the expand field\n- If there are fields with the same name, they may be overridden": "Kaart menselijke leesbare namen naar Fields, Rendered Fields, Schema en Bewerken Meta.\nnotities:\n- Dit zou impliciet \"namen\" toevoegen aan het uitbreidingsveld\n- Als er velden met dezelfde naam zijn ze kunnen worden overschreven",
@@ -103,8 +111,24 @@
103
111
  "New Issue": "Nieuw probleem",
104
112
  "Updated Issue": "Probleem bijgewerkt",
105
113
  "Updated Issue Status": "Bijgewerkte probleemstatus",
114
+ "New Comment": "Nieuwe reactie",
115
+ "Issue Assigned": "Issue toegewezen",
116
+ "New Attachment on Issue": "Nieuwe bijlage bij issue",
106
117
  "Triggers when a new issue is created": "Triggert wanneer een nieuw issue wordt aangemaakt",
107
118
  "Triggers when an issue is updated": "Triggert wanneer een issue wordt bijgewerkt",
108
119
  "Triggers when an issue status is updated": "Triggert wanneer een issuestatus wordt bijgewerkt",
109
- "Use to filter issues watched": "Gebruik om problemen te filteren"
120
+ "Fires whenever someone adds a new comment to a Jira issue. Great for getting notified in Slack or Teams, syncing customer replies, or reacting to feedback automatically.": "Schiet wanneer iemand een nieuwe reactie toevoegt aan een Jira probleem. Ideaal voor het ontvangen van meldingen bij Slack of Teams, het synchroniseren van klantreacties of het automatisch beantwoorden van feedback.",
121
+ "Fires when a Jira issue is assigned to someone. Use it to ping people in Slack/Teams the moment work lands on them, auto-create a to-do when tickets hit your queue, or track hand-offs between teammates.": "Vuurt af wanneer een zaak van Jira aan iemand is toegewezen. Gebruik het om mensen in Slack/Teams te pikken wanneer het moment waarop het werk aan hen begint, automatisch een todo maken als tickets je wachtrij raken of hand-offs tussen teamgenoten volgen.",
122
+ "Fires when a file is attached to a Jira issue. Great for auto-saving screenshots to Google Drive, forwarding customer uploads to support tools, or archiving documents in S3.": "Vuurt wanneer een bestand is toegevoegd aan een Jira probleem. Ideaal voor het automatisch opslaan van screenshots naar Google Drive, het doorsturen van klantuploads voor ondersteunende tools of archivering documenten in S3.",
123
+ "Only watch these issues (optional)": "Bekijk alleen deze problemen (optioneel)",
124
+ "Auto-fix the filter": "Auto-fix van de filter",
125
+ "Only when assigned to me": "Alleen wanneer toegewezen aan mij",
126
+ "Assignee (optional)": "Toegewezen (optioneel)",
127
+ "Use to filter issues watched": "Gebruik om problemen te filteren",
128
+ "Leave empty to watch comments on **every** issue in your Jira.\n\nTo narrow it down, paste a Jira filter here. A few ready-to-use examples:\n\n- `project = \"SUPPORT\"` — only issues in the Support project\n- `assignee = currentUser()` — only issues assigned to you\n- `status != Done` — skip closed issues\n- `labels = \"vip\"` — only issues tagged `vip`\n- `project = \"SUPPORT\" AND priority = High` — combine conditions with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build the filter visually, ": "Laat leeg om commentaar op **elke** probleem in je Jira te bekijken.\n\nOm het te verkleinen, plak hier een Jira filter. Enkele kant-en-klaar te gebruiken voorbeelden:\n\n- `project = \"SUPPORT\"` - alleen problemen in het Support project\n- `taakontvanger = currentUser()` — alleen problemen die aan je\nzijn toegewezen - `status! Gedaan` - sla gesloten issues\n- `labels = \"vip\"` - alleen problemen getagged `vip`\n- `project = \"SUPPORT\" EN D prioriteit = High` - combineer voorwaarden met `AND`\n\nNiet zeker wat te schrijven? Open Jira → Filters → Geavanceerd zoeken, bouw het filter visueel en kopieer de zoekopdracht hier.",
129
+ "Keep this on. If your filter references something you can't access (a private project, a deleted field), Jira will automatically clean it up instead of erroring.": "Blijf dit aan. Als je filter verwijst naar iets waar je geen toegang tot hebt (een privéproject, een verwijderd veld) zal Jira het automatisch opruimen in plaats van fouten.",
130
+ "Only trigger when the issue is assigned to the user who set up this connection. Overrides the Assignee field below.": "Alleen trigger wanneer het issue is toegewezen aan de gebruiker die deze verbinding heeft ingesteld. Overschrijft het toegewezen veld hieronder.",
131
+ "Pick a teammate to watch. Leave empty to trigger on assignments to anyone. Ignored if \"Only when assigned to me\" is checked.": "Kies een teamgenoot om te bekijken. Laat leeg om toe te wijzen aan iemand. Genegeerd als \"Alleen wanneer toegewezen aan mij\" is aangevinkt.",
132
+ "Narrow down which issues to watch. Leave empty to watch every issue in your Jira.\n\nReady-to-use examples:\n\n- `project = \"SUPPORT\"` — only the Support project\n- `priority = High` — only high-priority issues\n- `labels = \"vip\"` — only issues tagged `vip`\n- `project = \"SUPPORT\" AND status != Done` — combine with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build a filter visually, then copy the query here.": "Smalle naar beneden welke problemen u moet bekijken. Laat leeg om elk probleem in uw Jira te bekijken.\n\nReady-to-use voorbeelden:\n\n- `project = \"SUPPORT\"` - alleen het Support project\n- `priority = High` — alleen problemen met hoge prioriteit\n- `labels = \"vip\"` — alleen problemen met `vip`\n- `project = \"SUPPORT\" EN status ! Gedaan\" - combineren met `AND`\n\nNiet zeker wat te schrijven? Open Jira → Filters → Geavanceerd zoeken, bouw een filter visueel en kopieer de zoekopdracht hier.",
133
+ "Narrow down which issues to watch. Leave empty to watch every issue in your Jira.\n\nReady-to-use examples:\n\n- `project = \"SUPPORT\"` — only the Support project\n- `issuetype = Bug` — only bugs\n- `labels = \"screenshot-needed\"` — only issues tagged `screenshot-needed`\n- `project = \"SUPPORT\" AND status != Done` — combine with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build a filter visually, then copy the query here.": "Smalle naar beneden welke problemen u moet bekijken. Laat leeg om elk probleem in uw Jira te bekijken.\n\nReady-to-use voorbeelden:\n\n- `project = \"SUPPORT\"` - alleen het Support project\n- `issuetype = Bug` — alleen bugs\n- `labels = \"screenshot-needed\"` — alleen problemen met `screenshot-needed`\n- `project = \"SUPPORT\" EN status ! Gedaan\" - combineren met `AND`\n\nNiet zeker wat te schrijven? Open Jira → Filters → Geavanceerd zoeken, bouw een filter visueel en kopieer de zoekopdracht hier."
110
134
  }
package/src/i18n/pt.json CHANGED
@@ -22,6 +22,7 @@
22
22
  "Delete Issue Comment": "Excluir comentário da issue",
23
23
  "Markdown to Jira format": "Formato Jira Markdown",
24
24
  "Get Issue": "Obter problema",
25
+ "Transition Issue": "Problema de Transição",
25
26
  "Custom API Call": "Chamada de API personalizada",
26
27
  "Creates a new issue in a project.": "Cria uma nova issue em um projeto.",
27
28
  "Updates an existing issue.": "Atualiza uma issue existente.",
@@ -38,6 +39,7 @@
38
39
  "Deletes a comment on a specific issue.": "Exclui um comentário em uma issue específica.",
39
40
  "Convert Markdown-formatted text to Jira's ADF syntax for use in comments and descriptions etc": "Converter texto formatado em Markdown-formatado para sintaxe ADF da Jaria para uso em comentários e descrições, etc.",
40
41
  "Get issue data.": "Obter dados do problema.",
42
+ "Moves an issue to a new status by executing a workflow transition.": "Move um problema para um novo status executando uma transição de fluxo de trabalho.",
41
43
  "Make a custom API call to a specific endpoint": "Faça uma chamada de API personalizada para um ponto de extremidade específico",
42
44
  "Project ID or Key": "ID ou Chave do Projeto",
43
45
  "Issue Type": "Tipo de problema",
@@ -46,7 +48,10 @@
46
48
  "Issue ID or Key": "ID ou Chave de Problema",
47
49
  "Status": "Estado",
48
50
  "Keyword": "Keyword",
51
+ "Markdown": "Markdown",
49
52
  "JQL": "QEQ",
53
+ "Fields to Return": "Campos para Devolver",
54
+ "Map Field Names": "Nomes dos Campos do Mapa",
50
55
  "Max Results": "Resultados no Máx.",
51
56
  "Sanitize JQL": "JQL Sanitizado",
52
57
  "Assignee": "Assignee",
@@ -63,8 +68,8 @@
63
68
  "Limit": "Limitar",
64
69
  "Markdown text": "Texto Markdown",
65
70
  "Expand": "Expandir",
66
- "Map Field Names": "Nomes dos Campos do Mapa",
67
71
  "Map Transition Names": "Nomes de Transição",
72
+ "Transition": "Transição",
68
73
  "Method": "Método",
69
74
  "Headers": "Cabeçalhos",
70
75
  "Query Parameters": "Parâmetros da consulta",
@@ -75,7 +80,10 @@
75
80
  "Timeout (in seconds)": "Tempo limite (em segundos)",
76
81
  "Follow redirects": "Seguir redirecionamentos",
77
82
  "https://developer.atlassian.com/cloud/jira/platform/apis/document/structure": "https://developer.atlassian.com/cloud/jira/platform/apis/document/structure",
78
- "The JQL query to use in the search": "A consulta JQL a ser usada na busca",
83
+ "Fetching a large number of issues without specifying **Fields to Return** may exceed your flow's memory limits. Use field selection to reduce payload size.": "Obtendo um grande número de problemas sem especificar **Campos de Retorno** pode exceder o limite de memória do seu fluxo. Use a seleção do campo para reduzir o tamanho do payload.",
84
+ "The JQL query to use in search (Tip: Use single quotes for strings/dates)": "A consulta JQL a ser usada na busca (Dica: use aspas simples para strings/datas)",
85
+ "List of exact Jira Field IDs to return (e.g., 'summary', 'customfield_10016').\nSpecial commands:\n- Use *all for every field.\n- Use *navigable for standard fields (default).\n- Prefix with a minus to exclude (e.g., -description).\nExample: *all and -comment returns everything except comments.": "Lista de IDs de campos exatos do Jira para retornar (por exemplo, 'sumy', 'customfield_10016').\nComandos especiais:\n- Use *todos para cada campo.\n- Usar *navegável para campos padrão (padrão).\n- Prefixo com menos para excluir (e. ., -descrição).\nExemplo: *todos e -comentários retorna tudo, exceto os comentários.",
86
+ "Map human readable names to Fields in the output.\nNotes:\n- If there are fields with the same name, they may be overridden.": "Mapear nomes humanos legíveis para Campos na saída.\nNotas:\n- Se houver campos com o mesmo nome, eles podem ser substituídos.",
79
87
  "Maximum number of results": "Número máximo de resultados",
80
88
  "Include additional information about the issue in the response": "Incluir informações adicionais sobre o problema na resposta",
81
89
  "Map human readable names to Fields, Rendered Fields, Schema and Edit Meta.\nNotes:\n- This would implicitly add \"names\" to the expand field\n- If there are fields with the same name, they may be overridden": "Mapear nomes humanos legíveis para Campos, Campos Renderizados, Schema e Editar Meta.\nNotas:\n- Isso iria implicitamente adicionar \"nomes\" ao campo de expansão\n- Se houver campos com o mesmo nome, eles podem ser substituídos",
@@ -103,8 +111,24 @@
103
111
  "New Issue": "Nova issue",
104
112
  "Updated Issue": "Issue atualizada",
105
113
  "Updated Issue Status": "Status atualizado da tarefa",
114
+ "New Comment": "Novo Comentário",
115
+ "Issue Assigned": "Tarefa Atribuída",
116
+ "New Attachment on Issue": "Novo anexo na issue",
106
117
  "Triggers when a new issue is created": "Dispara quando uma nova issue é criada",
107
118
  "Triggers when an issue is updated": "Dispara quando uma issue é atualizada",
108
119
  "Triggers when an issue status is updated": "Aciona quando um status de issue é atualizado",
109
- "Use to filter issues watched": "Use para filtrar issues assistidas"
120
+ "Fires whenever someone adds a new comment to a Jira issue. Great for getting notified in Slack or Teams, syncing customer replies, or reacting to feedback automatically.": "É acionado sempre que alguém adiciona um novo comentário a uma issue Jira. Ótimo para ser notificado em Slack ou Teams, sincronizar respostas do cliente ou reagir ao feedback automaticamente.",
121
+ "Fires when a Jira issue is assigned to someone. Use it to ping people in Slack/Teams the moment work lands on them, auto-create a to-do when tickets hit your queue, or track hand-offs between teammates.": "Atira quando uma issue do Jira é atribuída a alguém. Use-o para pancar as pessoas no Slack/Teams o momento funciona neles. criar automaticamente automaticamente quando os tickets acertarem a sua fila, ou rastrear as mãos entre companheiros de equipe.",
122
+ "Fires when a file is attached to a Jira issue. Great for auto-saving screenshots to Google Drive, forwarding customer uploads to support tools, or archiving documents in S3.": "Efetua quando um arquivo está anexado a uma issue Jira. Ótimo para salvar capturas de tela automaticamente no Google Drive, encaminhando uploads de clientes para ferramentas de suporte ou arquivando documentos no S3.",
123
+ "Only watch these issues (optional)": "Apenas veja essas questões (opcional)",
124
+ "Auto-fix the filter": "Corrigir filtro automaticamente",
125
+ "Only when assigned to me": "Somente quando atribuído a mim",
126
+ "Assignee (optional)": "Atribuído (opcional)",
127
+ "Use to filter issues watched": "Use para filtrar issues assistidas",
128
+ "Leave empty to watch comments on **every** issue in your Jira.\n\nTo narrow it down, paste a Jira filter here. A few ready-to-use examples:\n\n- `project = \"SUPPORT\"` — only issues in the Support project\n- `assignee = currentUser()` — only issues assigned to you\n- `status != Done` — skip closed issues\n- `labels = \"vip\"` — only issues tagged `vip`\n- `project = \"SUPPORT\" AND priority = High` — combine conditions with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build the filter visually, ": "Deixe em branco para ver comentários sobre **todos** os problemas em seu Jira.\n\nPara restringir, cole um filtro Jira aqui. Alguns exemplos prontos para usar:\n\n- `project = \"SUPPORT\"` — apenas issues no projeto de Suporte\n- `assignee = currentUser()` — apenas issues atribuídas a você\n- `status ! Feito` — pular issues fechadas\n- `labels = \"vip\"` — apenas issues marcadas como `vip`\n- `projeto = \"SUPORTO\" E prioridade = Alta` — combinar condições com `AND`\n\nNão sabe ao certo o que escrever? Abra Jira → Filtros → Pesquisa avançada, crie o filtro visualmente e copie a consulta aqui.",
129
+ "Keep this on. If your filter references something you can't access (a private project, a deleted field), Jira will automatically clean it up instead of erroring.": "Mantenha ligado. Se seu filtro faz referência a algo que você não pode acessar (um projeto privado, um campo excluído), Jira irá limpá-lo automaticamente ao invés de um erro.",
130
+ "Only trigger when the issue is assigned to the user who set up this connection. Overrides the Assignee field below.": "Somente disparar quando a issue for atribuída ao usuário que configurou esta conexão. Sobrescreve o campo Atribuído abaixo.",
131
+ "Pick a teammate to watch. Leave empty to trigger on assignments to anyone. Ignored if \"Only when assigned to me\" is checked.": "Escolha um colega de equipe para assistir. Deixe em branco para disparar nas missões a qualquer um. Ignorado se \"Apenas quando me for atribuído\" estiver marcado.",
132
+ "Narrow down which issues to watch. Leave empty to watch every issue in your Jira.\n\nReady-to-use examples:\n\n- `project = \"SUPPORT\"` — only the Support project\n- `priority = High` — only high-priority issues\n- `labels = \"vip\"` — only issues tagged `vip`\n- `project = \"SUPPORT\" AND status != Done` — combine with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build a filter visually, then copy the query here.": "Reduza os problemas a serem observados. Deixe em branco para ver todas as questões no Jira.\n\nExemplos prontos para utilizar:\n\n- `project = \"SUPORT\"` — apenas o projeto de suporte\n- `prioridade = Alta` — apenas questões de alta prioridade\n- `labels = \"vip\"` — apenas issues marcadas como `vip`\n- `project = \"SUPORTO\" E status ! Feito` — combine com `AND`\n\nNão tem certeza do que escrever? Abra Jira → Filtros → Pesquisa avançada, crie um filtro visualmente e copie a consulta aqui.",
133
+ "Narrow down which issues to watch. Leave empty to watch every issue in your Jira.\n\nReady-to-use examples:\n\n- `project = \"SUPPORT\"` — only the Support project\n- `issuetype = Bug` — only bugs\n- `labels = \"screenshot-needed\"` — only issues tagged `screenshot-needed`\n- `project = \"SUPPORT\" AND status != Done` — combine with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build a filter visually, then copy the query here.": "Reduza os problemas a serem observados. Deixe em branco para ver todas as questões no Jira.\n\nExemplos de Ready-to-use:\n\n- `project = \"SUPORT\"` — apenas o projeto de suporte\n- `issuetype = Bug` — apenas bugs\n- `labels = \"screenshot-needed\"` — apenas problemas marcados como `screenshot-need`\n- `project = \"SUPPORT\" E status ! Feito` — combine com `AND`\n\nNão tem certeza do que escrever? Abra Jira → Filtros → Pesquisa avançada, crie um filtro visualmente e copie a consulta aqui."
110
134
  }
@@ -22,6 +22,7 @@
22
22
  "Delete Issue Comment": "Delete Issue Comment",
23
23
  "Markdown to Jira format": "Markdown to Jira format",
24
24
  "Get Issue": "Get Issue",
25
+ "Transition Issue": "Transition Issue",
25
26
  "Custom API Call": "Custom API Call",
26
27
  "Creates a new issue in a project.": "Creates a new issue in a project.",
27
28
  "Updates an existing issue.": "Updates an existing issue.",
@@ -38,6 +39,7 @@
38
39
  "Deletes a comment on a specific issue.": "Deletes a comment on a specific issue.",
39
40
  "Convert Markdown-formatted text to Jira's ADF syntax for use in comments and descriptions etc": "Convert Markdown-formatted text to Jira's ADF syntax for use in comments and descriptions etc",
40
41
  "Get issue data.": "Get issue data.",
42
+ "Moves an issue to a new status by executing a workflow transition.": "Moves an issue to a new status by executing a workflow transition.",
41
43
  "Make a custom API call to a specific endpoint": "Make a custom API call to a specific endpoint",
42
44
  "Project ID or Key": "Project ID or Key",
43
45
  "Issue Type": "Issue Type",
@@ -67,6 +69,7 @@
67
69
  "Markdown text": "Markdown text",
68
70
  "Expand": "Expand",
69
71
  "Map Transition Names": "Map Transition Names",
72
+ "Transition": "Transition",
70
73
  "Method": "Method",
71
74
  "Headers": "Headers",
72
75
  "Query Parameters": "Query Parameters",
@@ -108,8 +111,24 @@
108
111
  "New Issue": "New Issue",
109
112
  "Updated Issue": "Updated Issue",
110
113
  "Updated Issue Status": "Updated Issue Status",
114
+ "New Comment": "New Comment",
115
+ "Issue Assigned": "Issue Assigned",
116
+ "New Attachment on Issue": "New Attachment on Issue",
111
117
  "Triggers when a new issue is created": "Triggers when a new issue is created",
112
118
  "Triggers when an issue is updated": "Triggers when an issue is updated",
113
119
  "Triggers when an issue status is updated": "Triggers when an issue status is updated",
114
- "Use to filter issues watched": "Use to filter issues watched"
120
+ "Fires whenever someone adds a new comment to a Jira issue. Great for getting notified in Slack or Teams, syncing customer replies, or reacting to feedback automatically.": "Fires whenever someone adds a new comment to a Jira issue. Great for getting notified in Slack or Teams, syncing customer replies, or reacting to feedback automatically.",
121
+ "Fires when a Jira issue is assigned to someone. Use it to ping people in Slack/Teams the moment work lands on them, auto-create a to-do when tickets hit your queue, or track hand-offs between teammates.": "Fires when a Jira issue is assigned to someone. Use it to ping people in Slack/Teams the moment work lands on them, auto-create a to-do when tickets hit your queue, or track hand-offs between teammates.",
122
+ "Fires when a file is attached to a Jira issue. Great for auto-saving screenshots to Google Drive, forwarding customer uploads to support tools, or archiving documents in S3.": "Fires when a file is attached to a Jira issue. Great for auto-saving screenshots to Google Drive, forwarding customer uploads to support tools, or archiving documents in S3.",
123
+ "Only watch these issues (optional)": "Only watch these issues (optional)",
124
+ "Auto-fix the filter": "Auto-fix the filter",
125
+ "Only when assigned to me": "Only when assigned to me",
126
+ "Assignee (optional)": "Assignee (optional)",
127
+ "Use to filter issues watched": "Use to filter issues watched",
128
+ "Leave empty to watch comments on **every** issue in your Jira.\n\nTo narrow it down, paste a Jira filter here. A few ready-to-use examples:\n\n- `project = \"SUPPORT\"` — only issues in the Support project\n- `assignee = currentUser()` — only issues assigned to you\n- `status != Done` — skip closed issues\n- `labels = \"vip\"` — only issues tagged `vip`\n- `project = \"SUPPORT\" AND priority = High` — combine conditions with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build the filter visually, ": "Leave empty to watch comments on **every** issue in your Jira.\n\nTo narrow it down, paste a Jira filter here. A few ready-to-use examples:\n\n- `project = \"SUPPORT\"` — only issues in the Support project\n- `assignee = currentUser()` — only issues assigned to you\n- `status != Done` — skip closed issues\n- `labels = \"vip\"` — only issues tagged `vip`\n- `project = \"SUPPORT\" AND priority = High` — combine conditions with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build the filter visually, then copy the query here.",
129
+ "Keep this on. If your filter references something you can't access (a private project, a deleted field), Jira will automatically clean it up instead of erroring.": "Keep this on. If your filter references something you can't access (a private project, a deleted field), Jira will automatically clean it up instead of erroring.",
130
+ "Only trigger when the issue is assigned to the user who set up this connection. Overrides the Assignee field below.": "Only trigger when the issue is assigned to the user who set up this connection. Overrides the Assignee field below.",
131
+ "Pick a teammate to watch. Leave empty to trigger on assignments to anyone. Ignored if \"Only when assigned to me\" is checked.": "Pick a teammate to watch. Leave empty to trigger on assignments to anyone. Ignored if \"Only when assigned to me\" is checked.",
132
+ "Narrow down which issues to watch. Leave empty to watch every issue in your Jira.\n\nReady-to-use examples:\n\n- `project = \"SUPPORT\"` — only the Support project\n- `priority = High` — only high-priority issues\n- `labels = \"vip\"` — only issues tagged `vip`\n- `project = \"SUPPORT\" AND status != Done` — combine with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build a filter visually, then copy the query here.": "Narrow down which issues to watch. Leave empty to watch every issue in your Jira.\n\nReady-to-use examples:\n\n- `project = \"SUPPORT\"` — only the Support project\n- `priority = High` — only high-priority issues\n- `labels = \"vip\"` — only issues tagged `vip`\n- `project = \"SUPPORT\" AND status != Done` — combine with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build a filter visually, then copy the query here.",
133
+ "Narrow down which issues to watch. Leave empty to watch every issue in your Jira.\n\nReady-to-use examples:\n\n- `project = \"SUPPORT\"` — only the Support project\n- `issuetype = Bug` — only bugs\n- `labels = \"screenshot-needed\"` — only issues tagged `screenshot-needed`\n- `project = \"SUPPORT\" AND status != Done` — combine with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build a filter visually, then copy the query here.": "Narrow down which issues to watch. Leave empty to watch every issue in your Jira.\n\nReady-to-use examples:\n\n- `project = \"SUPPORT\"` — only the Support project\n- `issuetype = Bug` — only bugs\n- `labels = \"screenshot-needed\"` — only issues tagged `screenshot-needed`\n- `project = \"SUPPORT\" AND status != Done` — combine with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build a filter visually, then copy the query here."
115
134
  }
package/src/i18n/zh.json CHANGED
@@ -22,6 +22,7 @@
22
22
  "Delete Issue Comment": "Delete Issue Comment",
23
23
  "Markdown to Jira format": "Markdown to Jira format",
24
24
  "Get Issue": "Get Issue",
25
+ "Transition Issue": "Transition Issue",
25
26
  "Custom API Call": "自定义 API 呼叫",
26
27
  "Creates a new issue in a project.": "Creates a new issue in a project.",
27
28
  "Updates an existing issue.": "Updates an existing issue.",
@@ -38,6 +39,7 @@
38
39
  "Deletes a comment on a specific issue.": "Deletes a comment on a specific issue.",
39
40
  "Convert Markdown-formatted text to Jira's ADF syntax for use in comments and descriptions etc": "Convert Markdown-formatted text to Jira's ADF syntax for use in comments and descriptions etc",
40
41
  "Get issue data.": "Get issue data.",
42
+ "Moves an issue to a new status by executing a workflow transition.": "Moves an issue to a new status by executing a workflow transition.",
41
43
  "Make a custom API call to a specific endpoint": "将一个自定义 API 调用到一个特定的终点",
42
44
  "Project ID or Key": "Project ID or Key",
43
45
  "Issue Type": "Issue Type",
@@ -46,7 +48,10 @@
46
48
  "Issue ID or Key": "Issue ID or Key",
47
49
  "Status": "状态",
48
50
  "Keyword": "Keyword",
51
+ "Markdown": "Markdown",
49
52
  "JQL": "JQL",
53
+ "Fields to Return": "Fields to Return",
54
+ "Map Field Names": "Map Field Names",
50
55
  "Max Results": "Max Results",
51
56
  "Sanitize JQL": "Sanitize JQL",
52
57
  "Assignee": "Assignee",
@@ -63,8 +68,8 @@
63
68
  "Limit": "Limit",
64
69
  "Markdown text": "Markdown text",
65
70
  "Expand": "Expand",
66
- "Map Field Names": "Map Field Names",
67
71
  "Map Transition Names": "Map Transition Names",
72
+ "Transition": "Transition",
68
73
  "Method": "方法",
69
74
  "Headers": "信头",
70
75
  "Query Parameters": "查询参数",
@@ -75,7 +80,10 @@
75
80
  "Timeout (in seconds)": "超时(秒)",
76
81
  "Follow redirects": "Follow redirects",
77
82
  "https://developer.atlassian.com/cloud/jira/platform/apis/document/structure": "https://developer.atlassian.com/cloud/jira/platform/apis/document/structure",
78
- "The JQL query to use in the search": "The JQL query to use in the search",
83
+ "Fetching a large number of issues without specifying **Fields to Return** may exceed your flow's memory limits. Use field selection to reduce payload size.": "Fetching a large number of issues without specifying **Fields to Return** may exceed your flow's memory limits. Use field selection to reduce payload size.",
84
+ "The JQL query to use in search (Tip: Use single quotes for strings/dates)": "The JQL query to use in search (Tip: Use single quotes for strings/dates)",
85
+ "List of exact Jira Field IDs to return (e.g., 'summary', 'customfield_10016').\nSpecial commands:\n- Use *all for every field.\n- Use *navigable for standard fields (default).\n- Prefix with a minus to exclude (e.g., -description).\nExample: *all and -comment returns everything except comments.": "List of exact Jira Field IDs to return (e.g., 'summary', 'customfield_10016').\nSpecial commands:\n- Use *all for every field.\n- Use *navigable for standard fields (default).\n- Prefix with a minus to exclude (e.g., -description).\nExample: *all and -comment returns everything except comments.",
86
+ "Map human readable names to Fields in the output.\nNotes:\n- If there are fields with the same name, they may be overridden.": "Map human readable names to Fields in the output.\nNotes:\n- If there are fields with the same name, they may be overridden.",
79
87
  "Maximum number of results": "Maximum number of results",
80
88
  "Include additional information about the issue in the response": "Include additional information about the issue in the response",
81
89
  "Map human readable names to Fields, Rendered Fields, Schema and Edit Meta.\nNotes:\n- This would implicitly add \"names\" to the expand field\n- If there are fields with the same name, they may be overridden": "Map human readable names to Fields, Rendered Fields, Schema and Edit Meta.\nNotes:\n- This would implicitly add \"names\" to the expand field\n- If there are fields with the same name, they may be overridden",
@@ -103,8 +111,24 @@
103
111
  "New Issue": "New Issue",
104
112
  "Updated Issue": "Updated Issue",
105
113
  "Updated Issue Status": "Updated Issue Status",
114
+ "New Comment": "New Comment",
115
+ "Issue Assigned": "Issue Assigned",
116
+ "New Attachment on Issue": "New Attachment on Issue",
106
117
  "Triggers when a new issue is created": "Triggers when a new issue is created",
107
118
  "Triggers when an issue is updated": "Triggers when an issue is updated",
108
119
  "Triggers when an issue status is updated": "Triggers when an issue status is updated",
109
- "Use to filter issues watched": "Use to filter issues watched"
120
+ "Fires whenever someone adds a new comment to a Jira issue. Great for getting notified in Slack or Teams, syncing customer replies, or reacting to feedback automatically.": "Fires whenever someone adds a new comment to a Jira issue. Great for getting notified in Slack or Teams, syncing customer replies, or reacting to feedback automatically.",
121
+ "Fires when a Jira issue is assigned to someone. Use it to ping people in Slack/Teams the moment work lands on them, auto-create a to-do when tickets hit your queue, or track hand-offs between teammates.": "Fires when a Jira issue is assigned to someone. Use it to ping people in Slack/Teams the moment work lands on them, auto-create a to-do when tickets hit your queue, or track hand-offs between teammates.",
122
+ "Fires when a file is attached to a Jira issue. Great for auto-saving screenshots to Google Drive, forwarding customer uploads to support tools, or archiving documents in S3.": "Fires when a file is attached to a Jira issue. Great for auto-saving screenshots to Google Drive, forwarding customer uploads to support tools, or archiving documents in S3.",
123
+ "Only watch these issues (optional)": "Only watch these issues (optional)",
124
+ "Auto-fix the filter": "Auto-fix the filter",
125
+ "Only when assigned to me": "Only when assigned to me",
126
+ "Assignee (optional)": "Assignee (optional)",
127
+ "Use to filter issues watched": "Use to filter issues watched",
128
+ "Leave empty to watch comments on **every** issue in your Jira.\n\nTo narrow it down, paste a Jira filter here. A few ready-to-use examples:\n\n- `project = \"SUPPORT\"` — only issues in the Support project\n- `assignee = currentUser()` — only issues assigned to you\n- `status != Done` — skip closed issues\n- `labels = \"vip\"` — only issues tagged `vip`\n- `project = \"SUPPORT\" AND priority = High` — combine conditions with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build the filter visually, ": "Leave empty to watch comments on **every** issue in your Jira.\n\nTo narrow it down, paste a Jira filter here. A few ready-to-use examples:\n\n- `project = \"SUPPORT\"` — only issues in the Support project\n- `assignee = currentUser()` — only issues assigned to you\n- `status != Done` — skip closed issues\n- `labels = \"vip\"` — only issues tagged `vip`\n- `project = \"SUPPORT\" AND priority = High` — combine conditions with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build the filter visually, then copy the query here.",
129
+ "Keep this on. If your filter references something you can't access (a private project, a deleted field), Jira will automatically clean it up instead of erroring.": "Keep this on. If your filter references something you can't access (a private project, a deleted field), Jira will automatically clean it up instead of erroring.",
130
+ "Only trigger when the issue is assigned to the user who set up this connection. Overrides the Assignee field below.": "Only trigger when the issue is assigned to the user who set up this connection. Overrides the Assignee field below.",
131
+ "Pick a teammate to watch. Leave empty to trigger on assignments to anyone. Ignored if \"Only when assigned to me\" is checked.": "Pick a teammate to watch. Leave empty to trigger on assignments to anyone. Ignored if \"Only when assigned to me\" is checked.",
132
+ "Narrow down which issues to watch. Leave empty to watch every issue in your Jira.\n\nReady-to-use examples:\n\n- `project = \"SUPPORT\"` — only the Support project\n- `priority = High` — only high-priority issues\n- `labels = \"vip\"` — only issues tagged `vip`\n- `project = \"SUPPORT\" AND status != Done` — combine with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build a filter visually, then copy the query here.": "Narrow down which issues to watch. Leave empty to watch every issue in your Jira.\n\nReady-to-use examples:\n\n- `project = \"SUPPORT\"` — only the Support project\n- `priority = High` — only high-priority issues\n- `labels = \"vip\"` — only issues tagged `vip`\n- `project = \"SUPPORT\" AND status != Done` — combine with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build a filter visually, then copy the query here.",
133
+ "Narrow down which issues to watch. Leave empty to watch every issue in your Jira.\n\nReady-to-use examples:\n\n- `project = \"SUPPORT\"` — only the Support project\n- `issuetype = Bug` — only bugs\n- `labels = \"screenshot-needed\"` — only issues tagged `screenshot-needed`\n- `project = \"SUPPORT\" AND status != Done` — combine with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build a filter visually, then copy the query here.": "Narrow down which issues to watch. Leave empty to watch every issue in your Jira.\n\nReady-to-use examples:\n\n- `project = \"SUPPORT\"` — only the Support project\n- `issuetype = Bug` — only bugs\n- `labels = \"screenshot-needed\"` — only issues tagged `screenshot-needed`\n- `project = \"SUPPORT\" AND status != Done` — combine with `AND`\n\nNot sure what to write? Open Jira → Filters → Advanced search, build a filter visually, then copy the query here."
110
134
  }