[Report Creation UI] Total and action columns are not aligned and in the incorrect row

[trjExpensify]

Coming from here.

• The green View button should be on the header row in the Action column.
• The bold total should be on the header row in the Total column.
• Each expense on the report should have a hyperlinked view button in the Action column.

Example on staging:

[melvin-bot]

Triggered auto assignment to @jliexpensify (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.

[sumo-slonik]

Hi, I'm Kuba from SWM, and I'll take care of this

[mavrickdeveloper]

hey @sumo-slonik , didn't notice your message , i already addressed this

[melvin-bot]

📣 @mavrickdeveloper! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

1. Make sure you've read and understood the contributing guidelines.
2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
   
   Format:

Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

[sumo-slonik]

Hi @mavrickdeveloper, where did you address it?

[mavrickdeveloper]

Here :

Expensify.61895.mp4

[mavrickdeveloper]

@trjExpensify any ideas why you are getting view button in different color than the current version of main branch ?

[Kicu]

@mavrickdeveloper can you please provide an issue link and a PR link to help us better understand what specifically you are adressing and in what context?

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[jliexpensify]

@mavrickdeveloper you haven't been assigned this issue - if you haven't been assigned an issue, you're not able to work on it.

[trjExpensify]

Sorry @jliexpensify forgot to add myself so you got assigned to BZ. Switching it! 👍

[jliexpensify]

All good!

[trjExpensify]

Marking this as a deploy blocker, so QA don't create more dupes like #61976

[melvin-bot]

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

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

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[srikarparsi]

This is being fixed in this PR

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.