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

Add ability to set rules for duty roster creation #71

Open
parsonsbatsc opened this issue Apr 20, 2018 · 2 comments
Open

Add ability to set rules for duty roster creation #71

parsonsbatsc opened this issue Apr 20, 2018 · 2 comments

Comments

@parsonsbatsc
Copy link

Unless you want to import different lists for each roster, you might want a way to set additional rules for roster creation using subsets of the same personnel list, like "This roster only uses personnel that are e-4 and e-5", or "This roster only uses personnel that are e-3 and below."

This would save you from checking a whole lot of boxes in the case of roster by grade.

If there's currently a way to do this other than checking boxes, I missed it.

@oprock
Copy link
Contributor

oprock commented Apr 22, 2018

Since this program pulls from the entire employee list, how about a grade filter on the roster assignment selection?

@parsonsbatsc
Copy link
Author

That's more or less what I meant. I'm sorry if I wasn't clear enough.

That would make it easier to assign people for duty that requires an NCO vs. field day...uh...I'm not sure what they call it in the Army. Cleaning everything.

That's actually what I was thinking about when I added the info about reasons for not being available for duty also. If you have it attached to the personnel list rather than the roster, you can automatically rule people out for certain things (and then have it copy the reason into the box provided.) That way, the form is filled out correctly, and you have all of the information you need about each person stored in the personnel list.

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

No branches or pull requests

7 participants
@parsonsbatsc @austinjfreed @oprock @hkarnati @HarlowM @fpiedade and others