Add System Settings Tab in Sub Navigation

[DirkCionci]

What type(s) of user does this feature affect?

• admins? (note: all-casa admins are Ruby for Good staff like @seanmarcia who can create new CASA organizations on the platform)

Description As an Admin, I would like a System Settings page where I can turn on/ off features for volunteers and supervisors because not all CASA organizations use the platform in the same way.

Screenshots of current behavior, if any
System Settings tab does NOT currently exist

How should it work System Settings sub-nav

• Nested under System Imports
• URL: https://casa-qa.herokuapp.com/settings or devs choice
• Feature Toggles menu option nested Under 'System Settings"
• Feature Toggles option has Feature Toggles as header on page
  • Sub-header - New Case Contact Form
  • Feature Toggle (True/ False) - Volunteers can add Other Expenses
  • Feature Toggle defaults to "False"

Acceptance Criteria

• Page format as outlined above
• Only CASA Admins can view System Settings sub-nav
• When "Volunteers can add Other Expenses" feature toggle is "True"
  • Volunteers can view and add "Other" Expenses
• When "Volunteers can add Other Expenses" feature toggle is "False"
  • Volunteers cannot view or add "Other" Expenses
• Feature Toggle defaults to "False"
• Minimum Java Script
• Test Coverage for Java Script

QA Login Details:
Link to QA site

Login Emails:

• [email protected] view site as a volunteer
• [email protected] view site as a supervisor
• [email protected] view site as an admin

password for all users: 12345678

Questions? Join Slack!

We highly recommend that you join us in slack https://rubyforgood.herokuapp.com/ #casa channel to ask questions quickly and hear about office hours (currently Wednesday 6-8pm Pacific), stakeholder news, and upcoming new issues.

[github-actions[bot]]

This issue has been inactive for 244 hours (10.17 days) and will be automatically unassigned after 116 more hours (4.83 days).

[github-actions[bot]]

This issue has been inactive for 364 hours (15.17 days) and is past the limit of 360 hours (15.00 days) so is being unassigned.

[ludamillion]

Is this still a desired feature? I can tackle it if it is.

[danaguilar]

I would like to start work on this issue