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. Features that use a channel work 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. Global creation has no source channel.

Create an issue from a message

Open the message’s More actions menu and choose Create ReasonOS issue. Slack may place app shortcuts under Connect to apps → More message shortcuts. Search there for ReasonOS if it is not listed. Slack controls this menu placement; the app cannot guarantee a top-level entry. For creation without a source message, you can also use the existing /reasonos command.
  1. A private form opens, filled from the message: the message’s first line as an editable title (a colon does not split a single-line message), and a description made of the remaining lines, so the title is not repeated, followed by a line identifying the Slack user it came from. A first line longer than 150 characters is cut there and the rest carried into the description. The line identifying the author shows a readable name only when you are the message’s author and the shortcut supplies your name; otherwise it shows the Slack user id, because the app never looks up anyone’s profile. The source message is linked separately on the issue. 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. Optionally set Status, Assignee and Priority. Status and assignee list that project’s own columns and the people who can be assigned there; leave any of them empty to get the usual Work default. Choosing another project refreshes the form: your title and description stay, the status and assignee are cleared because they belong to the old project, and the priority is kept. If the choices cannot be shown, for example because a project has more people than a Slack list holds, the form says so and the issue is created with the Work defaults; set them in ReasonOS afterwards.
  4. Edit, then confirm. Until you confirm, no issue exists. The result, Issue saved with an Open issue button, is shown to you alone. Existing feed and personal-notification opt-ins still apply to the new issue.
If the message is already the source of an issue in a project you can write in, the form begins with Already linked to and that issue’s key and title, linked to the issue. It is a reminder, not a block: you can still create a second issue on purpose. If the app cannot check, the form says so rather than showing nothing. The issue records the message it came from. No branch or server is created. The form expires after ten minutes. If a confirmation response times out, check the issue in ReasonOS before trying again. Repeating the same completed submission recovers its issue under your current access instead of making another one; an expired, uncompleted form needs to be reopened. If you have not linked your Slack account yet, a private Link your account dialog opens instead, with a Link account button. Press it, check the Slack and ReasonOS accounts shown, choose Link this Slack account, then run the shortcut again. The link works once and expires after ten minutes.

Create without selecting a message

Use Slack’s composer shortcuts or search for Create ReasonOS issue to open a blank private form. Choose a project, enter a title and description, and confirm. The optional status, assignee and priority choices appear once a project is chosen, as in the message form. This entry has no source message or channel: it creates no Slack source link or synced thread. The shortcut answers privately; configured Work feeds and personal notifications still follow their existing opt-ins. Use the message shortcut when the issue should retain its original conversation. This global shortcut becomes available after the app operator deploys a supporting build and registers it for the workspace. If it is not listed, use the existing /reasonos command in a channel, or ask your administrator whether the updated shortcut is available. Global creation does not select a channel-default template or offer AI drafts. After you confirm, the Issue saved dialog says no Slack message was selected when you created the issue, so none is attached yet, and names the two ways to attach one. The easiest: close the dialog first (a Slack dialog blocks the channel behind it), then open that message’s More actions (⋯) → Link to ReasonOS issue and choose the issue by its key there. The other: press Link to a Slack message and paste the message’s link (copy it from the message’s More actions (⋯) → Copy link). Either way the message becomes the issue’s source, thread included, so status updates and reply sync can be switched on from the issue page; linking switches on neither by itself. Only messages in this workspace, in a channel the app can see, can be linked; the issue linked is the one you just saved.

The app’s Home tab

Open ReasonOS under Apps in Slack’s sidebar. Its Home tab is a private starting point, not a workspace: it shows how to create and link issues and offers buttons that open the same private forms as the shortcuts. It lists no projects or issues. The forms are private; an issue you create from here still reaches any channel feeds its project or initiative has opted into, as with every other way of creating one.
  • If your account is not linked yet, the only button is Link your ReasonOS account. It opens the private Link your account dialog; its Link account button opens the usual confirmation in your browser.
  • Once linked, Create issue opens the blank form described above (no source message, no channel). Link a message to an issue asks for the project, the issue (by status and search, described below) and the message’s link: open the message’s More actions menu, choose Copy link, and paste it. The link is required and must point to a message in this workspace, in a channel the app can see. The message becomes the issue’s source, with its title and description unchanged. Unlike the message shortcut, a message linked this way does not get status updates or reply sync; use Link to ReasonOS issue from the message itself when you want those.
The Home tab becomes available after the app operator deploys a supporting build and switches the tab on for the app. Until then the Apps entry shows nothing, or only Slack’s default page; the shortcuts and /reasonos work regardless.

Return to the source message

