I was able to login with my existing credentials.

Also check out this plugin
https://marketplace.atlassian.com/apps/1220209/issue-checklist-free?hosting=cloud&tab=overview

Looks like this is not available
Cc: [~aloraine]

I and Prutha Kulkarni worked on this ticket to check the functioning of Jira following migration.
Following are our observations:
1) Attachments to tickets after 2017 are available and can be downloaded if necessary.
2) Tickets can be moved from column to column as expected and can be updated. Attachments can be added to tickets.
3) Jira credentials can be used to login
4) Issues can be linked and the link functions properly.
5) Search functions properly and filters work as expected.
6) Emails are received for tickets being watched or assigned to.

The following observations are made as well:
1) New tickets can be created in any epic without facing any errors.
2) New boards can be created and worked with.
3) When we checked the configurations for existing boards on Jira (IGB, Release-testing), an error message is being displayed at the bottom for every option (like General, Columns, Swimlanes, Quick filters, Card Layout, Issue Detail View, etc.) but this message is not displayed for the board we created for testing (Named Test-Board). Please refer the screenshots attached to this ticket, to view the error message displayed.

Admin testing
1. I tried modifying the JIRA user groups to grant my personal account higher privs, that seems to work.
2. Also tried switching Transition states order like moving "IN PROGRESS" sections location to "NEEDS 1ST LEVEL REVIEW" locations. That seems to work.
Shamika Gajanan Kulkarni and Prutha Kulkarni The error you have reported I believe is because your accounts are not administrator accounts(Configure of boards in an admin priv). I tried the same with admin account, didn't seem to get the error. Looks like we are good on that error.

Cc: [~aloraine]

After reading through the JIRA suggestions and running some time analysis on the type of instances used currently for existing workload and test instance performance.
Jira recommends using m series instances for database and c series for JIRA server.

I suggest below hardware configuration
Instance Type: c5n.large or higher
Disk size(EBS Volume): 15GB or higher
Cost: $0.108 per Hour (slightly more expensive than our existing setup but we can get cost-benefit on the reserved instances )

Cost reference: https://aws.amazon.com/ec2/pricing/on-demand/
JIRA Infrastructure recommendation References: https://confluence.atlassian.com/enterprise/infrastructure-recommendations-for-enterprise-jira-instances-on-aws-969532459.html

Note: Reserved instance costing is much lower than on-demand costing.
Attached: Price and hardware comparison of 3 best instance types for our usage.

Cc: [~aloraine]

Next step will be to run the migration playbooks in Loraine Lab account. Moving to Closed.