difference between issue, ticket, and part
ART-15716_KNOWLEDGE_NODE-8
for TicketsWe have a summarize option (it would resemble sparkle symbol) in the top right corner of the ticket view, which uses the ticket content to summarize the ticket\n\n7. Difference between Issues and Tickets\n\nTickets\xc2\xa0are for customer support\xe2\x80\x94tracking requests, problems, or questions from customers or prospects.\n\nIssues\xc2\xa0are internal work items for developers\xe2\x80\x94used to improve the product, fix bugs, or implement features. Issues can be linked to
Support queries related playbook
ART-1002_KNOWLEDGE_NODE-1
\xe2\x86\x92 Issues\n  Items to track customer requests/problems \xe2\x86\x92 Tickets\n\n\nGiven the converged nature of the DevRev platform, we have both Tickets, and Issues, so when do you use what? The answer is \xe2\x80\x9cit depends\xe2\x80\x9d on what your role is on the part you\xe2\x80\x99re creating the work item on. In general, issues should be restricted to those individuals that either own or contribute to a part. Tickets should be used for all customer/consumer (internal or
Tickets, Issues: When to Use Each
ART-1002_KNOWLEDGE_NODE-4
hold value\n  reduces noise as only valid issues are created/tracked\n  unifies the triage process for escalations between tickets and issues\n\n\nTL;DR\n\n\n  If you work on a part, you create issues\n  If you are a consumer/customer of a part, you create tickets\n\n'
Tickets, Issues: When to Use Each
ART-1946_KNOWLEDGE_NODE-27
synchronous or near-synchronous discussion that may be escalated to a ticket. Conversations are part of [Computer for Support Teams](./support).\n* A *ticket* is a work item created by the customer or consumer. Tickets are part of [Computer for Support Teams](./support).\n* An *issue* is a work item created by the builder or maintainer. Issues are part of [Computer for Builders](./build).\n* An *enhancement* is the parent of multiple issues that lead to a desired change to the product.
Core concepts | Computer by DevRev | DevRev
ART-1947_KNOWLEDGE_NODE-33
language is reflected in issues.\n\nIssues\n------\n\nLater on, a software engineer may start work on this ticket by creating an issue and breaking that issue into smaller pieces with tasks. An issue describes what the developer will work on and is created or accepted by someone who owns or works on the associated part of the product. This distinction allows developers to break up a ticket from an external user into issues as they see fit and delegate the work to other team members as
Apps | Computer by DevRev | DevRev
ART-1002_KNOWLEDGE_NODE-2
external) items.\n\nThe following figure shows a decision tree that will help you identify what work type you should be using (this is not global but part specific):\n\n\n\nFor example, if I work on part foo, I can create issues on it. However, if I am a consumer of part bar I would create tickets which would then be triaged and potentially escalated into an issue by that team.\n\nWhy\n\n\n  Noise and context switching kill productivity\n\n\nHistorically, a huge pain point has been that any
Tickets, Issues: When to Use Each
ART-1242_KNOWLEDGE_NODE-0
b'Tickets and issues | DevRev | Docs\n\n[![]()![]()](https://developer.devrev.ai/)\n\nPublic\n\nPublic\n\nSearch\n\n`/`\n\n[API Reference](/api-reference/getting-started)[works](/api-reference/works/tickets-and-issues)\n\nTickets and issues\n==================\n\nCopy page\n\n`works` endpoint\n\n\xe2\x84\xb9\xef\xb8\x8f A work item is a record of some work that has to be done for a customer (ticket) or for another builder or maintainer of a part (issue).\n\n\xf0\x9f\x93\x8c For more information
Tickets and issues | DevRev | Docs
ART-1447_KNOWLEDGE_NODE-0
b'[](/public/api-reference/works/tickets-and-issues)\n\nPublic\n\n[API Reference](/public/api-reference/getting-started)[Works](/public/api-reference/works/tickets-and-issues)\n\n#\n\nTickets and issues\n\n`works` endpoint\n\n\xe2\x84\xb9\xef\xb8\x8f A work item is a record of some work that has to be done for a customer (ticket) or for another builder or maintainer of a part (issue).\n\n\xf0\x9f\x93\x8c For more information about work items, refer to
Tickets and issues — DevRev | Docs
ART-1947_KNOWLEDGE_NODE-25
systems, important details that help define the *why* behind work is lost.\n\n\xf0\x9f\x8e\xa5 Video: Convergence: Bringing work together\n\nBy linking work items\xe2\x80\x94conversations and tickets for support, issues and enhancements for build\xe2\x80\x94together, DevRev preserves context. That context defines the problem and requirements for anyone who works on this issue. Moreover, both tickets and issues are always associated with [parts](/docs/product/parts), tying them to the overall
Apps | Computer by DevRev | DevRev
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