BUG - sev-3 - All - Messaging: can get 'stuck' on empty page when moving the only message in a page to a new folder

[TKDickson]

What happened?

When a message is the only one on its page within a custom folder (ex: the 11th message, because 1-10 are on the first screen, and only 11 is on the second page screen), and you move that message to a different folder, when you navigate back out of the message you are brought to a screen that appears kind of broken:

Specs:

• Device:
• OS:
• User Account:
• Accessibility State:

Steps to Reproduce

Video reproducing

Desired behavior

Will need to talk with UX. The 'easy' answer is I assume to be brought back into the folder, on the 'prior' page (screen showing the 1-10 messages if you just deleted the 11th, the 11-20 messages if you just deleted the 21st, etc) but I'd rather have them sign off on that approach.

Acceptance Criteria

Bug Severity - BE SURE TO ADD THE SEVERITY LABEL

See Bug Tracking for details on severity levels

• Impact: Low
• Frequency: Low

• 3 - Low

Linked to Story

Screen shot(s) and additional information

Full JSON response for services related to issue (expand/collapse)

Ticket Checklist

• Steps to reproduce are defined
• Desired behavior is added
• Labels added (front-end, back-end, global, Health, relevant feature, accessibility, etc)
• Estimate of 1 added (for front-end tickets)
• Added either to the relevant feature epic (if found during new feature implementation), or the relevant team's bug epic (Global, Health & Benefits, API, QART)

[alexandec]

Lauren approves the approach described above. Source: https://adhoc.slack.com/archives/C067S0FRP0C/p1733930579447599

[alexandec]

@TKDickson do you know of a good staging user where I can move messages around and test a fix?

[TKDickson]

@alexandec +226

[alexandec]

@TKDickson thanks. Is it normal for all the pages to be empty when you page past 100 messages? That user has 188 total messages in the inbox, and paging works fine up to 100 messages, but after that the pages are empty for me.

[TKDickson]

NOPE that's a bug. @alexandec please write a bug ticket.

[alexandec]

Looks like @rbontrager beat me to it: #10379