ticket stopped syncing with Slack
ART-2035_KNOWLEDGE_NODE-40
channel determines the sync location in DevRev:\n\n* **External/Connect channels:** Syncs with the **Customer Messages** panel.\n* **Internal channels:** Syncs with the **Internal Discussions** panel.\n\nSyncing different panels to separate Slack threads is not supported.\n\n![]()\n\nOnly shared tickets are synchronized between DevRev and Slack.\n\n### Follow-up and merged Tickets\n\nThe Slack snap-in supports follow-up and merged tickets.\n\n* When two tickets merge, and both have syncing
Slack | Integrate | Snap-ins | DevRev
ART-2035_KNOWLEDGE_NODE-41
Slack threads, all the messages from both Slack threads reach only the primary ticket in DevRev, while messages from DevRev only sync to the primary ticket\xe2\x80\x99s Slack thread.\n* If only one ticket has a syncing Slack thread, that thread syncs with the primary ticket.\n* No messages from the duplicate ticket sync to Slack.\n* If a ticket is immutable but receives a new customer message in its Slack thread, a follow-up ticket is automatically created for future discussions.\n\n### New
Slack | Integrate | Snap-ins | DevRev
ART-2035_KNOWLEDGE_NODE-39
fields will auto-fill based on the messages.\n\n### Ticket sharing options\n\nThe new ticket modal in Slack includes a **Share with everyone** checkbox at the bottom:\n\n* **Enabled:** Shares the ticket details with the Slack channel via a summary card.\n* **Disabled:** Keeps the ticket internal with no updates to the Slack channel.\n\nRegardless of sharing, the ticket details are visible to the creator in the submission modal.\n\n### Syncing details\n\nIf sharing is enabled, the type of Slack
Slack | Integrate | Snap-ins | DevRev
ART-2035_KNOWLEDGE_NODE-57
**Slack snap-in event discussions panel** to automatically invite the DevRev app to all public channels.\n  + Private channels still require manual addition.\n\n### When sync is not possible\n\nIf sync isn\xe2\x80\x99t possible, the form will display a clear warning. Possible reasons include:\n\n* The thread is already in sync with another DevRev object.\n* Sync is not supported for the object in the given Slack channel.\n* The DevRev app is not a member of the channel.\n* The channel is
Slack | Integrate | Snap-ins | DevRev
ART-4199_KNOWLEDGE_NODE-27
message.channels.\n7. Add this custom app and the **DevRev Slack Bot** into the Slack channel from which you want to create the DevRev object.\n\nConfigure DevRev\n----------------\n\n1. Add the Slack Signing Secret and Slack Bot Token copied from the custom Slack bot app.\n2. Add the channel IDs for either incidents, tickets or issues.\n3. Click the respective buttons to enable the sync between threads.\n4. Select the part ID to associate a particular part.\n5. Click **Save** and copy the
Slack message agent | Automate | Snap-ins | DevRev
ART-2035_KNOWLEDGE_NODE-55
Set up 2 way message synchronization between a complete Slack channel and DevRev object discussion. | - Slack connection   - DevRev object ID   - Slack channel ID | N/A |\n\nAdditional capabilities and limitations\n---------------------------------------\n\n### 2-way sync between DevRev and Slack\n\n* If two-way sync is enabled on an object, new messages received from non-Slack source channels will appear in DevRev but won't sync to the Slack thread.\n* By default, messages from bots, service
Slack | Integrate | Snap-ins | DevRev
ART-2035_KNOWLEDGE_NODE-33
DevRev app.\n\nIf a message is sent to a Slack thread belonging to an archived conversation, the Slack snap-in creates a new follow-up conversation, and all messages sync to this new conversation.\n\n![]()\n\nA Slack channel can be linked to only one DevRev account workspace, and vice versa.\n\nConversation roll window\n------------------------\n\nTo avoid multiple conversations for related customer messages, a **conversation roll window** is used.\n\n* The roll window remains active for five
Slack | Integrate | Snap-ins | DevRev
ART-2045_KNOWLEDGE_NODE-58
synced items is not propagated. This includes works (issues or tickets), accounts, users, links, and other types. When an item is deleted (either in DevRev or at the source) and that item exists at the other end, it will not be deleted but no further updates to it will be made.\n\n### References\n\n* In-text references (such as @mentions) will not be remapped.\n\n### Schema changes\n\n* If a new type is added to the external source after the initial sync, it will not be automatically picked up
AirSync | Snap-ins | DevRev
ART-2035_KNOWLEDGE_NODE-34
minutes after a conversation is created.\n* Any new message sent directly in the channel within this time frame is appended to the existing conversation.\n* A new direct message from the customer resets the roll window timer.\n* Any message sent from DevRev will be synced to the thread of the first message that initiated the conversation.\n* Only messages within the thread of the originating message of the conversation are synced.\n* Messages within Slack threads of follow-ups sent directly to
Slack | Integrate | Snap-ins | DevRev
ART-2035_KNOWLEDGE_NODE-58
private or a DM.\n\n> In such cases, the object can still be created, but without two-way sync.\n\nDevRev object customization support\n-----------------------------------\n\nThe Slack snap-in honors DevRev\xe2\x80\x99s object customizations, including:\n\n* Custom fields and subtypes\n* Stock field overrides\n* Slack-specific client overrides\n* Summary view card\n\nThe summary view card of all objects can be customized.\n\n* Only fields marked with **Show in Summary = true** in object
Slack | Integrate | Snap-ins | DevRev