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

/allOpen Slack command #61

Open
3 tasks
CherrelleTucker opened this issue Mar 27, 2024 · 0 comments
Open
3 tasks

/allOpen Slack command #61

CherrelleTucker opened this issue Mar 27, 2024 · 0 comments

Comments

@CherrelleTucker
Copy link
Owner

Description

Once an item is marked done in Slack (deployed webApp: completedActionsSlackApp) it is helpful to be able to call the users open action items list to verify that it has been correctly updated. Currently, open action items are sent on an automated schedule (Slack webhook: slackWorkflowOpenActionItemsCherrelle). These actions are completed in two different scripts. To send the correct open action items list to the correct workflow webhook, each user has their own copy of the slackWorkflowOpenActionItems[User Name] script.

To implement /allOpen, the command would need to work with both a webhook and a webApp.
Thoughts:

  • since each users automated message requires a unique workflow webhook, I can't combine both scripts completely.
  • if I use the slackWorkflowOpenActionItems[User Name] scripts as a library script, I would need to also have individual slash command scripts for each name. - undesirable.
  • Modify a copy of the existing slackWorkflowOpenActionItems[username] script to require the [User Name] as an input in the command. "/allopen Cherrelle" "/allopen Pontus" and add to the existing completedActionsSlackApp script.

Examples or References

No response

Deliverable

  • modify slackWorkflowOpenActionItems[User Name] script to accept first name as an input for search
  • Slack command: /allopen [UserName]
  • accommodate "Jeanne'"

Implementation Considerations

No response

Related Issues

#58 , #57, #54, #53

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

1 participant