Skip to content

[NoQA][Business Central][R3] Change phrasing for sync reimbursed reports feature - #104429

Merged
NikkiWines merged 2 commits into
mainfrom
francois-sync-reimbursement-phrasing
Oct 20, 2026
Merged

NikkiWines merged 2 commits into
mainfrom
francois-sync-reimbursement-phrasing

Conversation

@francoisl

Copy link
Copy Markdown
Contributor

Explanation of Change

The Business Central integration won't be creating "bills" for reimbursement syncing, yet the text for the feature was copied from other integrations that do, and it makes little sense at the moment. This essentially replaces "bill" with "journal". Suggestions are welcome because I'm not sure if we also need to update the "Choose where to pay bills from" sentence - from a customer's point of view, is the bill here the expense report?

Fixed Issues

Part of https://github.com/Expensify/Expensify/issues/686634

Tests

  1. Connect a policy to BC
  2. Open the ⚙️ Advanced menu
  3. Read the text under the "Sync reimbursed reports" option
  • Verify that no errors appear in the JS console

QA Steps

N/A

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I verified any copy / text that was added to the app is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

MacOS: Chrome / Safari image

@francoisl francoisl self-assigned this Oct 20, 2026
@francoisl
francoisl requested review from a team as code owners October 20, 2026 01:06
@melvin-bot
melvin-bot Bot requested review from garrettmknight and removed request for a team October 20, 2026 01:06
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 20, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-20T01:09:29.694638Z c16028c PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@melvin-bot
melvin-bot Bot requested review from arosiclair and removed request for a team October 20, 2026 01:07
@melvin-bot

melvin-bot Bot commented Oct 20, 2026

Copy link
Copy Markdown

@arosiclair Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@francoisl

Copy link
Copy Markdown
Contributor Author

No C+ review needed for this

@OSBotify

Copy link
Copy Markdown
Contributor

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

View the translation diff
diff --git a/src/languages/de.ts b/src/languages/de.ts
index aff85e69..57361655 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -9316,9 +9316,9 @@ Fügen Sie weitere Ausgabelimits hinzu, um den Cashflow Ihres Unternehmens zu sc
                 exportToNextOpenPeriodDescription:
                     'Wenn ein Bericht auf eine geschlossene Periode in Dynamics 365 Business Central datiert ist, wird er in die nächste offene Periode exportiert.',
                 syncReimbursedReports: 'Erstattete Berichte synchronisieren',
-                syncReimbursedReportsDescription: 'Wenn ein Bericht per ACH bezahlt wird, wird in diesem Konto eine Rechnungszahlung erstellt.',
+                syncReimbursedReportsDescription: 'Wenn ein Bericht per ACH bezahlt wird, wird in diesem Konto eine allgemeine Journalzeile erzeugt.',
                 reimbursementBankAccount: {
-                    label: 'Rechnungskonto',
+                    label: 'Zahlungskonto',
                     description: 'Wählen Sie aus, von wo Sie Rechnungen bezahlen möchten, und wir erstellen die Zahlung in Dynamics 365 Business Central.',
                 },
                 syncExpensifyCardSettlements: 'Expensify Karte-Abrechnungen synchronisieren',
