Skip to content

Chat - Unable to add to group user when previously have offline conversation with #81693

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: v9.3.15-1
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/TR-4567/folder/13176684/41236589/1174435270?sort=-status_id
Email or phone of affected tester (no customers): gocemate+b21549011@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Windows 10/Chrome
App Component: Other

Action Performed:

  1. Login with new user
  2. Go offline
  3. Create a chat with existing user> Send a message
  4. Go online
  5. Go to FAB> Start chat
    6, Observe the RHP

Expected Result:

there should be Add to group button next to the user

Actual Result:

There is no Add to group button next to the user

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7069632_1770387633441.Recording__194.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @rojiphil

Activity

  1. added
    ExternalAdded to denote the issue can be worked on by a contributor
    BugSomething is broken. Auto assigns a BugZero manager.
    on Feb 6, 2026
  2. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Feb 6, 2026
  3. melvin-bot commented on Feb 6, 2026

    @melvin-bot

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

  4. melvin-bot commented on Feb 6, 2026

    @melvin-bot

    Triggered auto assignment to @johncschuster (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  5. annaweber830 commented on Feb 6, 2026

    @annaweber830
    Contributor

    Proposal

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

    When a user creates a 1:1 chat while offline and later goes online, starting a new chat (FAB → Start chat) shows the existing DM in the list/RHP but does not show the “Add to group” button next to that user. This prevents quickly turning that DM into a group chat from the start-chat flow.

    What is the root cause of that problem?

    The “Add to group” button in NewChatPage is only rendered when the option has a login. If login is missing, the right-side component returns null, so the button never appears:

    const itemRightSideComponent = (item: ListItem & Option, isFocused?: boolean) => {
    if (!!item.isSelfDM || (item.login && excludedGroupEmails.has(item.login)) || !item.login) {
    return null;
    }

    In the offline-created DM case, the “recent report” option can be built without a matching PersonalDetails entry for the other participant yet. In createOption(), login and accountID are only set from the matched personalDetail. If that lookup fails, login stays undefined (and accountID remains the default 0), which makes the UI treat the option as “not a person you can add”, even though we do have a participant accountID from the report:

    // Set login and accountID only for single participant cases (used in SearchOption context)
    // Also always set for personal details options (showPersonalDetails: true) to ensure search filtering works correctly
    if (showPersonalDetails || (!hasMultipleParticipants && (!report || (report && !reportUtilsIsGroupChat(report) && !reportUtilsIsChatRoom(report))))) {
    result.login = personalDetail?.login;
    result.accountID = Number(personalDetail?.accountID);
    }
    return result;

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

    1. Update createOption() to always set accountID for single-participant (DM) report options from accountIDs[0] even when personalDetail isn’t available yet. This preserves an identity we can safely use in selection/group-draft flows until personal details arrive.
    2. Update NewChatPage’s itemRightSideComponent to allow showing “Add to group” when we have a valid accountID, even if login is temporarily missing.
    3. Update toggleOption() to remove selections using accountID when login is missing, so selecting/unselecting works consistently for these transient options.

    const itemRightSideComponent = (item: ListItem & Option, isFocused?: boolean) => {
    if (!!item.isSelfDM || (item.login && excludedGroupEmails.has(item.login)) || !item.login) {
    return null;
    }
    if (item.isSelected) {
    return (
    <PressableWithFeedback
    sentryLabel={CONST.SENTRY_LABEL.NEW_CHAT.SELECT_PARTICIPANT}
    onPress={() => toggleOption(item)}
    disabled={item.isDisabled}
    role={CONST.ROLE.CHECKBOX}
    accessibilityLabel={item.text ?? ''}
    accessibilityState={{checked: item.isSelected}}
    style={[styles.flexRow, styles.alignItemsCenter, styles.ml5, styles.optionSelectCircle]}
    >
    <SelectCircle
    isChecked={item.isSelected}
    selectCircleStyles={styles.ml0}
    />
    </PressableWithFeedback>
    );
    }
    const buttonInnerStyles = isFocused ? styles.buttonDefaultHovered : {};
    return (
    <Button
    onPress={() => toggleOption(item)}
    style={[styles.pl2]}
    text={translate('newChatPage.addToGroup')}
    innerStyles={buttonInnerStyles}
    small
    />
    );
    };

    const itemRightSideComponent = (item: ListItem & Option, isFocused?: boolean) => {
        // When a DM report is created offline, we can temporarily be missing `login` even though we have `accountID`.
        // Still allow adding to group when we have a valid participant identity.
        if (!!item.isSelfDM || (item.login && excludedGroupEmails.has(item.login)) || (!item.login && !item.accountID)) {
            return null;
        }
    
        if (item.isSelected) {
            return (
                <PressableWithFeedback
                    sentryLabel={CONST.SENTRY_LABEL.NEW_CHAT.SELECT_PARTICIPANT}
                    onPress={() => toggleOption(item)}
                    disabled={item.isDisabled}
                    role={CONST.ROLE.CHECKBOX}
                    accessibilityLabel={item.text ?? ''}
                    accessibilityState={{checked: item.isSelected}}
                    style={[styles.flexRow, styles.alignItemsCenter, styles.ml5, styles.optionSelectCircle]}
                >
                    <SelectCircle
                        isChecked={item.isSelected}
                        selectCircleStyles={styles.ml0}
                    />
                </PressableWithFeedback>
            );
        }
        const buttonInnerStyles = isFocused ? styles.buttonDefaultHovered : {};
        return (
            <Button
                onPress={() => toggleOption(item)}
                style={[styles.pl2]}
                text={translate('newChatPage.addToGroup')}
                innerStyles={buttonInnerStyles}
                small
            />
        );
    };
    

    const toggleOption = (option: ListItem & Partial<OptionData>) => {
    const isOptionInList = !!option.isSelected;
    let newSelectedOptions: SelectedOption[];
    if (isOptionInList) {
    newSelectedOptions = reject(selectedOptions, (selectedOption) => selectedOption.login === option.login);
    } else {
    newSelectedOptions = [...selectedOptions, {...option, isSelected: true, selected: true, reportID: option.reportID, keyForList: `${option.keyForList ?? option.reportID}`}];
    selectionListRef?.current?.scrollToIndex(0, true);
    }
    selectionListRef?.current?.clearInputAfterSelect?.();
    if (!canUseTouchScreen()) {
    selectionListRef.current?.focusTextInput();
    }
    setSelectedOptions(newSelectedOptions);
    if (personalData?.login && personalData?.accountID) {
    const participants: SelectedParticipant[] = [
    ...newSelectedOptions.map((selectedOption) => ({
    login: selectedOption.login,
    accountID: selectedOption.accountID ?? CONST.DEFAULT_NUMBER_ID,
    })),
    {
    login: personalData.login,
    accountID: personalData.accountID,
    },
    ];
    setGroupDraft({participants});
    }
    };

    const toggleOption = (option: ListItem & Partial<OptionData>) => {
        const isOptionInList = !!option.isSelected;
    
        let newSelectedOptions: SelectedOption[];
    
        if (isOptionInList) {
            newSelectedOptions = reject(selectedOptions, (selectedOption) => (option.login ? selectedOption.login === option.login : selectedOption.accountID === option.accountID));
        } else {
            newSelectedOptions = [...selectedOptions, {...option, isSelected: true, selected: true, reportID: option.reportID, keyForList: `${option.keyForList ?? option.reportID}`}];
            selectionListRef?.current?.scrollToIndex(0, true);
        }
    
        selectionListRef?.current?.clearInputAfterSelect?.();
        if (!canUseTouchScreen()) {
            selectionListRef.current?.focusTextInput();
        }
        setSelectedOptions(newSelectedOptions);
    
        if (personalData?.login && personalData?.accountID) {
            const participants: SelectedParticipant[] = [
                ...newSelectedOptions.map((selectedOption) => ({
                    login: selectedOption.login,
                    accountID: selectedOption.accountID ?? CONST.DEFAULT_NUMBER_ID,
                })),
                {
                    login: personalData.login,
                    accountID: personalData.accountID,
                },
            ];
            setGroupDraft({participants});
        }
    };
    

    function createOption(
    accountIDs: number[],
    personalDetails: OnyxInputOrEntry<PersonalDetailsList>,
    report: OnyxInputOrEntry<Report>,
    currentUserAccountID: number,
    config?: PreviewConfig,
    reportAttributesDerived?: ReportAttributesDerivedValue['reports'],
    privateIsArchived?: string,
    ): SearchOptionData {
    const {showChatPreviewLine = false, forcePolicyNamePreview = false, showPersonalDetails = false, selected, isSelected, isDisabled} = config ?? {};
    // Initialize only the properties that are actually used in SearchOption context
    const result: SearchOptionData = {
    // Core identification - used in SearchOption context
    // We use empty string as a default for reportID as in many places the application uses conditional checks that test for reportID existence with truthiness operators
    // eslint-disable-next-line rulesdir/no-default-id-values
    reportID: report?.reportID ?? '',
    accountID: 0, // Set conditionally below
    login: undefined, // Set conditionally below
    policyID: report?.policyID,
    ownerAccountID: report?.ownerAccountID,
    // Display properties - used in SearchOption context
    text: undefined, // Set below
    alternateText: undefined, // Set below
    participantsList: undefined, // Set below
    // State properties - used in SearchOption context
    isSelected: isSelected ?? selected ?? false, // Use isSelected preferentially, fallback to selected for compatibility
    isDisabled,
    brickRoadIndicator: null,
    // Type/category flags - used in SearchOption context
    isPolicyExpenseChat: report ? reportUtilsIsPolicyExpenseChat(report) : false,
    isMoneyRequestReport: report ? reportUtilsIsMoneyRequestReport(report) : false,
    isThread: report ? isChatThread(report) : false,
    isTaskReport: report ? reportUtilsIsTaskReport(report) : false,
    isSelfDM: report ? reportUtilsIsSelfDM(report) : false,
    isChatRoom: report ? reportUtilsIsChatRoom(report) : false,
    isInvoiceRoom: report ? isInvoiceRoom(report) : false,
    isDM: report ? isDM(report) : false,
    // Status properties - used in SearchOption context
    private_isArchived: undefined, // Set from reportNameValuePairs below
    lastVisibleActionCreated: report?.lastVisibleActionCreated,
    notificationPreference: report ? getReportNotificationPreference(report) : undefined,
    lastMessageText: report?.lastMessageText ?? '',
    // Display properties needed for UI rendering
    icons: undefined, // Set below - needed for avatars
    subtitle: undefined, // Set below - needed for display
    keyForList: '', // Set below - needed for React keys
    // Legacy property kept for backwards compatibility
    selected: isSelected ?? selected ?? false, // Duplicate of isSelected for backwards compatibility
    };
    const personalDetailMap = getPersonalDetailsForAccountIDs(accountIDs, personalDetails);
    const personalDetailList = Object.values(personalDetailMap).filter((details): details is PersonalDetails => !!details);
    const personalDetail = personalDetailList.at(0);
    let hasMultipleParticipants = personalDetailList.length > 1;
    let subtitle;
    let reportName;
    result.participantsList = personalDetailList;
    if (report) {
    const reportNameValuePairsForReport = allReportNameValuePairsOnyxConnect?.[`${ONYXKEYS.COLLECTION.REPORT_NAME_VALUE_PAIRS}${report.reportID}`];
    // Set properties that are used in SearchOption context
    result.private_isArchived = privateIsArchived ?? reportNameValuePairsForReport?.private_isArchived;
    result.keyForList = String(report.reportID);
    // Type/category flags already set in initialization above, but update brickRoadIndicator
    const reportAttribute = reportAttributesDerived?.[report.reportID];
    result.allReportErrors = reportAttribute?.reportErrors ?? {};
    result.brickRoadIndicator = !isEmptyObject(result.allReportErrors) ? CONST.BRICK_ROAD_INDICATOR_STATUS.ERROR : (reportAttribute?.brickRoadStatus ?? '');
    // eslint-disable-next-line @typescript-eslint/prefer-nullish-coalescing -- below is a boolean expression
    hasMultipleParticipants = personalDetailList.length > 1 || result.isChatRoom || result.isPolicyExpenseChat || reportUtilsIsGroupChat(report);
    subtitle = getChatRoomSubtitle(report, true, !!result.private_isArchived);
    // If displaying chat preview line is needed, let's overwrite the default alternate text
    const lastActorDetails = personalDetails?.[report?.lastActorAccountID ?? String(CONST.DEFAULT_NUMBER_ID)] ?? {};
    // eslint-disable-next-line @typescript-eslint/no-deprecated
    result.lastMessageText = getLastMessageTextForReport({translate: translateLocal, report, lastActorDetails, isReportArchived: !!result.private_isArchived, currentUserAccountID});
    result.alternateText =
    showPersonalDetails && personalDetail?.login
    ? personalDetail.login
    : getAlternateText(result, {showChatPreviewLine, forcePolicyNamePreview}, !!result.private_isArchived, currentUserAccountID, lastActorDetails);
    const personalDetailsForCompute: PersonalDetailsList | undefined = personalDetails ?? undefined;
    const computedReportName = computeReportName(
    report,
    allReports,
    allPolicies,
    undefined,
    undefined,
    personalDetailsForCompute,
    allReportActions,
    currentUserAccountID,
    result.private_isArchived,
    );
    reportName = showPersonalDetails
    ? getDisplayNameForParticipant({accountID: accountIDs.at(0), formatPhoneNumber: formatPhoneNumberPhoneUtils}) || formatPhoneNumberPhoneUtils(personalDetail?.login ?? '')
    : computedReportName;
    } else {
    // eslint-disable-next-line @typescript-eslint/prefer-nullish-coalescing
    reportName =
    getDisplayNameForParticipant({accountID: accountIDs.at(0), personalDetailsData: personalDetails ?? undefined, formatPhoneNumber: formatPhoneNumberPhoneUtils}) ||
    formatPhoneNumberPhoneUtils(personalDetail?.login ?? '');
    result.keyForList = String(accountIDs.at(0));
    result.alternateText = formatPhoneNumberPhoneUtils(personalDetails?.[accountIDs[0]]?.login ?? '');
    }
    // Set core display properties that are used in SearchOption context
    result.text = reportName;
    result.icons = getIcons(
    report,
    formatPhoneNumberPhoneUtils,
    personalDetails,
    personalDetail?.avatar,
    personalDetail?.login,
    personalDetail?.accountID,
    null,
    undefined,
    !!result?.private_isArchived,
    );
    result.subtitle = subtitle;
    // Set login and accountID only for single participant cases (used in SearchOption context)
    // Also always set for personal details options (showPersonalDetails: true) to ensure search filtering works correctly
    if (showPersonalDetails || (!hasMultipleParticipants && (!report || (report && !reportUtilsIsGroupChat(report) && !reportUtilsIsChatRoom(report))))) {
    result.login = personalDetail?.login;
    result.accountID = Number(personalDetail?.accountID);
    }
    return result;
    }

    // Set login and accountID only for single participant cases (used in SearchOption context)
    // Also always set for personal details options (showPersonalDetails: true) to ensure search filtering works correctly
    if (showPersonalDetails || (!hasMultipleParticipants && (!report || (report && !reportUtilsIsGroupChat(report) && !reportUtilsIsChatRoom(report))))) {
        result.login = personalDetail?.login;
        result.accountID = personalDetail?.accountID ? Number(personalDetail.accountID) : Number(accountIDs.at(0));
    }
    

    What alternative solutions did you explore? (Optional)

    • Recomputing missing login for DM report options from other Onyx sources (e.g., login lists) isn’t reliable because ONYXKEYS.LOGIN_LIST is keyed by login and doesn’t provide an accountID → login mapping.
    • Fetching/forcing personal details hydration before rendering the start-chat list would add latency and still risk timing races; falling back to a stable accountID is simpler and keeps the UI responsive.
  6. twilight2294 commented on Feb 6, 2026

    @twilight2294
    Contributor

    Proposal

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

    When a user creates a 1:1 direct message while offline, then comes back online and navigates to "Start chat", the "Add to group" button is missing for that user, even though they should be addable to a group since they have an existing 1:1 DM.

    What is the root cause of that problem?

    When a 1:1 DM is created optimistically (while offline), the buildOptimisticChatReport function sets policyID to CONST.POLICY.OWNER_EMAIL_FAKE which equals '__FAKE__':

    https://github.com/Expensify/App/blob/main/src/libs/ReportUtils.ts#L7672

    However, the isOneOnOneChat() function only checks for CONST.POLICY.ID_FAKE (which equals '_FAKE_') or falsy values:

    https://github.com/Expensify/App/blob/main/src/libs/ReportUtils.ts#L2713-L2714

    Because '__FAKE__' is neither '_FAKE_' nor falsy, isOneOnOneChat() incorrectly returns false for offline-created DMs. This causes the current user to not be excluded from the participant list (since the exclusion logic depends on isOneOnOneChat returning true):

    https://github.com/Expensify/App/blob/main/src/libs/ReportUtils.ts#L3458

    With both participants in the list, hasMultipleParticipants becomes true in createOption, which prevents the login field from being set:

    https://github.com/Expensify/App/blob/main/src/libs/OptionsListUtils/index.ts#L997-L1000

    Finally, without a login value on the option, the "Add to group" button is not rendered:

    https://github.com/Expensify/App/blob/main/src/pages/NewChatPage.tsx#L401

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

    Update the isOneOnOneChat function to also recognize CONST.POLICY.OWNER_EMAIL_FAKE as a valid indicator of a policy-less 1:1 chat:

    https://github.com/Expensify/App/blob/main/src/libs/ReportUtils.ts#L2713-L2714

    return (
        (report?.policyID === CONST.POLICY.ID_FAKE || report?.policyID === CONST.POLICY.OWNER_EMAIL_FAKE || !report?.policyID) &&
        isPolicyExpenseChat(report) === false &&
        // ...

    For consistency, also update the same check on line 1911:

    https://github.com/Expensify/App/blob/main/src/libs/ReportUtils.ts#L1911

    (report?.policyID === CONST.POLICY.ID_FAKE || report?.policyID === CONST.POLICY.OWNER_EMAIL_FAKE || !report?.policyID ? hasParticipantInArray(report, policyMemberAccountIDs) : isPolicyRelatedReport(report, policyID))

    What alternative solutions did you explore?

    An alternative would be to change buildOptimisticChatReport to use CONST.POLICY.ID_FAKE instead of CONST.POLICY.OWNER_EMAIL_FAKE, but this could have unintended side effects elsewhere in the codebase where OWNER_EMAIL_FAKE might be expected. The proposed fix is safer as it makes isOneOnOneChat handle both fake policy constants consistently.

  7. yatin-italy commented on Feb 7, 2026

    @yatin-italy

    Proposal

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

    When a user creates a 1:1 chat while offline and then goes online, opening “Start chat” (FAB → Start chat) shows the existing DM in the list/RHP, but it does not show the “Add to group” button next to that user; expected is that “Add to group” is shown so the user can convert the DM into a group chat, but the button is missing.

    What is the root cause of that problem?

    In this flow, ReportUtils.ts classifies policy-less 1:1 chats with an assumption that only CONST.POLICY.ID_FAKE or a falsy policyID can represent them, but offline optimistic 1:1 DMs are created with policyID = CONST.POLICY.OWNER_EMAIL_FAKE in buildOptimisticChatReport() (ReportUtils.ts, line 7672), so isOneOnOneChat() (src/libs/ReportUtils.ts, lines 2713–2714) returns false for these reports, which causes downstream participant display logic to treat the chat as multi-participant and produce an option without login/accountID, and then the right-side action does not render because it depends on item.login.

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

    Fix the earliest root cause in the layer that owns it by expanding 1:1 chat classification in ReportUtils.ts to treat CONST.POLICY.OWNER_EMAIL_FAKE the same as CONST.POLICY.ID_FAKE and falsy policyID, and keep buildOptimisticChatReport() unchanged because other code depends on OWNER_EMAIL_FAKE.

    // src/libs/ReportUtils.ts – isOneOnOneChat() (lines 2713–2714)
    Treat OWNER_EMAIL_FAKE as a policy-less 1:1 chat indicator:
    return (    (report?.policyID === CONST.POLICY.ID_FAKE || report?.policyID === CONST.POLICY.OWNER_EMAIL_FAKE || !report?.policyID) &&    !isChatRoom(report) &&
    // src/libs/ReportUtils.ts – doesReportBelongToWorkspace() (line 1911)
    Use the same policy condition so workspace membership logic stays aligned with 1:1 classification:
    (report?.policyID === CONST.POLICY.ID_FAKE || report?.policyID === CONST.POLICY.OWNER_EMAIL_FAKE || !report?.policyID ? hasParticipantInArray(report, policyMemberAccountIDs) : isPolicyRelatedReport(report, policyID))

    After this, isOneOnOneChat() becomes true for offline-created 1:1 DMs, the current user is excluded from the participant list, the option becomes a single-participant option with login/accountID, and “Add to group” is shown.

    What alternative solutions did you explore? (Optional)

    Changing buildOptimisticChatReport() to use ID_FAKE: It would match the existing checks, but other code (e.g. ModifiedExpenseMessage.ts, usePolicy.ts) explicitly depends on OWNER_EMAIL_FAKE, so changing it increases the blast radius and can cause regressions. Keeping OWNER_EMAIL_FAKE at creation time and expanding the reader-side classification is safer.

    UI or OptionsListUtils fallbacks for missing login/accountID: This would hide the real problem by compensating for misclassified reports and would duplicate responsibility; fixing classification where it belongs keeps the behavior consistent.

  8. Uzaifm127 commented on Feb 9, 2026

    @Uzaifm127
    Contributor

    This issue isn't only about Add to group button.

    We have incorrect optimistic data conflicting in the app when coming back online.

    Note: uzafim127+5@gmail.com is exist in the app, it isn't the account which is new or which we need to invite.

    issue.mp4
  9. Uzaifm127 commented on Feb 9, 2026

    @Uzaifm127
    Contributor

    @trjExpensify I'm not aware of the search in start chat.

    Should we enable to show the results when we search offline (FAB > Start chat > Search user) and when the search term (typed by user) option isn't there in local cache then should we show the result?

    Because showing the result from local cache when offline make sense, but (while offline) showing the results which aren't in cache is what I have doubt.

    Also if a user exist in the backend but after searching offline, it won't show the result from backend so it creates a user to invite but user exist already. That also seems to doubtful to me.

    Screen.Recording.2026-02-09.at.11.mp4
  10. 55 remaining items

  11. melvin-bot commented on Jul 15, 2026

    @melvin-bot

    This issue has not been updated in over 15 days. @rojiphil, @johncschuster eroding to Monthly issue.

    P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

  12. melvin-bot commented on Jul 23, 2026

    @melvin-bot

    @rojiphil Whoops! This issue is 2 days overdue. Let's get this updated quick!

  13. rojiphil commented on Jul 24, 2026

    @rojiphil
    Contributor

    @johncschuster Can we close this issue please since the issue is not reproducible ?

  14. mvtglobally commented on Jul 25, 2026

    @mvtglobally

    Issue not reproducible during KI retests. (Third week)

  15. melvin-bot commented on Jul 27, 2026

    @melvin-bot

    @rojiphil Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributorsretest-weeklyApply this label if you want this issue tested on a Weekly basis by Applause

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions