Skip to content

[$250] Web-Expense details-distance and rate menu items are shown after created unreported expense #96343

Closed

Description

@lanitochka17

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Version Number: undefined
Reproducible in staging?: Yes
Reproducible in production?: (https://github.com/Expensify/Expensify/issues/492149)
If this was caught during regression testing, add the test name, ID and link from BrowserStack: undefined
Email or phone of affected tester (no customers): undefined
Issue reported by: Applause Internal Team
Bug source: undefined
Device used: undefined
App Component: undefined

Action Performed:

  1. Go to staging.expensify.com
  2. Create an unreported distance expense (Report field is none) with the following waypoints:
  • Start - 88 kearny street
  • Stop - Golden gate bridge
  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Go to transaction thread of the expense created in Step 2.

Expected Result:

distance and rate menu items are not shown

Actual Result:

distance and rate menu are shown

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari

Screenshots/Videos

Bug7194186_1782728953562.1781609744400_distance.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jul 16, 2026
  2. MelvinBot commented on Jul 16, 2026

    @MelvinBot
    Contributor

    Proposal

    What is the root cause of that problem?

    The Distance and Rate menu items are gated only by the transaction type — with no check for whether the expense is reported or unreported.

    In MoneyRequestView.tsx:1247, the block that renders the Distance + Rate rows is shown whenever the transaction is a distance request:

    {isManualDistanceRequest || isGPSDistanceRequest || isOdometerDistanceRequest || (isMapDistanceRequest && transaction?.comment?.waypoints) ? (distanceRequestFields) : (...merchant...)}
    

    Every other conditionally-visible field checks isExpenseUnreported for visibility — see MoneyRequestView.tsx:486-504 (shouldShowCategory, shouldShowTag, shouldShowBillable, shouldShowReimbursable all gate on isPolicyExpenseChat || isExpenseUnreported plus a policy/enablement condition). The distance/rate block has no such flag, so for an unreported distance expense it falls through the same path as a reported one and renders.

    The canEditDistance / canEditDistanceRate flags (lines 432-459) only control interactivity (right chevron / editability), not whether the row is shown — so the rows appear even when non-editable. This block appears to have simply been missed when the unreported-expense feature landed.

    What changes do you think we should make in order to solve the problem?

    Add an unreported-aware visibility flag alongside the other shouldShow* flags (near line 486) and require it in the ternary at line 1247 before rendering distanceRequestFields:

    • Introduce shouldShowDistanceRate that suppresses the Distance/Rate block when isExpenseUnreported (isExpenseUnreported is already computed at line 233 and means "report field none / self DM").
    • When it's a distance request but shouldShowDistanceRate is false, render nothing (or the merchant fallback, per design).

    ⚠️ One decision to confirm with the feature owner: whether to hide the rows for all unreported distance expenses, or to keep them for P2P / track-expense distance where a rate is still meaningful (isP2PDistanceRequest / isTrackExpense). The bug report says the rows should not be shown, which points to the first option, but this should be confirmed so we don't regress a valid case.

    Related issues

    Investigation details & evidence
    • isExpenseUnreported is defined in TransactionUtils/index.ts:3004 as transaction?.reportID === CONST.REPORT.UNREPORTED_REPORT_ID — exactly "Report field is none".
    • distanceRequestFields (the Distance + Rate MenuItemWithTopDescriptions) is defined at MoneyRequestView.tsx:937-1047; interactive/shouldShowRightIcon use canEditDistance/canEditDistanceRate, confirming those flags only affect interactivity, not presence.
    • Alternative considered: the rows might have been intended to show read-only for unreported expenses. Rejected because the bug report explicitly states they should not be shown, and the consistent sibling pattern (Category/Tag/Billable/Reimbursable gate visibility on isExpenseUnreported) indicates the distance/rate block was just never updated.

    Confidence: High — code evidence directly shows the missing gate and a clear peer pattern. No production logs needed (deterministic UI-rendering logic).


    Next Steps for Contributor+ team:
    To accept: @MelvinBot implement this to create a draft PR.
    To refine: @MelvinBot <your feedback>
    To reject: Explain why you are rejecting Melvin's proposal.

  3. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Jul 16, 2026
  4. yusufdeveloper2903 commented on Jul 16, 2026

    @yusufdeveloper2903
    Contributor

    Proposal

    What is the root cause of that problem?

    The distance and rate menu items in the expense details view are being shown based solely on whether the expense is a distance request, without checking if the expense belongs to a report. For an unreported expense (where reportID is empty or none), these menu items should be hidden since they're not applicable in that context.

    What changes do you think we should make in order to solve the problem?

    I'd look at the transaction details page where distance/rate menu items are conditionally rendered. The condition likely checks isDistanceRequest but doesn't also verify the expense is tied to a report.

    In src/pages/TransactionDuplicate/TransactionDetails.tsx or more likely src/pages/EditRequestPage.tsx or the relevant transaction detail component, the fix would be:

    - const shouldShowDistanceMenuItems = isDistanceRequest;
    + const shouldShowDistanceMenuItems = isDistanceRequest && !!reportID;

    Or wherever the menu items are rendered:

    - {isDistanceRequest && (
    + {isDistanceRequest && !!report?.reportID && (
        <>
          <DistanceMenuItem ... />
          <RateMenuItem ... />
        </>
      )}

    This ensures distance and rate menu items are only displayed when the expense is both a distance request and has an associated report, hiding them for unreported/draft expenses.

    What alternative solutions did you explore?

    An alternative would be to check !isEmptyObject(report) instead of !!reportID, which is more robust since an empty report object would also indicate an unreported expense. However, checking !!reportID is simpler and more direct for this use case.

  5. aswin-s commented on Jul 16, 2026

    @aswin-s
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    On Web, when a user creates an unreported distance expense (Report = none) and opens its transaction thread from the workspace chat, the details view still renders the "Distance" and "Rate" menu items. Expected: for an unreported distance expense viewed from the workspace-chat transaction thread, the distance and rate rows should not be shown.

    What is the root cause of that problem?

    The gate that decides whether to render the distance/rate rows in src/components/ReportActionItem/MoneyRequestView.tsx:1247 only inspects the transaction's iouRequestType (isManualDistanceRequest || isGPSDistanceRequest || isOdometerDistanceRequest || (isMapDistanceRequest && transaction?.comment?.waypoints)) and never considers whether the transaction is unreported. The iouRequestType flags at src/components/ReportActionItem/MoneyRequestView.tsx:325-328 are true for the freshly-created unreported distance transaction, so the branch at line 1247 renders distanceRequestFields (the Distance row at line 937 and the Rate row at line 988) even though transaction?.reportID === CONST.REPORT.UNREPORTED_REPORT_ID. The same file already treats the unreported state as a suppression signal for other conditional UI at line 653 (transaction?.reportID !== CONST.REPORT.UNREPORTED_REPORT_ID is part of shouldShowConvertedAmount), but that check was never applied to the distance/rate gate.

    What changes do you think we should make in order to solve the problem?

    1. In src/components/ReportActionItem/MoneyRequestView.tsx around line 1247, extend the gate so distanceRequestFields is only rendered when the transaction is not unreported — e.g. compute const isUnreportedTransaction = transaction?.reportID === CONST.REPORT.UNREPORTED_REPORT_ID; and change the condition to (!isUnreportedTransaction) && (isManualDistanceRequest || isGPSDistanceRequest || isOdometerDistanceRequest || (isMapDistanceRequest && transaction?.comment?.waypoints)), so unreported distance expenses fall through to the Merchant branch like non-distance expenses.
    2. Reuse the same UNREPORTED_REPORT_ID check that already gates shouldShowConvertedAmount at line 653, rather than introducing a new constant, so the two suppression rules stay consistent.
    3. Verify the change against the four distance sub-types (DISTANCE_MANUAL, DISTANCE_GPS, DISTANCE_ODOMETER, DISTANCE_MAP) using the flags declared at lines 325-328 — all four paths must fall through when the transaction is unreported.
    4. Sanity-check that the corresponding edit/route handlers at lines 439 (EDIT_REQUEST_FIELD.DISTANCE) and 452 (EDIT_REQUEST_FIELD.DISTANCE_RATE) either become unreachable or are also guarded, so no orphan navigation into the distance/rate edit steps can happen when there is no owning report.

    What alternative solutions did you explore? (Optional)

  6. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jul 16, 2026
  7. ahmdshrif commented on Jul 16, 2026

    @ahmdshrif
    Contributor

    🚨 Edited by proposal-police: This proposal was edited at 2026-07-16 19:04:08 UTC.

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    A distance expense created unreported in OldDot (Report field = none) shows the Distance and Rate menu items when its transaction thread is opened in NewDot. They should not be shown — the expense should render like a plain expense (merchant/amount/date).

    What is the root cause of that problem?

    The structural cause: MoneyRequestView decides to render the distance field set purely from the transaction's type, but never checks that it has the rate context those fields need. A legacy OldDot unreported expense has the type but not the context.

    The chain:

    1. The Distance/Rate rows are gated only on request-type predicates plus a waypoints check:
      {isManualDistanceRequest || isGPSDistanceRequest || isOdometerDistanceRequest || (isMapDistanceRequest && transaction?.comment?.waypoints) ? (
      distanceRequestFields
      ) : (
    2. Since PR #88289, every one of those predicates trusts the server-stamped transaction.iouRequestType alone — the old saved-transaction heuristics were deleted:
      function isDistanceRequest(transaction: OnyxEntry<Transaction>): boolean {
      const requestType = transaction?.iouRequestType;
      return requestType === CONST.IOU.REQUEST_TYPE.DISTANCE || isDistanceExpenseType(requestType);
      }
      function isDistanceTypeRequest(transaction: OnyxEntry<Transaction>): boolean {
      return transaction?.iouRequestType === CONST.IOU.REQUEST_TYPE.DISTANCE;
      }
      /**
      * Compare two waypoint collections by their addresses only (ignoring coordinates/names), which is
      * the meaningful signal for "did the user change the route?". Numeric fields like lat/lng can drift
      * due to rounding in transaction backups, so they're excluded.
      */
      function haveWaypointAddressesChanged(oldWaypoints: WaypointCollection | undefined, newWaypoints: WaypointCollection | undefined): boolean {
      const toAddresses = (collection: WaypointCollection | undefined) =>
      Object.fromEntries(Object.entries(collection ?? {}).map(([key, waypoint]) => [key, waypoint && 'address' in waypoint ? waypoint.address : undefined]));
      return !deepEqual(toAddresses(oldWaypoints), toAddresses(newWaypoints));
      }
      function isMapDistanceRequest(transaction: OnyxEntry<Transaction>): boolean {
      return transaction?.iouRequestType === CONST.IOU.REQUEST_TYPE.DISTANCE_MAP;
      }
      function isGPSDistanceRequest(transaction: OnyxEntry<Transaction>): boolean {
      return transaction?.iouRequestType === CONST.IOU.REQUEST_TYPE.DISTANCE_GPS;
      }
      function isManualDistanceRequest(transaction: OnyxEntry<Transaction>): boolean {
      return transaction?.iouRequestType === CONST.IOU.REQUEST_TYPE.DISTANCE_MANUAL;
      }
      function isOdometerDistanceRequest(transaction: OnyxEntry<Transaction>): boolean {
      return transaction?.iouRequestType === CONST.IOU.REQUEST_TYPE.DISTANCE_ODOMETER;
      }

      Nothing in NewDot ever wrote iouRequestType for this transaction (it was created in OldDot), so the server stamps it as a distance type and the gate passes.
    3. But the rate is unresolvable. The view resolves it from customUnitRateID against a policy:
      const {
      unit,
      rate,
      name: rateName,
      } = DistanceRequestUtils.getRate({
      transaction: updatedTransaction ?? transaction,
      policy: distanceOriginalPolicy ?? policy,
      personalPolicyOutputCurrency: personalPolicy?.outputCurrency,
      });
      const distance = getDistanceInMeters(transactionBackup ?? updatedTransaction ?? transaction, unit);
      — for an unreported expense that policy is just the user's default "policy for moving expenses" (
      // If the expense is unreported the policy should be the user's default policy, if the expense is a per diem request and is unreported
      // the policy should be the one where the per diem rates are enabled, otherwise it should be the expense's report policy
      if (isExpenseUnreported && !isPerDiemRequest) {
      policy = policyForMovingExpenses;
      policyID = policyForMovingExpensesID;
      ), which does not contain the OldDot rate ID.
    4. NewDot's own unreport flow avoids this exact hole by re-pointing customUnitRateID to _FAKE_P2P_ID_ (PR #81756), which isCustomUnitRateIDForP2P then recognizes:
      function isCustomUnitRateIDForP2P(transaction: OnyxInputOrEntry<Transaction>): boolean {
      return transaction?.comment?.customUnit?.customUnitRateID === CONST.CUSTOM_UNITS.FAKE_P2P_ID;
      }
      . An expense created unreported in OldDot never went through that flow, so it is a distance-typed transaction with no resolvable rate and no P2P marker.
    5. With isDistanceRequest && !rate, the view marks the rate out-of-policy (
      const isCustomUnitOutOfPolicy =
      (transactionViolations.some((violation) => violation.name === CONST.VIOLATIONS.CUSTOM_UNIT_OUT_OF_POLICY) || (isDistanceRequest && !rate)) && !isTrackExpense;
      ) and renders the nonsense "Rate out of policy" copy (
      if (isCustomUnitOutOfPolicy) {
      return translate('common.rateOutOfPolicy');
      }
      ) — for an expense that has no policy at all.

    One more trap: OldDot unreported transactions can arrive with reportID: '', while isExpenseUnreported only matches '0' (

    function isExpenseUnreported(transaction?: Transaction): transaction is UnreportedTransaction {
    return transaction?.reportID === CONST.REPORT.UNREPORTED_REPORT_ID;
    }
    ). ReportUtils already documents and handles both forms:
    const isUnreportedLegacyTransaction = !reportAction && (!transaction?.reportID || transaction?.reportID === CONST.REPORT.UNREPORTED_REPORT_ID);

    This explains every symptom: rows appear (type gate passes), the rate value is broken (no resolvable rate), and it only happens for the unreported OldDot case (a reported copy of the same expense resolves its rate through the report's policy; a NewDot unreported one resolves through _FAKE_P2P_ID_).

    What changes do you think we should make in order to solve the problem?

    In MoneyRequestView, render the distance field set only when we can actually resolve a rate for an unreported expense — otherwise fall back to the existing merchant row (the plain-expense presentation QA expects):

    const isUnreportedExpenseWithoutRate =
        (!transaction?.reportID || transaction?.reportID === CONST.REPORT.UNREPORTED_REPORT_ID) && !isP2PDistanceRequest && !rate;
    const shouldShowDistanceRequestFields =
        (isManualDistanceRequest || isGPSDistanceRequest || isOdometerDistanceRequest ||
            (isMapDistanceRequest && !!transaction?.comment?.waypoints)) && !isUnreportedExpenseWithoutRate;

    and use shouldShowDistanceRequestFields in the ternary at L1247. isP2PDistanceRequest already exists in the component (L285).

    Coverage: this is the single render site for these rows — MoneyRequestView is the shared details body for transaction threads on every platform and both narrow/wide layouts (no index.native variant exists). The amount row keeps showing because hasRoute is satisfied by customUnit.quantity (L1926-L1928), and the merchant fallback row renders the OldDot route merchant. It also closes the downstream hole where the Rate row would navigate to a rate editor that ReportUtils happily allows for unreported expenses but that has no valid rates to offer (L5276-L5282).

    Regression safety in one sentence: reported expenses (reportID set) and NewDot unreported distance expenses (_FAKE_P2P_ID_ → isP2PDistanceRequest) short-circuit the new condition to false, so nothing changes for them.

    Why the obvious spot-fix fails: adding && !isExpenseUnreported to the gate breaks NewDot's own unreported distance expenses — the unreport flow deliberately re-points them to the P2P rate so these rows keep working (PR #81756) — and it silently misses OldDot transactions whose reportID is '' rather than '0', so the bug survives for exactly the legacy case this issue is about.

    What alternative solutions did you explore? (Optional)

    1. Require non-empty waypoints in the gate (!isEmptyObject(transaction?.comment?.waypoints)) — incomplete: it only touches the map branch, and an OldDot expense with synced waypoints would still show a Distance row plus a bogus "Rate out of policy" row.
    2. Normalize legacy unreported expenses to _FAKE_P2P_ID_ at read time so the rows show a P2P rate — contradicts the expected result (rows hidden) and silently rewrites the expense's rate semantics.
    3. The true upstream source is that the server stamps a distance iouRequestType on OldDot-created unreported expenses without NewDot-usable rate data; the in-App gate above is the mergeable fix and remains correct even if the backend later normalizes this.
  8. samranahm commented on Jul 16, 2026

    @samranahm
    Contributor

    Proposal

    What is the root cause of that problem?

    On the transaction thread of an unreported distance expense, MoneyRequestView renders the "Distance" and "Rate" menu rows. Those rows are gated by whether the transaction is treated as a distance request, which is computed through TransactionUtils.isDistanceRequest (and the related isCustomUnit/rate helpers) inside MoneyRequestView.tsx.

    https://github.com/Expensify/App/blob/b69fd76a9ba7dd30e39464e5ea2c5fc7c659f360/src/components/ReportActionItem/MoneyRequestView.tsx

    The distance expense created on OldDot syncs into NewDot with the waypoint/route data still present on the transaction comment, so isDistanceRequest returns true even though the expense is unreported (its report field is none). Because that gate is based only on the transaction type and not on whether the expense is part of a report, the Distance and Rate rows render. The expected behavior is that these rows are hidden for an unreported expense, which is not part of a report and therefore has no policy distance rate context to display.

    https://github.com/Expensify/App/blob/b69fd76a9ba7dd30e39464e5ea2c5fc7c659f360/src/libs/TransactionUtils.ts

    So the gap: the row visibility depends only on "is this a distance transaction", while it should also account for "does this expense belong to a report".

    What changes do you think we should make in order to solve the problem?

    1. In MoneyRequestView.tsx, the Distance and Rate rows are shown when the transaction is a distance request. Extend that condition so the rows are hidden when the expense is unreported (no valid reportID).

    https://github.com/Expensify/App/blob/b69fd76a9ba7dd30e39464e5ea2c5fc7c659f360/src/components/ReportActionItem/MoneyRequestView.tsx

    const isReportedExpense = !!transaction?.reportID && transaction.reportID !== CONST.REPORT.UNREPORTED_REPORT_ID;
    const shouldShowDistanceRate = isDistanceRequest && isReportedExpense;

    Use shouldShowDistanceRate in place of the current distance-only check that gates both the distance row and the rate row. This keeps the rows for normal reported distance expenses while hiding them for unreported ones, which matches the expected result.

    1. Confirm the same unreported guard is applied to both the distance amount row and the rate row so they toggle together, since the issue reports both appearing.

    This fixes the root cause because visibility now depends on the expense actually belonging to a report, not just on the presence of leftover waypoint/route data synced from OldDot.

    What alternative solutions did you explore? (Optional)

    Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

  9. melvin-bot commented on Jul 16, 2026

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @rojiphil (External)

  10. changed the title [-]Web-Expense details-distance and rate menu items are shown after created unreported expense[/-] [+][$250] Web-Expense details-distance and rate menu items are shown after created unreported expense[/+] on Jul 16, 2026
  11. melvin-bot commented on Jul 16, 2026

    @melvin-bot
  12. nabi-ebrahimi commented on Jul 16, 2026

    @nabi-ebrahimi

    Proposal

    What is the root cause of that problem?

    Unreported OldDot distance expenses are stored as transactions with reportID === CONST.REPORT.UNREPORTED_REPORT_ID, and MoneyRequestView already detects that with isExpenseUnreportedTransactionUtils(transaction) ([source](https://github.com/Expensify/App/blob/main/src/components/ReportActionItem/MoneyRequestView.tsx#L229-L233)). However, the same component decides whether to render the Distance/Rate block only from the distance request type and waypoint shape ([source](https://github.com/Expensify/App/blob/main/src/components/ReportActionItem/MoneyRequestView.tsx#L323-L329)), then renders the Distance and Rate menu items unconditionally inside distanceRequestFields ([source](https://github.com/Expensify/App/blob/main/src/components/ReportActionItem/MoneyRequestView.tsx#L936-L990)) whenever the current inline condition is true ([source](https://github.com/Expensify/App/blob/main/src/components/ReportActionItem/MoneyRequestView.tsx#L1242-L1244)). Because that render condition does not exclude unreported expenses, an unreported distance expense with waypoints still shows both menu rows even though the expense has no report selected.

    There is also a related permission mismatch: canEditFieldOfMoneyRequest treats DISTANCE_RATE as editable for either an expense report or an unreported expense ([source](https://github.com/Expensify/App/blob/main/src/libs/ReportUtils.ts#L5265-L5270)), even though this UI should not expose distance/rate editing for unreported distance expenses.

    What changes do you think we should make in order to solve the problem?

    In MoneyRequestView, replace the inline distance-field render condition with a named boolean that preserves the existing distance-type checks but also requires !isExpenseUnreported. For example, only render distanceRequestFields when the transaction is a manual/GPS/odometer/map distance request and the transaction is not unreported. When that boolean is false, keep the existing fallback path so the details view does not show the Distance and Rate menu items for unreported distance expenses.

    In ReportUtils.canEditFieldOfMoneyRequest, remove the unreported-expense allowance from the DISTANCE_RATE branch, and explicitly prevent distance/rate edits for unreported expenses. That keeps the permission helper aligned with the UI: unreported expenses can still use the Report field move flow where allowed, but they should not expose Distance or Rate editing until they belong to a real report.

    What alternative solutions did you explore? (Optional)

    I considered only hiding the rows in MoneyRequestView, but that would leave canEditFieldOfMoneyRequest reporting distance-rate editability for unreported expenses in other callers. Updating both the visibility condition and the shared editability check keeps the behavior consistent.

  13. 35 remaining items

  14. melvin-bot commented on Aug 11, 2026

    @melvin-bot

    @rojiphil 10 days overdue. I'm getting more depressed than Marvin.

  15. melvin-bot commented on Aug 13, 2026

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  16. melvin-bot commented on Aug 13, 2026

    @melvin-bot

    @rojiphil this issue is now 4 weeks old, please consider:

    • Finding a contributor to fix the bug
    • Closing the issue if BZ has been unable to add the issue to a VIP or Wave project
    • If you have any questions, don't hesitate to start a discussion in #expensify-open-source

    Thanks!

  17. melvin-bot commented on Aug 13, 2026

    @melvin-bot

    @rojiphil 12 days overdue. Walking. Toward. The. Light...

  18. melvin-bot commented on Aug 17, 2026

    @melvin-bot

    This issue has not been updated in over 14 days. @rojiphil eroding to Weekly issue.

  19. melvin-bot commented on Aug 20, 2026

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  20. melvin-bot commented on Aug 27, 2026

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  21. rojiphil commented on Aug 27, 2026

    @rojiphil
    Contributor

    Requested in slack here to close this issue as the actual result looks to be the expected one.

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

Metadata

Metadata

Assignees

Labels

BugSomething is broken. Auto assigns a BugZero manager.ExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributorsWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions