{% extends "sentry/bases/modal.html" %} {% load crispy_forms_tags %} {% load sentry_assets %} {% load i18n %} {% block wrapperclass %}narrow auth{% endblock %} {% block modal_header_signout %}{% endblock %} {% block title %}{% trans "Slack Migration" %} | {{ block.super }}{% endblock %} {% block css %} {% endblock %} {% block main %} {% script %} {% endscript %}
{% trans "The time has come, Slack's deprecated its workspace apps. And with it, goes our legacy Slack integration." %}
{% trans "But don't worry, we built you a whole new Sentry-Slack integration. Just authorize the app, and then you can get back to doing whatever it is you came here to do." %}
{% blocktrans %} Want to know more about the move? We wrote you some docs. {% endblocktrans %}
{% trans "If you don't have private channels in your alert rules, just authorize our new Slack app and then you can get on with your life." %}
{% blocktrans %} If you do have private channels being used in your alert rules, bear with us. You've got an extra step to go. {% endblocktrans %}
{% blocktrans %} How do you know which channels are used in alert rules? We'll tell you. Our next step audits your configuration to identify which channels need some post-authentication love. Bear in mind that if you've got a lot of Slack channels with alert rules, this might take a hot minute. {% endblocktrans %}
{% if extra_orgs %}{% blocktrans %} Your Slack workspace, {{workspace}}, is installed on additional organizations: {% endblocktrans %} {% for org in extra_orgs %} {{org}} {% endfor %} {% trans "Once you've upgraded your integration, all other organizations with the same workspace will be upgraded as well." %}
{% endif %} {% endblock %}