Report fields - "Enabled/Disabled" does not align with header "Status" in list value page

[izarutskaya]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.0.54-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes in Hybrid iOS
Email or phone of affected tester (no customers): [email protected]
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

Precondition:

• Workspace has list type report field with some list values.

1. Go to staging.new.expensify.com
2. Go to workspace settings > Report fields.
3. Click on the list type report field.
4. Click List values.

Expected Result:

"Enabled/Disabled" will align with header "Status".

Actual Result:

"Enabled/Disabled" does not align with header "Status" in list value page.

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6645373_1729849785470.list.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @MarioExpensify (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[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.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[izarutskaya]

We think this issue might be related to the #wave-control

[izarutskaya]

Production

bandicam.2024-10-25.13-00-16-098.mp4

[Krishna2323]

Edited by proposal-police: This proposal was edited at 2024-10-25 11:35:49 UTC.

Proposal


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

Report fields - "Enabled/Disabled" does not align with header "Status" in list value page

What is the root cause of that problem?

• Min width is not set.
  

  App/src/pages/workspace/reportFields/ReportFieldsListValuesPage.tsx

  Lines 166 to 167 in 904e715

  	<Text style={styles.searchInputStyle}>{translate('common.name')}</Text>
  	<Text style={[styles.searchInputStyle, styles.textAlignCenter]}>{translate('statusPage.status')}</Text>

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


• Wrap status text in a view and pass style={[StyleUtils.getMinimumWidth(60)]}.
• Same as we do in workspace tags page and other similar pages.
  

  App/src/pages/workspace/tags/WorkspaceViewTagsPage.tsx

  Lines 130 to 140 in 904e715

  	const getCustomListHeader = () => {
  	const header = (
  	<View style={[styles.flex1, styles.flexRow, styles.justifyContentBetween, canSelectMultiple && styles.ml3]}>
  	<View>
  	<Text style={[styles.searchInputStyle]}>{translate('common.name')}</Text>
  	</View>
  	<View style={[StyleUtils.getMinimumWidth(60)]}>
  	<Text style={[styles.searchInputStyle, styles.textAlignCenter]}>{translate('statusPage.status')}</Text>
  	</View>
  	</View>
  	);

• We should also check other missing styles and make them consistent and we should also check other similar components to fix the same bug.

What alternative solutions did you explore? (Optional)

Result

[MarioExpensify]

Hardly a deploy blocker. Will check if we have any recent PR affecting this and revert it if needed. If not we'll move with an External task.

[Krishna2323]

@MarioExpensify, I think this is the offending PR.