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.

Sign up for GitHub

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

Jump to bottom

Move Contact Settings up under Contact Info to increase visibility #190

Closed
jim-mcgowan opened this issue Sep 25, 2019 · 3 comments
Closed

Move Contact Settings up under Contact Info to increase visibility #190

jim-mcgowan opened this issue Sep 25, 2019 · 3 comments
Labels
contact-info high-priority XS
Milestone
DCSOps Fixes

Comments

@jim-mcgowan
Copy link
Member

jim-mcgowan commented Sep 25, 2019 •
edited
Loading

contact info
@kfogel kfogel mentioned this issue Sep 25, 2019
Closed
@jim-mcgowan jim-mcgowan added the XS label Nov 25, 2019
@jim-mcgowan jim-mcgowan added this to the One Red Cross milestone Nov 25, 2019
@frankduncan
Copy link
Contributor

This causes a few newlines to appear under call seetings and carrier settings because the panel is now squeezed, but that should be ok.

frankduncan pushed a commit that referenced this issue Jul 4, 2020
Remove unused scheduler/people files
9ab24be 
roster/people should be the only routes used, and indeed are the only
routes used.  But in Issue #190, we are updating how those look, and
these come up as duplicates.  Instead of modifying both places, remove
these and remove them from the routes.
frankduncan pushed a commit that referenced this issue Jul 4, 2020
Fix #190: Move contact settings up under contact info
2ec6846 
Issue #190: Move Contact Settings up under Contact Info
            to increase visibility
frankduncan pushed a commit that referenced this issue Jul 4, 2020
Remove unused scheduler/people files
4ffffe0 
roster/people should be the only routes used, and indeed are the only
routes used.  But in Issue #190, we are updating how those look, and
these come up as duplicates.  Instead of modifying both places, remove
these and remove them from the routes.
@jim-mcgowan
Copy link
Member Author

@frankduncan I assume I will be able to see this when it gets pushed to staging.

@frankduncan
Copy link
Contributor

@OhMcGoo Yep!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
contact-info high-priority XS
Projects
None yet
Milestone
DCSOps Fixes
Development

No branches or pull requests
2 participants
@jim-mcgowan @frankduncan