tm21cy / SS-HR-Automation

1 stars 0 forks source link

Staff Lookup #6

Open tm21cy opened 2 years ago

tm21cy commented 2 years ago

Concise explanation of requested feature. One of the core reasons this bot exists is the usage of staff-related data - this means we need to immediately support functionality to search for staff. It is preferable if users are able to search by optional first and last names, and if multiple results return in such a case, implement a drop-down list that users can select from to load a specific profile (@tm21cy has code in Bit that may be able to assist with this).

There should also be support via subcommands for searching by position, by department, by team, and by supervisor of a department. this will be added at a later date.

What problem does this feature solve? Necessary implementation. This is a necessary function for the bot to continue to production.

Describe the necessary implementation summary, and specific implementations under each sub-heading. Ideally, the bot has two scenarios of searching for a user: Searching via any subcommand for a single user result

Searching via any subcommand for a multi-user result

Front-End (Bot) [] denotes optional, ![] denotes required. /search user [firstName] [lastName] /search position ![position] [dept] [team] - for search narrowing. /search department [team] [position] /search team [department] /search supervisors [department] [team] - ideally only one of these should be selected

See above for rendering instructions.

Back-End (DB)

Additional context None. Request below.

Requested Timeline ASAP - within one week if possible.

Requesting Department Human Resources - Corporate

Requesting User & Title Tyler McDonald Senior Vice President of Human Resources

tm21cy commented 2 years ago

Updated to remove supervisor queries due to decreasing importance + existing 2 way communication

tm21cy commented 2 years ago

Initial queries merged and changelog will be made under routes v1.2.0

net-tech commented 2 years ago

@tm21cy please click transfer issue below "Lock Conversation" and transfer this issue to the new repository,