Update MerchStore Sidebar Menu

[sync-by-unito[bot]]

Update the left sidebar menu with the new options for the MerchStores. Currently there is no button or easy way to navigate to /admin/merchstores/

Steps to Test

1. Open the deploy preview
2. Login
3. Verify that the sidebar has two icons, the group order icon and the merchstore icon
4. Verify that navigation is working correctly and that if you are on the merchstore page or in a merchstore, the merchstore icon is orange. Same thing for group orders

﹍Links﹍

----	----		Author's Name	Patrick Nelson		Pull Request	https://github.com/RangeMPLS/merchology-merch-stores/pull/367
Deploy Preview	https://deploy-preview-367--staging-merch-stores.netlify.app/
Branch	feature/merchstore-icon-sidebar

﹍Functionality Review Checklist﹍

Functionality Reviewer's name: _____

Notes before you begin: Plan to spend approximately 10% of the original development time to accomplish a thorough functionality review. Never approve critical issues. Minor issues can be approved to meet deadlines, but the task should still be sent back to the author to address them in the future (depending on the severity).

Functionality review checklist:

• [ ] Confirmed the functionality is working correctly.
• [ ] Tried to break it. The goal is to find critical and serious bugs. If time allows, you can also flag minor bugs to the author to fix. See the section on bugs from the dev protocol doc for information on how to classify bugs.
• [ ] Changed values to ensure the update still works correctly when things change. Channel your inner Shadab and try putting crazy values into admin fields and see how the program responds!
• [ ] Summarized the methodology you used to test (including links) and attached it to the Wrike task.

﹍Code Review Checklist﹍

Code Reviewer's name: _____

Notes before you begin: Plan to spend approximately 10% of the original development time to accomplish a thorough code review. Never merge critical issues. Minor issues can be merged to meet deadlines, but the task should still be sent back to the author to address them in the next release or a hotfix (depending on the severity). See the section on bugs from the dev protocol doc for information on how to classify bugs.

Code review checklist:

• [ ] Looked for potential logic flaws in the code.
• [ ] Confirmed best practices were utilized (DRY, ETL, modular code, etc).
• [ ] Ensured that adequate documentation of the feature/fix was provided (comments explaining the purpose of the code, updating the README, and/or updating supplemental documents like a syntax spreadsheet).
• [ ] Ensured the code is legible and can be easily understood by any developer via the use of descriptive yet concise variable/function names, comments on particularly complex code blocks explaining purpose, etc.
• [ ] Executed additional testing focused on potentially problematic pieces of logic.

┆Issue is synchronized with this Wrike Item by Unito

[sync-by-unito[bot]]

➤ jg-digital commented:

patrickrnelson We're working on getting you a different / larger task this week so putting this in your court for tomorrow! Let us know if you have trouble!

[sync-by-unito[bot]]

➤ Patrick Nelson commented:

Becky Brown this is ready for FR!

By the way, it looks like when I changed the status of this task it automatically reassigned to Meghan.