manually create a linked ticket
ART-1947_KNOWLEDGE_NODE-36
Conversations can be immediately linked to a ticket, a ticket to an issue and subsequently to a part (product capabilities and features).\n\n| Link | Control |\n| --- | --- |\n| Conversation \xe2\x86\x92 Ticket | Open the conversation and click **Tickets > + Link tickets**. Either create a new ticket or select an existing ticket. |\n| Ticket \xe2\x86\x92 Issue | Open the ticket and click **Issues > + Link issues**. Either create a new issue or select an existing issue. |\n| Issue \xe2\x86\x92
Apps | Computer by DevRev | DevRev
ART-1979_KNOWLEDGE_NODE-39
other tickets or issues that relate to this ticket, click **Link Records** and select the relevant items.\n7. If you would like to immediately create another ticket, select **Create multiple**.\n8. Click **Create**.\n\nIf a ticket is created from an existing conversation, then the ticket's title and description are populated automatically from the conversation.\n\n![]()\n\nYou can create a child issue by clicking **+ Link issue** > **Add a child issue**. You can link the other existing issue as
Tickets | Computer for Support Teams | DevRev
ART-1947_KNOWLEDGE_NODE-37
Ticket | Open the issue and click **Tickets > + Link tickets**. Either create a new ticket or select an existing ticket. |\n| Issue \xe2\x86\x92 Issue | Open the issue and click **Issues > + Link issues**. Either create a new issue or select an existing issue. |\n\n| Conversation | Ticket | Issue |\n| --- | --- | --- |\n|  |  | > |\n\nTo delete a ticket or issue, select the work item in the list view and click the **Delete** icon in the taskbar that appears.\n\n![]()\n\n[PreviousCore
Apps | Computer by DevRev | DevRev
ART-6174_KNOWLEDGE_NODE-28
tickets\n--------------------------------\n\n**Manual conversion**\n\nGo to the conversation record pane and select **Convert to Ticket** to create a new ticket from the conversation.\n\n![]()\n\n**Automated conversion via workflows**\n\nSet up automated [workflows](./workflow-engine) to convert conversations to tickets based on specific triggers:\n\n* When a conversation meets defined criteria\n* When the AI agent identifies an issue requiring escalation\n* According to custom business
Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev
ART-1992_KNOWLEDGE_NODE-32
other [tickets](./tickets) or issues that relate to this issue, click **Link Records** and select the relevant items.\n7. If you would like to immediately create another issue, select **Create multiple**.\n8. Click **Create**.\n\nTags\n----\n\n* Stalled\n* Priority/Escalated\n* Fast/Slow Moving\n* Blocked\n* Resolution: [*values*]\n* Impact: [*values*]\n* Reason: [*values*]\n\nAn *autonomous issue* is an issue created automatically from an external event, such as a new VCS branch or pull
Issues | Computer for Builders | DevRev
ART-15664_KNOWLEDGE_NODE-9
--location \'https://api.devrev.ai/links.create\' \\ |\n| > | --header \'Content-Type: application/json\' \\ |\n| > | --header \'Authorization: Bearer <TOKEN>\' \\ |\n| > | --data \'{ |\n| > | "custom_link_type": "don:core:dvrv-us-1:devo/demo:custom_link_type/1", |\n| > | "link_type": "custom_link", |\n| > | "source": "don:core:dvrv-us-1:devo/demo:ticket/1", |\n| > | "target": "don:core:dvrv-us-1:devo/demo:custom_object/campaign/1" |\n| > | }\' |\n```\n\n##### \n\nWhen creating a link:\n\n* Set
Links | DevRev | Docs
ART-2048_KNOWLEDGE_NODE-27
allows you to create parent/child relationships between issues, you cannot do the same with tickets. If your workflow requires manual creation of parent/child relationships in DevRev work items, you should use issues. If that is not a requirement and tickets are preferred for another reason, you can specify tickets as the target for ClickUp tasks.\n\nImport from ClickUp\n-------------------\n\nFollow the steps below to import from ClickUp:\n\n1. In **Marketplace**, search for **ClickUp** and
ClickUp AirSync | AirSync | Snap-ins | DevRev
ART-4271_KNOWLEDGE_NODE-26
conversation metadata including: \n      * Source channel\n      * Customer account information\n      * External members added as **reported by** on the ticket\n    * An AI-generated ticket title and description based on customer messages.\n\n### How to convert Conversations to Tickets\n\n**Manual Conversion**\n\nTo manually convert a conversation to a ticket:\n\n  1. Open the conversation record pane view.\n  2. Click **Convert to Ticket** to initiate the conversion.\n\n**Automated Conversion
Convert Conversations to Tickets | Conversations | Support | DevRev
ART-2046_KNOWLEDGE_NODE-29
Ticket** button to create a ticket in DevRev by filling necessary attributes. You can turn this feature off in the app configuration if you want.\n* To view comments on the tickets linked to the discussions that support teams had with customers or internally on DevRev, head over to the DevRev activity tab which is present in the same line as the **Comments** tab of Jira.\n* To send comments from the Jira issue to the DevRev ticket, select the ticket from the dropdown, type in the comment, and
DevRev for Jira app | Jira Software AirSync | AirSync | Snap-ins | DevRev
ART-1947_KNOWLEDGE_NODE-32
same conversation. This means you do not need to ask your external users to write in separately about each topic they\'d like to discuss, while the workspace can still track each item separately.\n\nIn the DevRev app, a support engineer can create a ticket based on a conversation they had with someone using the Plug widget. This ticket and conversation are linked.\n\nA ticket should describe what the external user is experiencing in a language that\'s familiar to them. Developer-specific
Apps | Computer by DevRev | DevRev
ART-2046_KNOWLEDGE_NODE-28
configuration.\n3. Enable the desired features by toggling them on. Only enabled features will be visible to all users within your Atlassian organization.\n\nFeatures\n--------\n\n* The side panel on the Jira issue displays DevRev tickets linked to the Jira issue and their counterparts in DevRev.\n\n  ![]()\n* If there are multiple tickets linked to the issue, look at the details of each ticket by selecting a ticket with the dropdown field provided.\n\n  ![]()\n* Click on the **Create New
DevRev for Jira app | Jira Software AirSync | AirSync | Snap-ins | DevRev
ART-1558_KNOWLEDGE_NODE-278
authorization request.\n\nAPI Reference links Create.\n\nPOST https://api.devrev.ai / links.create\n\nCreates a link between two objects to indicate a relationship.\n\nRequest.\n\nThis endpoint expects an object.\nlink_type enum Required\n\nType of link used to define the relationship.\n\nShow 13 enum values\nsource string Required\n\nThe ID of the source object.\n\ntarget string Required\n\nThe ID of the target object.\n\nResponse.\n\nThis endpoint returns an object.\nlink object\nShow 9
Metric Definitions List (Beta) — DevRev | Docs
ART-1551_KNOWLEDGE_NODE-278
authorization request.\n\nAPI Reference links Create.\n\nPOST https://api.devrev.ai / links.create\n\nCreates a link between two objects to indicate a relationship.\n\nRequest.\n\nThis endpoint expects an object.\nlink_type enum Required\n\nType of link used to define the relationship.\n\nShow 13 enum values\nsource string Required\n\nThe ID of the source object.\n\ntarget string Required\n\nThe ID of the target object.\n\nResponse.\n\nThis endpoint returns an object.\nlink object\nShow 9
Update (Beta) — DevRev | Docs
ART-1547_KNOWLEDGE_NODE-278
authorization request.\n\nAPI Reference links Create.\n\nPOST https://api.devrev.ai / links.create\n\nCreates a link between two objects to indicate a relationship.\n\nRequest.\n\nThis endpoint expects an object.\nlink_type enum Required\n\nType of link used to define the relationship.\n\nShow 13 enum values\nsource string Required\n\nThe ID of the source object.\n\ntarget string Required\n\nThe ID of the target object.\n\nResponse.\n\nThis endpoint returns an object.\nlink object\nShow 9
Get Post (Beta) — DevRev | Docs
ART-1545_KNOWLEDGE_NODE-278
authorization request.\n\nAPI Reference links Create.\n\nPOST https://api.devrev.ai / links.create\n\nCreates a link between two objects to indicate a relationship.\n\nRequest.\n\nThis endpoint expects an object.\nlink_type enum Required\n\nType of link used to define the relationship.\n\nShow 13 enum values\nsource string Required\n\nThe ID of the source object.\n\ntarget string Required\n\nThe ID of the target object.\n\nResponse.\n\nThis endpoint returns an object.\nlink object\nShow 9
Create (Beta) — DevRev | Docs
ART-1564_KNOWLEDGE_NODE-278
authorization request.\n\nAPI Reference links Create.\n\nPOST https://api.devrev.ai / links.create\n\nCreates a link between two objects to indicate a relationship.\n\nRequest.\n\nThis endpoint expects an object.\nlink_type enum Required\n\nType of link used to define the relationship.\n\nShow 13 enum values\nsource string Required\n\nThe ID of the source object.\n\ntarget string Required\n\nThe ID of the target object.\n\nResponse.\n\nThis endpoint returns an object.\nlink object\nShow 9
List (Beta) — DevRev | Docs
ART-1543_KNOWLEDGE_NODE-278
authorization request.\n\nAPI Reference links Create.\n\nPOST https://api.devrev.ai / links.create\n\nCreates a link between two objects to indicate a relationship.\n\nRequest.\n\nThis endpoint expects an object.\nlink_type enum Required\n\nType of link used to define the relationship.\n\nShow 13 enum values\nsource string Required\n\nThe ID of the source object.\n\ntarget string Required\n\nThe ID of the target object.\n\nResponse.\n\nThis endpoint returns an object.\nlink object\nShow 9
Metric Definitions List Post (Beta) — DevRev | Docs
ART-1549_KNOWLEDGE_NODE-278
authorization request.\n\nAPI Reference links Create.\n\nPOST https://api.devrev.ai / links.create\n\nCreates a link between two objects to indicate a relationship.\n\nRequest.\n\nThis endpoint expects an object.\nlink_type enum Required\n\nType of link used to define the relationship.\n\nShow 13 enum values\nsource string Required\n\nThe ID of the source object.\n\ntarget string Required\n\nThe ID of the target object.\n\nResponse.\n\nThis endpoint returns an object.\nlink object\nShow 9
List Post (Beta) — DevRev | Docs
ART-1566_KNOWLEDGE_NODE-278
authorization request.\n\nAPI Reference links Create.\n\nPOST https://api.devrev.ai / links.create\n\nCreates a link between two objects to indicate a relationship.\n\nRequest.\n\nThis endpoint expects an object.\nlink_type enum Required\n\nType of link used to define the relationship.\n\nShow 13 enum values\nsource string Required\n\nThe ID of the source object.\n\ntarget string Required\n\nThe ID of the target object.\n\nResponse.\n\nThis endpoint returns an object.\nlink object\nShow 9
Transition (Beta) — DevRev | Docs