Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sunday Dec 22, 2024 Release Sign-Off: chanel-10321-bug-release-issue-tag-flagship-mobile-approver-members #10347

Closed
9 tasks
github-actions bot opened this issue Dec 9, 2024 · 2 comments
Assignees
Labels
release tag for release tickets

Comments

@github-actions
Copy link
Contributor

github-actions bot commented Dec 9, 2024

Release for Sunday Dec 22, 2024

This ticket is to control for all the requirements for the upcoming release before the Pull Request is opened. This should hold any tasks or bug fixes unique to the release branch. It should also collect any text for What's New and any content changes for the app stores.

This ticket should be complete by Sunday Dec 15, 2024

Release Checklist

  • What's new content (App Store) - required
  • What's new content (In app/Alert Box) - optional
  • Content updates

Sign-offs:

  • QA Due Wednesday Dec 11, 2024
  • Product Due Saturday Dec 14, 2024
  • Mobile Release Manager Due after 10am EST Sunday Dec 15, 2024

Release version

chanel-10321-bug-release-issue-tag-flagship-mobile-approver-members

What's New content (App Store) - required

If there aren't any new features, use standard messaging: We added general improvements and fixed a few bugs.

If a Flagship team decides to update the App Stores What's New content, their work should be done in a ticket and provided to the release manager, who will then update this section. If not provided, it's assumed not to be used.

What's New content (In App/Alert Box) - optional

This work is to be completed by Flagship teams before RC branch is cut and completed by engineering. Flagship team to provide release manager with the ticket this work was completed in for reference.

App Store content changes?

All changes should be made to the files in the repo and not directly to the stores.
Indicate NA if no changes.

  • Images:
  • Content:
  • Other (Privacy Policy, Promotions etc.):

Severe bugs:

Issue Title Notes
#10327 BUG - sev-2 - All - Appointments: Screen reader users with no appointments trapped in broken UI
#9800 BUG - sev-2 - Probably all? Definitely iOS - Some links in appeals not announcing as links to screenreader
#9615 BUG - sev-2 - [iOS/Android/All] - Increase in session refresh error rates (which forces users to re-authenticate)
#9476 BUG - sev-2 - All - Keyboard navigation on subtasks, large panels, cancel popups often goes to hidden layers, gets stuck
#9461 BUG - sev-2 - iOS - Some assistive tech can't get 'into'/'onto' screens where the only actionable items are initially offscreen
#9064 BUG - sev-2 - Android - LinkWithAnalytics-related crashes
#8271 BUG - sev-2 - iOS - Unable to log in on older iPad (maybe related to older version of Safari?)

Regression Testing

QA Testrail Regression Test Run Here

@TKDickson
Copy link
Contributor

Removed myself, as well as Don and Chris, from this ticket.

@IsraelleHub @SarahHuber-AdHoc I assume this was made entirely for testing purposes and can be closed (like I've closed many other release testing-related tickets). Someone will need to be keeping an eye out for these and closing them in my stead, as an FYI.

@TKDickson TKDickson removed their assignment Dec 12, 2024
@timwright12
Copy link
Contributor

@IsraelleHub if we're using this template for testing, please change the title so it's more obvious

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release tag for release tickets
Projects
None yet
Development

No branches or pull requests

8 participants