Currently the only way to set up a channel is by create a 'fake' user and setting the slack_channel as the channel id/string. This works but is a bit hacky.

Would be nice to concretely represent channels as first-class entities with their own options.

Once an incident has been resolved we have no need to keep it in the DB anymore.

Another that would be nice would be to schedule something every n minutes to check that all of the incidents we have as not resolved are still in that state. This can be periodic across all incidents or enqueued for n minutes after we receive an incident, or both 🤷‍♂

Add the ability to add a note to a specific incident.

Currently, you have to manually set up the PagerDuty Webhooks for every service you want slackerduty to know about, this is pretty laborious and unnecessary.

The PagerDuty API exposes endpoints to manage extensions which is what webhooks come under for them.

Would be cool to have some facility to manage adding/removing slackerduty webhooks via the web UI.

Not sure what the best way to maintain consistency between slackerduty & PagerDuty would be? Maybe ping the extensions endpoint and try to regex match on a slackerduty URL that matchers with the current organisations pager_duty_token?

We want to:

• Display a nice description of the issue raised, something like:

☁️ [Quotes Site] Client error: Timeout haendler.carwow.de
🐛 [RestfulResource::HttpClient::Timeout] Timeout: Service not responding
📝 app/controllers/offers_controller.rb:80
🔗 https://app.bugsnag.com/carwow/quotes-site/errors/5aeb4334a76a96001a3fa5f1

• Add the ability to forward only the bugsnag description to a given channel (or user?)

• Add the ability to add a note with the forward

Add a incidents view to logged in users on / root page.

Would be nice to have them self update (websockets? polling?)

• Show Incidents + status #26
• Show alert/ack/resolve info
• Allow ack/resolve
• Allow forward?

The action buttons to Acknowledge, Escalate, Resolve, Unacknowledge an incident need to be implemented.

• Acknowledge
• Resolve
• Unacknowledge (won't do)
• Escalate (won't do)

When a incident is raised through honeycomb we want to display that in a nice manner.

Showing the link might be enough as the graph should be previewed by default.

We should allow users / channels to subscribe only to specific escalation policies.

• Add ability to acknowledge, escalate, resolve
• Add ability to add a note to incident
• Add /slackerduty incidents [ID] command #4
• Add Honeycomb integration #2
• Add bugsnag integration #3
• Add ability to forward to a channel #3
• Add ability to forward with a optional message #3
• Docs / How-to install
• Better errors handling & feedback
• Get rid of activesupport stuff
• Subscribe (Web?)
• Unsubscribe (Web?)
• Subscriptions (Web?)
• List Policies (Web?)

https://api.slack.com/surfaces/tabs

Slack has added a 'home' tab for apps. It would be cool to use this as a way to give an overview of all/recent incidents.