When the issue was created from a message, or a message was linked to it with Link to ReasonOS issue, the issue’s Slack section offers Open source message in Slack and Copy link. A message linked from the Home tab, and an issue created with /reasonos or the global shortcut and never linked, have no Slack section; the source, if any, is in the Links section. Expand Source link to select the complete URL, including its thread parameters, if clipboard access is unavailable. Existing descriptions are kept as written; newly created issues do not automatically repeat the source URL in the description. The Links section labels the same destination Slack source message. The HTTPS link may open your browser before Slack. If Slack reports that the browser is unsupported, copy the link and open it in Slack or a supported browser. That browser warning does not mean the source message was lost. Choose Link to ReasonOS issue from the message’s More actions menu. Pick the project, narrow by status if you like (Open issues is the default; All and each of the project’s own statuses are there too), then find the issue by its key, such as PAY-12, or by words from its title. If the message already sources an issue you can write in, the form begins with Already linked to that issue, so you do not link it twice. Changing the project or the status clears the issue choice, so what you link always belongs to the project and filter you see. 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 Post status updates to Slack on in the issue’s Slack section, 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: one line with the issue’s key, its title (cut at 240 characters) and the word started, completed, cancelled or reopened, then 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. While Work is switched off for the project, or the account’s plan no longer includes it, the thread’s activity is paused: a status change made meanwhile is recorded as stopped at once and is never posted, even after Work comes back; a reply arriving meanwhile is not copied; the switches stay as they were (an issue still open on screen shows the thread as paused when refreshed; the project’s Work pages themselves are hidden while Work is off). The next change after Work is on again posts as usual. 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 comments 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 (or Send to linked Slack thread for a thread linked before ReasonOS recorded the channel’s name) 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 Open issue, Change status and Assign buttons. 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.

Change status or assignee from a preview

New issue previews offer Change status and Assign. Each opens a private form, with the project’s current statuses, or its current Work members and Unassigned; choosing does nothing until you confirm. You need a linked Slack account and current write access to the issue. The form expires after ten minutes. If someone changes the issue or its status choices while the form is open, reopen the action to review the current values. A retry of the same completed submission recovers its original result under your current access, without overwriting later issue edits. A different selection cannot reuse the completed form. Paused connectivity, disabled previews or revoked access stop new changes. Existing previews are not automatically refreshed or given new buttons; the actions appear on previews sent by the updated build.

AI-suggested drafts

When an administrator has enabled AI drafts in Slack for a project and chosen the model, the message-shortcut or /reasonos create form offers Suggest a draft… once you have picked that project. The global shortcut does not offer AI drafts.
  • A private confirmation shows what will be sent: the title and description as they stand in the form (the first 300 characters, with a note that the full text is sent, when it is longer), 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, or that matches common credential patterns (such as a private key, some API token formats or a password= value), is refused with a request to remove it. The check cannot catch every secret, so 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 plan must include AI draft suggestions. Suggestions also stop if the administrator who switched them on is no longer a member of the organization, or no longer has organization settings and Work write access for the project, until another administrator saves the setting again.

Channel feeds

A feed posts a project’s activity, or an initiative’s updates, into a non-shared channel the ReasonOS app has joined. Private channels also need an administrator to choose Allow private channels. Each feed is an administrator’s decision; a channel receives nothing until a feed is added.
  • Project feeds: open Project settings → Work → Slack feeds. Choose Add feed, give it a name, and search for the channel by name. The picker offers channels the app has joined and labels private channels. Load more channels continues the list; search covers the loaded results. If discovery fails or a channel is missing, use Enter channel ID manually. Saving always checks current access with Slack.
  • Choose new issues, status changes, won’t-complete and reopen, optionally limited to selected statuses, and a cadence. Normal notices carry the issue key, title, event, actor and link. Descriptions are excluded by default.
  • Include description on new issues separately opts in to a short description excerpt on creation. Description changes separately enables notices when a description changes. Either can be enabled without the other. Both share text with everyone in the channel, so check that channel’s audience first.
  • Excerpts use the current description when the post is prepared, rather than a historical diff. They collapse whitespace, include up to 500 characters, mark truncation, and link to the full issue. Empty descriptions are stated explicitly. No attachments are included. Rapid pending edits of one issue are combined; turning an option on never imports old descriptions or replays past changes.
  • Initiative feeds: under Settings → Initiative feeds, choose an initiative and a channel with the same name picker or manual-ID fallback. Published updates carry the initiative, health, author and link. Update text is included only where Include the update’s text is on; this is separate from project issue-description settings.
  • As it happens gathers a minute’s activity into one post. Daily summaries become eligible from 09:00 UTC and weekly summaries from Monday 09:00 UTC. Posts contain up to 20 items; the post says how many more remain queued. Nothing is posted when nothing happened.
  • Choose a feed’s visible Edit action to change it, then Save changes. Slack connection settings ↗ opens the organization connection settings; its helper text explains how unsaved changes are kept for the return trip.
  • Pausing stops future posts and keeps settings. Editing or pausing retires old queued content; already dispatched posts cannot be recalled. Removing a feed stops it, and posts already made stay in Slack. An organization can have up to 20 feeds.
  • No extra Slack permission is requested by channel discovery. Public channels use the existing connection; private channels require the separate private-channel grant. Slack Connect/shared channels, archived channels and direct messages are refused. If the channel or an administrator’s access changes, the feed pauses and explains recovery.

Direct messages about your issues

Once an administrator has allowed direct messages (Authorize direct messages on the Slack settings page) and you have linked your account, open Settings → Organization → Integrations → Slack, find Slack notifications, and switch Send me Slack notifications on. It is off until you do, and it is your choice alone: an administrator’s authorization sends nothing by itself. 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 email or profile through a separate lookup. Account-link confirmation can show names already included in Slack’s verified shortcut request; identity remains the Slack user ID and the ReasonOS account you linked.

Limits