diff --git a/src/languages/el.ts b/src/languages/el.ts
index cda27383..62cf56fb 100644
--- a/src/languages/el.ts
+++ b/src/languages/el.ts
@@ -9479,9 +9479,9 @@ ${reportName}`,
                 exportToNextOpenPeriod: 'Εξαγωγή στην επόμενη ανοικτή περίοδο',
                 exportToNextOpenPeriodDescription: 'Όταν μια αναφορά έχει ημερομηνία σε κλειστή περίοδο του Dynamics 365 Business Central, εξάγεται στην επόμενη ανοιχτή περίοδο.',
                 syncReimbursedReports: 'Συγχρονισμός αποζημιωμένων αναφορών',
-                syncReimbursedReportsDescription: 'Όταν μια αναφορά πληρωθεί μέσω ACH, θα δημιουργηθεί μια πληρωμή λογαριασμού σε αυτόν τον λογαριασμό.',
+                syncReimbursedReportsDescription: 'Όταν μια αναφορά εξοφλείται μέσω ACH, θα δημιουργείται μια γραμμή γενικής λογιστικής εγγραφής σε αυτόν τον λογαριασμό.',
                 reimbursementBankAccount: {
-                    label: 'Λογαριασμός πληρωμής λογαριασμών',
+                    label: 'Τραπεζικός λογαρια​σμός πληρωμών',
                     description: 'Επιλέξτε από πού θα πληρώνονται οι λογαριασμοί και θα δημιουργήσουμε την πληρωμή στο Dynamics 365 Business Central.',
                 },
                 syncExpensifyCardSettlements: 'Συγχρονισμός διακανονισμών Κάρτας Expensify',
diff --git a/src/languages/es.ts b/src/languages/es.ts
index d7ad5a7a..77379dd3 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -9133,11 +9133,8 @@ ${reportName}`,
                 exportToNextOpenPeriod: 'Exportar al siguiente período abierto',
                 exportToNextOpenPeriodDescription: 'Cuando la fecha de un informe cae en un período cerrado de Dynamics 365 Business Central, se exporta al siguiente período abierto.',
                 syncReimbursedReports: 'Sincronizar informes reembolsados',
