Skip to main content
Once an administrator has connected your organization’s workspace and you have linked your own Slack account, these are the things you can do from Slack and from an issue’s page. Everything here works in public channels, and in private channels the app has been invited to once an administrator has allowed them; never in a channel shared with another workspace.

​
Create an issue from a message

Open the message’s More actions menu and choose Create ReasonOS issue. The first time, Slack lists it under More message shortcuts; after that it appears in the menu directly.
  1. A private form opens, filled from the message: the message’s first line as an editable title, and a description made of the message text followed by a line naming the Slack user it came from and a link to the message. A long message is excerpted and the form says so.
  2. Choose the project. The list holds the projects you can write issues in; if the channel has a project default, it is preselected.
  3. Edit, then confirm. Until you confirm, no issue exists. The result, Issue saved with an Open issue button, is shown to you alone; nothing is posted to the channel.
The issue records the message it came from, attributed by Slack user id. No branch or server is created. If the form timed out, submit it again: a form that already created its issue shows that issue instead of making a second one. If you have not linked your Slack account yet, a private Link your account dialog opens instead, with a Link account button. Press it, confirm the ReasonOS account shown is yours, then run the shortcut again. The link works once and expires after ten minutes. Choose Link to ReasonOS issue from the message’s More actions menu, pick the project and enter the issue number. The issue’s title and description are left unchanged; the message is added as its source and the thread becomes available for status updates and reply sync.

​
/reasonos

  • /reasonos Fix the export button opens the same create form with that text as the title (the first line, if there are several); /reasonos alone opens it with the title Issue from Slack.
  • /reasonos --template Bug report opens the form filled from the project’s Bug report template. This needs a project default for the channel; without one, or with a template name the project has no template for, the command answers privately and creates nothing.
The command has no source message, so the issue it creates is not tied to a thread. Use Link to ReasonOS issue on a message afterwards if it should be.

​
Status updates in the thread

An organization administrator who can write the issue and has linked their own Slack account can switch Slack updates on from the issue page, for the thread the issue was created or linked from. From then on a reply is posted in that thread when the issue starts, completes, is cancelled or reopens: the issue’s key, its title, the word Started, Completed, Cancelled or Reopened, and a link to the issue. Nothing else is posted; moving between statuses of the same kind is silent, and switching updates on does not replay earlier changes. A failed or uncertain update is shown on the issue page with a choice to retry or skip, so a reply is never silently sent twice.

​
Share replies both ways

An organization administrator who can write the project’s issues and has a linked Slack account can switch Sync replies with Slack on for a captured thread, from the issue page. Then:
  • A new reply in the Slack thread by a linked member who can write the issue appears as a comment on the issue, attributed to them and marked as coming from Slack. Replies by anyone who is not linked, and messages from before sync was switched on, are not read.
  • Comments on the issue stay in ReasonOS unless you send them: a comment box under a synced thread offers Send to Slack · #channel beside Send. Only a comment you send that way reaches the thread. A shared reply is at most 12,000 bytes.
  • Editing or deleting a comment or a message changes it only where you did it; the copy on the other side stays.
One Slack thread can sync with one issue. If you unlink your own account, your future replies are no longer imported; everyone else’s still are. If the administrator who switched the sync on unlinks theirs, the sync stops for that thread. Disconnecting the workspace stops every sync at once. What was already shared stays on both sides.

​
Issue previews

When an administrator has switched previews on for a channel, under Project settings → Work → Slack previews, a link to an issue that you post there unfurls into its key, title and status with a link. Previews show only for a link posted by a linked member who can read the issue; for anyone else, or for an issue that does not exist, the app stays silent. A preview is not updated when the issue changes afterwards.

​
AI-suggested drafts

When an administrator has enabled AI drafts in Slack for a project and chosen the model, the create form offers Suggest a draft… once you have picked that project.
  • A private confirmation shows exactly what will be sent: the title and description as they stand in the form, the project, the model and whose key pays for the call. Nothing is sent until you press Suggest.
  • The suggestion comes back as an editable title and description. The issue is still created only when you press Create issue.
  • One suggestion per form. To try again, open a new form.
  • What is sent is only the text in the form, up to 12,000 bytes. No message history, files, linked pages or other channel content is read. Text that contains one of the integration’s own credentials is refused; do not put secrets in an issue.
  • If the model is unavailable or the organization’s budget refuses the call, the form keeps working by hand.
You need permission to use AI agents in the project as well as write access to its issues, and the project’s AI draft budget must allow the call.

​
Channel feeds

A feed posts a project’s activity, or an initiative’s updates, into one public channel the ReasonOS app has been invited to. It is an administrator’s decision per channel; a channel receives nothing until a feed is added.
  • Project feeds: under Project settings → Work → Slack feeds, an administrator with write access to the project’s issues adds a feed by channel ID, chooses what to post — new issues, status changes, won’t-complete and reopen — optionally only for some statuses, and the cadence: as it happens, a daily summary, or a weekly summary. Each post carries the issue key, its title, what happened and who did it, with a link; never the description.
  • Initiative feeds: under Settings → Initiative feeds, an organization administrator chooses an initiative and a channel. Each published update posts the initiative, its health, the author and a link; the update’s text is included only where Include the update’s text is switched on.
  • As it happens gathers everything that happens within a minute into one post. Daily summaries are sent from 09:00 UTC and weekly ones from Monday 09:00 UTC; a summary lists up to 20 items and says how many more there were, and the rest follow in the next one. Nothing is posted when nothing happened.
  • Pausing a feed stops future posts and keeps its settings; editing or pausing discards anything still queued for it. Removing a feed stops it; posts already made stay in Slack. An organization can have up to 20 feeds.
  • A feed uses the permissions the app already has. Private channels, Slack Connect channels, archived channels and direct messages cannot receive a feed, and the app must be a member of the channel. If the channel or the administrator’s access changes, the feed pauses itself and says so.

​
Direct messages about your issues

Once an administrator has allowed direct messages (Reconnect to allow direct messages on the Slack settings page) and you have linked your account, open Settings → Slack → Slack notifications and switch Send me Slack messages on. It is off until you do. Choose which of these you want:
  • Assignments: when an issue is assigned to you, or taken from you.
  • Mentions: when someone mentions you in an issue or a comment.
  • Status changes: when an issue assigned to you starts, completes, is cancelled or reopens.
  • Due dates: one message a day, from 09:00 UTC, listing your issues due today or overdue; nothing when nothing is due.
Each message comes from the ReasonOS app as a direct message to the Slack account you linked, and carries the issue key, its title, the project, what happened and who did it, and a link to the issue — never the description or a comment’s text. You are not told about your own actions. At most a few messages a minute are sent to one person; further ones are queued and sent later, each still subject to your access and your choices at that moment, not necessarily in the order the events happened. Switching the whole thing off pauses every message and keeps your choices; anything that happened while it was off is not sent later. A message is only sent if you can still read the issue at that moment, so leaving a project ends its messages. Unlinking your account or the workspace being disconnected stops them too. Nothing is read from Slack for this, and nobody else receives your messages.

​
What the app never reads

  • Channel history before a thread’s reply sync was switched on, and any thread that has no sync.
  • Files, attachments and link contents.
  • Replies by people who have not linked their account are never imported or synced. (Slack still delivers its signed event to ReasonOS, which discards it; and the message you create an issue from may have been written by someone else — the issue records them as its source and you as its creator.)
  • Your name, email or profile: you are known by your Slack user id and the ReasonOS account you linked.

​
Limits