Describe the bug

A clear and concise description of what the bug is.

The bot doesn't respond

2022-05-20T09:58:56.256051+00:00 app[web.1]:     at new AuthorizationError (/app/node_modules/@slack/oauth/dist/errors.js:84:28)
2022-05-20T09:58:56.256051+00:00 app[web.1]:     at InstallProvider.<anonymous> (/app/node_modules/@slack/oauth/dist/index.js:253:31)
2022-05-20T09:58:56.256052+00:00 app[web.1]:     at step (/app/node_modules/@slack/oauth/dist/index.js:54:23)
2022-05-20T09:58:56.256052+00:00 app[web.1]:     at Object.throw (/app/node_modules/@slack/oauth/dist/index.js:35:53)
2022-05-20T09:58:56.256053+00:00 app[web.1]:     at rejected (/app/node_modules/@slack/oauth/dist/index.js:27:65)
2022-05-20T09:58:56.256053+00:00 app[web.1]:     at processTicksAndRejections (internal/process/task_queues.js:97:5) {
2022-05-20T09:58:56.256053+00:00 app[web.1]:   code: 'slack_bolt_authorization_error'
2022-05-20T09:58:56.256054+00:00 app[web.1]: }

Requirements (place an x in each of the [ ])**

• I've read and understood the Contributing guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.
• I've searched for any related issues and avoided creating a duplicate issue.

To Reproduce

Steps to reproduce the behavior:

1. Deploy via Heroku
2. Integrate to Company Slack
3. invite to channel
4. use the triage command

Expected behavior

A clear and concise description of what you expected to happen.
It should show a triage

Screenshots

If applicable, add screenshots to help explain your problem.

Reproducible in:

package version:
node version:
OS version(s):

Additional context

Add any other context about the problem here.

Description

Create and populate a docs/CONFIGURATION.md that talks through the options in config.js

Requirements (place an x in each of the [ ])

• I've read and understood the Contributing guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.
• I've searched for any related issues and avoided creating a duplicate issue.

Description

Unify/standardize logging

Consider winston, pino, etc.

Requirements (place an x in each of the [ ])

• I've read and understood the Contributing guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.
• I've searched for any related issues and avoided creating a duplicate issue.

Description

Slack APIs do not provide a timestamp of when a reaction was placed on a message, so using the Events API to capture reaction_added events will be necessary.

This also means we will need to start tracking message (or at least reaction) state in the database.

Requirements (place an x in each of the [ ])

• I've read and understood the Contributing guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.
• I've searched for any related issues and avoided creating a duplicate issue.

Description

People often put the current on call alias or user in an @mention of the channel topic. This feature request would implement an option to @mention that user during scheduled reminders (probably only if there are requests that meet the criteria, not every time)

Requirements (place an x in each of the [ ])

• I've read and understood the Contributing guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.
• I've searched for any related issues and avoided creating a duplicate issue.

Description

Support socket mode

Requirements (place an x in each of the [ ])

• I've read and understood the Contributing guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.
• I've searched for any related issues and avoided creating a duplicate issue.

Description

Encrypt bot tokens in database

Will need to rework upserting as Mongo field encryption helpers dont seem to support this method

Requirements (place an x in each of the [ ])

• I've read and understood the Contributing guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.
• I've searched for any related issues and avoided creating a duplicate issue.

Description

Improve UX by displaying "N days" instead of "X hours" (when X % 24)

Requirements (place an x in each of the [ ])

• I've read and understood the Contributing guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.
• I've searched for any related issues and avoided creating a duplicate issue.

Description

Some ideas:

• Allow changing of configurations (TBD: per team or per app server?)
• List team channels the app is in
• Allow triggering of the reminder ad-hoc (per channel?)

Requirements (place an x in each of the [ ])

• I've read and understood the Contributing guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.
• I've searched for any related issues and avoided creating a duplicate issue.

Description

In freestyle mode, I can get a CSV report for a channel that might have..

• A row for each message in the past N hours/days with:
  • the timestamp for when the data was collected (we may want to append the data at a certain interval so we can see the trend of reactions/threaded replies)
  • basic metadata about the message such as channel, timestamp, author, message content (text, blocks, attachments)
  • The total number of reactions
  • An object with all reactions and their counts
  • The total number of threaded replies
  • An object with all threaded replies

Requirements (place an x in each of the [ ])

• I've read and understood the Contributing guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.
• I've searched for any related issues and avoided creating a duplicate issue.

When trying to deploy the app to Heroku using app.json (following the instructions in docs/DEPLOY_Heroku.md), the following error is given:

• Couldn't find either the add-on service or the add-on plan of "mongolab:sandbox".

Describe the bug

Add information to Heroku deploy docs on how to modify config.js.

Basically, you'll need to follow https://help.heroku.com/XOBUHLKQ/why-do-i-see-a-message-you-appear-to-have-cloned-an-empty-repository-when-using-heroku-git-clone. Or more specifically:

heroku git:clone -a YOUR_HEROKU_APP_NAME
cd YOUR_HEROKU_APP_NAME
git remote add origin https://github.com/slackapi/template-triage-bot
git pull origin main
# make changes to config.js
git add . && git commit -m "a useful commit message"
git push

Requirements (place an x in each of the [ ])**

• I've read and understood the Contributing guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.
• I've searched for any related issues and avoided creating a duplicate issue.

Describe the bug

Hello, I've been chasing this one down for a bit, and think I found out what's going on.

When the underlying bot token for the triage bot expires (for whatever reason, it's still not entirely clear to me why Slack bot tokens go to account_inactive despite nobody doing anything or being deactivated), the solution is to re-auth. However, it looks like the new token doesn't save in MongoDB, and we still persist the other one.

Requirements (place an x in each of the [ ])**

• I've read and understood the Contributing guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.
• I've searched for any related issues and avoided creating a duplicate issue.

To Reproduce

Steps to reproduce the behavior:

1. Install the triage bot, persisting token xoxb-{...}
2. Have the token go to account_inactive – presumably you can deactivate the first user that installed the bot, or in my case it was just a time-based thing I believe
3. Re-install the bot
4. See how the old token is still stored in the database, resulting in a persistent broken integration

Expected behavior

The new token should replace the old one in the database

Screenshots

After re-auth:

ERROR processing {redacted}...
Error: An API error occurred: account_inactive

Reproducible in:

package version: 1.0.1
node version: v20.10.0
OS version(s): Mac OS, Heroku

Additional context

N/A

Description

If the app is only ever going to be based in a single workspace, we can probably branch the code such that we don't need a DB, instead storing the values in an environment variable.

Requirements (place an x in each of the [ ])

• I've read and understood the Contributing guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.
• I've searched for any related issues and avoided creating a duplicate issue.