-                syncReimbursedReportsDescription: 'Cuando un informe se paga mediante ACH, se generará un pago de factura en esta cuenta.',
-                reimbursementBankAccount: {
-                    label: 'Cuenta de pago de facturas',
-                    description: 'Elige desde dónde pagar las facturas y crearemos el pago en Dynamics 365 Business Central.',
-                },
+                syncReimbursedReportsDescription: 'Cuando un informe se pague mediante ACH, se generará un asiento de diario general en esta cuenta.',
+                reimbursementBankAccount: {label: 'Cuenta bancaria de pago', description: 'Elige desde dónde pagar las facturas y crearemos el pago en Dynamics 365 Business Central.'},
                 syncExpensifyCardSettlements: 'Sincronizar liquidaciones de la Tarjeta Expensify',
                 settlementsBankAccount: {
                     label: 'Cuenta de liquidación de la Tarjeta Expensify',
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index a089625e..96b6f74b 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -9343,9 +9343,9 @@ Ajoutez davantage de règles de dépenses pour protéger la trésorerie de l’e
                 exportToNextOpenPeriodDescription:
                     'Lorsqu’une note de frais est datée dans une période clôturée de Dynamics 365 Business Central, elle est exportée vers la période ouverte suivante.',
                 syncReimbursedReports: 'Synchroniser les notes de frais remboursées',
-                syncReimbursedReportsDescription: 'Lorsqu’une note de frais est payée par virement ACH, un paiement de facture sera généré sur ce compte.',
+                syncReimbursedReportsDescription: 'Lorsqu’une note de frais est payée par ACH, une écriture de journal général sera générée dans ce compte.',
                 reimbursementBankAccount: {
-                    label: 'Compte de paiement des factures',
+                    label: 'Compte bancaire de paiement',
                     description: 'Choisissez d’où payer les factures et nous créerons le paiement dans Dynamics 365 Business Central.',
                 },
                 syncExpensifyCardSettlements: 'Synchroniser les règlements de Carte Expensify',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 6eb2a2e9..e3fbfc3c 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -9258,11 +9258,8 @@ Aggiungi altre regole di spesa per proteggere il flusso di cassa aziendale.`,
                 exportToNextOpenPeriod: 'Esporta nel prossimo periodo aperto',
                 exportToNextOpenPeriodDescription: 'Quando un report ha una data in un periodo chiuso di Dynamics 365 Business Central, viene esportato nel periodo aperto successivo.',
                 syncReimbursedReports: 'Sincronizza i report rimborsati',
-                syncReimbursedReportsDescription: 'Quando un resoconto viene pagato tramite ACH, verrà generato un pagamento di fattura in questo conto.',
-                reimbursementBankAccount: {
-                    label: 'Conto per il pagamento delle bollette',
-                    description: 'Scegli da dove pagare le fatture e creeremo il pagamento in Dynamics 365 Business Central.',
-                },
+                syncReimbursedReportsDescription: 'Quando un report viene pagato tramite ACH, in questo conto verrà generata una riga di prima nota generale.',
+                reimbursementBankAccount: {label: 'Conto bancario di pagamento', description: 'Scegli da dove pagare le fatture e creeremo il pagamento in Dynamics 365 Business Central.'},
                 syncExpensifyCardSettlements: 'Sincronizza le liquidazioni della Carta Expensify',
                 settlementsBankAccount: {
                     label: 'Conto di regolamento Carta Expensify',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 58a13bfc..dad8171d 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -9133,11 +9133,8 @@ ${reportName}`,
                 exportToNextOpenPeriod: '次の未締め期間にエクスポート',
                 exportToNextOpenPeriodDescription: 'レポートの日付が Dynamics 365 Business Central の締め済み期間にある場合、次の未締め期間にエクスポートします。',
                 syncReimbursedReports: '精算済みレポートを同期',
-                syncReimbursedReportsDescription: 'レポートが ACH で支払われると、この口座に支払伝票が作成されます。',
-                reimbursementBankAccount: {
-                    label: '請求支払用口座',
-                    description: '請求書の支払い元を選択すると、Dynamics 365 Business Central 内に支払いを作成します。',
-                },
+                syncReimbursedReportsDescription: 'レポートが ACH で支払われると、この勘定科目に総勘定元帳の仕訳行が作成されます。',
+                reimbursementBankAccount: {label: '支払用銀行口座', description: '請求書の支払い元を選択すると、Dynamics 365 Business Central 内に支払いを作成します。'},
                 syncExpensifyCardSettlements: 'Expensify カード清算を同期する',
                 settlementsBankAccount: {
                     label: 'Expensify カードの決済口座',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 55d382cb..98414394 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -9233,9 +9233,9 @@ er bestedingsregels toe om de kasstroom van het bedrijf te beschermen.`,
                 exportToNextOpenPeriodDescription:
                     'Als een rapport is gedateerd in een afgesloten periode in Dynamics 365 Business Central, wordt het geëxporteerd naar de volgende open periode.',
                 syncReimbursedReports: 'Vergoede rapporten synchroniseren',
-                syncReimbursedReportsDescription: 'Wanneer een rapport via ACH wordt betaald, wordt er in deze rekening een rekeningbetaling aangemaakt.',
+                syncReimbursedReportsDescription: 'Wanneer een rapport via ACH wordt betaald, wordt er in deze rekening een journaalpostregel aangemaakt.',
                 reimbursementBankAccount: {
-                    label: 'Rekening voor het betalen van rekeningen',
+                    label: 'Betaalbankrekening',
                     description: 'Kies van waar je rekeningen wilt betalen en we maken de betaling aan in Dynamics 365 Business Central.',
                 },
                 syncExpensifyCardSettlements: 'Expensify Kaartafrekeningen synchroniseren',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 17a89282..ccd5a07e 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -9248,9 +9248,9 @@ Dodaj więcej zasad wydatków, żeby chronić płynność finansową firmy.`,
                 exportToNextOpenPeriod: 'Eksportuj do następnego otwartego okresu',
                 exportToNextOpenPeriodDescription: 'Gdy raport ma datę w zamkniętym okresie w Dynamics 365 Business Central, zostanie wyeksportowany do następnego otwartego okresu.',
                 syncReimbursedReports: 'Synchronizuj rozliczone raporty',
-                syncReimbursedReportsDescription: 'Gdy raport zostanie opłacony przez ACH, na tym koncie zostanie wygenerowana płatność rachunku.',
+                syncReimbursedReportsDescription: 'Gdy raport zostanie opłacony przez ACH, w tym koncie zostanie wygenerowany wiersz dziennika ogólnego.',
                 reimbursementBankAccount: {
-                    label: 'Konto do opłacania rachunków',
+                    label: 'Rachunek bankowy do płatności',
                     description: 'Wybierz, z którego konta chcesz opłacać rachunki, a my utworzymy płatność w Dynamics 365 Business Central.',
                 },
                 syncExpensifyCardSettlements: 'Synchronizuj rozliczenia Karty Expensify',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 274d6290..99456040 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -9238,9 +9238,9 @@ Adicione mais regras de gasto para proteger o fluxo de caixa da empresa.`,
                 exportToNextOpenPeriod: 'Exportar para o próximo período em aberto',
                 exportToNextOpenPeriodDescription: 'Quando um relatório tem data em um período fechado do Dynamics 365 Business Central, ele é exportado para o próximo período aberto.',
                 syncReimbursedReports: 'Sincronizar relatórios reembolsados',
-                syncReimbursedReportsDescription: 'Quando um relatório for pago via ACH, um pagamento de conta será gerado nesta conta.',
+                syncReimbursedReportsDescription: 'Quando um relatório é pago via ACH, uma linha de lançamento contábil será gerada nesta conta.',
                 reimbursementBankAccount: {
-                    label: 'Conta de pagamento de contas',
+                    label: 'Conta bancária de pagamento',
                     description: 'Escolha de onde pagar as contas e nós vamos criar o pagamento no Dynamics 365 Business Central.',
                 },
                 syncExpensifyCardSettlements: 'Sincronizar liquidações do Cartão Expensify',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 79dafb43..97462175 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -8892,11 +8892,8 @@ ${reportName}`,
                 exportToNextOpenPeriod: '导出到下一个未结会计期间',
                 exportToNextOpenPeriodDescription: '当报告日期位于 Dynamics 365 Business Central 的已关闭期间时,将其导出到下一个未关闭期间。',
                 syncReimbursedReports: '同步已报销报表',
-                syncReimbursedReportsDescription: '当报表通过 ACH 支付时,将在此账户中生成一笔账单付款。',
-                reimbursementBankAccount: {
-                    label: '账单支付账户',
-                    description: '选择从哪里支付账单,我们会在 Dynamics 365 Business Central 中创建付款。',
-                },
+                syncReimbursedReportsDescription: '当报表通过 ACH 支付时,将在此科目中生成一条普通日记账分录。',
+                reimbursementBankAccount: {label: '付款银行账户', description: '选择从哪里支付账单,我们会在 Dynamics 365 Business Central 中创建付款。'},
                 syncExpensifyCardSettlements: '同步 Expensify 卡结算',
                 settlementsBankAccount: {
                     label: 'Expensify 卡结算账户',

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply 😉

View workflow run

NikkiWines

This comment was marked as outdated.

@NikkiWines NikkiWines left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh actually @francoisl we do need the translations for this

@arosiclair

Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified any copy / text that was added to the app is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
Android: mWeb Chrome
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari

@francoisl

Copy link
Copy Markdown
Contributor Author

we do need the translations for this

Yes I was waiting for approval on the english text first, going to apply it now

@francoisl
francoisl requested a review from NikkiWines October 20, 2026 18:22
@NikkiWines
NikkiWines merged commit aff6ccb into main Oct 20, 2026
43 of 44 checks passed
@NikkiWines
NikkiWines deleted the francois-sync-reimbursement-phrasing branch October 20, 2026 20:32
@OSBotify

Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@github-actions

Copy link
Copy Markdown
Contributor

🚧 NikkiWines has triggered a test Expensify/App build. You can view the workflow run here.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/NikkiWines in version: 9.5.16-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@MelvinBot

Copy link
Copy Markdown
Contributor

No help site update needed. This PR only rewords two labels in the Dynamics 365 Business Central integration, which is still behind the BUSINESS_CENTRAL beta and has no public help article that names these labels.


view run

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants