Talk to your Director in Slack.
Connect each project's Director to its own Slack app. Your team asks it questions in Slack, and digests and alerts land in your channel.
Stalled: #409 Fatal error on PHP 8.3 has had no update for 2 days. @Riza, can you take it?
@Formwise Director what is the fix?
is searching tickets…
It is our bug on PHP 8.3, and PR #422 fixes it. Until it ships, saving the settings page once gets them going.
Three kinds of message. Each one names the person who should act.
Nobody wants one more tab to check. The Director answers where your team already talks.
Daily digest
Once a day, in your alerts channel.
Good morning. 8 open tickets:
• 2 unanswered: #415, #416
• 1 stalled: #409 (@Riza)
• 1 draft ready: #412 (@Riza)
Stall alert
When a ticket gets no update.
Stalled: #409 Fatal error on PHP 8.3 has had no update for 2 days. @Riza, can you take it?
Answers in the thread
Ask it anything. It shows what it is doing.
@Formwise Director is #409 our bug?
is searching tickets…
Yes, on PHP 8.3. PR #422 fixes it.
Connected from project settings, in four steps.
Each project connects its own Slack app, named after that project's Director.
1Create the Slack app
Generate the app manifest in project settings, then install the app in your workspace.
2Paste the tokens
The bot token and the app token. They stay in a secret file on your server.
3Pick who and where
Who may talk to the Director, and the channel for alerts.
4Ask away
Message the Director in Slack and watch the answer stream in.
Common questions.
Anything else? Write to [email protected] and a human answers.
Does each project need its own Slack app?
Yes. Each project connects its own Slack app, named after that project's Director.
Who can talk to it?
Everyone in your workspace, or only the Slack users you allow. People are matched to Repile members by email.
Where are the Slack tokens kept?
On your own Repile server, in a secret file. Never in a database or in the app.