parts when creating an issue
ART-1992_KNOWLEDGE_NODE-26
importance of the issue. Priorities can be set to P0, P1, P2, and P3. P0 is the highest priority and P3 is the lowest.\n* **Stage**: The current state of the issue. The stage attribute is used to track the progress of the issue through its lifecycle. For more information on stages, see [stages](#stages).\n* **Part**: The part of the company or product that the issue is related to. For more information on parts, see [parts](./parts).\n* **Created by**: The person who created the issue.\n*
Issues | Computer for Builders | DevRev
ART-1992_KNOWLEDGE_NODE-31
on the top right corner of your screen.\n3. Add a title and description for your new issue. You can also attach files related to the issue in the description.\n4. Select which part of the company/product this issue is related to.\n\n   ![]()\n5. Enter other attributes for the issue: change the assignee or accept the default; enter the severity; add any relevant tags to help employees identify any relevant traits of the issue; select the workspace that the issue pertains to.\n6. If there are
Issues | Computer for Builders | DevRev
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-1950_KNOWLEDGE_NODE-46
or bug fix to include it in the release notes.\n* **Customer impact**: The impact of the part on the customer.\n* **Target close date**: The date by which the part is expected to be resolved.\n* **Target start date**: The date by which the part is expected to start.\n\nYou can add custom attributes to issues to track additional information. For more information on custom attributes, see [object customization](./object-customization).\n\nSubtypes\n--------\n\nYou can create subtypes of issues to
Parts & trails | Computer by DevRev | DevRev
ART-1979_KNOWLEDGE_NODE-29
**Severity**: The importance of the ticket. Severity can be set to low, medium, blocker, or high.\n* **Stage**: The current state of the issue. The stage attribute is used to track the progress of the issue through its lifecycle. For more information on stages, see [stages](#stages).\n* **Part**: The part of the company or product that the issue is related to. For more information on parts, see [parts](./parts).\n* **Created by**: The user who created the ticket.\n* **Created date**: The date
Tickets | Computer for Support Teams | 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-8441_KNOWLEDGE_NODE-36
off if you choose to explicitly create issues and link your GitLab activity or you can enable it either for PR creation or branch creation event.\n* Select the default part under **Default part for autonomous issues** as a default Part ID if you enable **Track autonomous work**. Autonomous issues originating from GitLab are attributed to a default part. You can configure the default part while setting up your snap-in. Every issue in DevRev must have a part attribution.\n\n### Autonomous work
GitLab | Integrate | Snap-ins | DevRev
ART-2030_KNOWLEDGE_NODE-37
disabled if you choose to explicitly create issues and link your Bitbucket activity or you can enable it either for PR creation or branch creation event.\n* Select the default part under **Default part for autonomous issues** as a default Part ID if you enable **Track autonomous work**. Autonomous issues originating from BitBucket will be attributed to a default part. You can configure the default part while setting up your snap-in. Every issue in DevRev must have a part attribution.\n\n###
Bitbucket | Integrate | Snap-ins | 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-1992_KNOWLEDGE_NODE-28
various vistas in DevRev to track specific work, capacity, and more.\n\nYou can add custom attributes to issues to track additional information. For more information on custom attributes, see [object customization](./object-customization).\n\nIssues are attached to parts in order to align efforts with product priorities.\n\nAs to the size of an issue and the flexibility it offers to manage changes in size, issues offer hierarchy in the form of parent-child relationships and granularity.\n\nFrom
Issues | Computer for Builders | DevRev
ART-1961_KNOWLEDGE_NODE-31
needed. For example, if the ticket is found to be spam, you can automatically add a comment to the ticket.\n\n**Suggest part**\n\nOften, your integrations create tickets or issues associated with a default part. The suggest part takes the ID of a ticket or issue and suggests a relevant part. You can use this to route your tickets or issues to the most appropriate part of the product. For example, when a ticket is created, you can find a relevant part and update the ticket with the suggested
Workflows | Computer by DevRev | DevRev
ART-1651_KNOWLEDGE_NODE-439
https://api.devrev.ai/works.create \\ > -H " Authorization: Bearer <token> " \\ > -H " Content-Type: application/json " \\ > -d \' { > "type": "issue", > "applies_to_part": "string", > "owned_by": [ > "string" > ], > "title": "string" > } \'\n200 Successful 1 { 2 " work " : { 3 " type " : " issue " , 4 " actual_start_date " : " 2023-01-01T00:00:00Z " , 5 " developed_with " : [ 6 { 7 " type " : " capability " , 8 " name " : " string " , 9 " owned_by " : [ 10 { 11 " type " : " dev_user " , 12 "
Create — DevRev | Docs
ART-1994_KNOWLEDGE_NODE-33
sprint board and click **+Issue**.\n   Create a new issue, assign it to the part, sprint and add the owner.\n\n   ![]()\n\n   Sprints are not coordinated with stages.\n3. Select issues that you would like to assign to **Sprint 1** or **Sprint 2** then click **Move** in the toolbar at the top of the screen and select the sprint.\n\n   ![]()\n4. Go to **Sprint 1** or **Sprint 2** to see that issues are displayed.\n\n   ![]()\n\n   The sprint is also displayed in (and can be changed from) the
Sprint mode | Computer for Builders | DevRev
ART-1957_KNOWLEDGE_NODE-31
can select a date in this field. For example, "Date of bug identified: 19/07/2024".\n     + **Part**: Select the part to which this object belongs. It could be an enhancement, feature, capability, runnable, linkable, or product.\n     + **Dev user**: Select one or multiple users from the dropdown.\n     + **Customer**: Assign the object to an existing customer workspace.\n     + **Account**: Assign the object to a customer account.\n     + **Workspace**: Assign the object to a workspace.\n\n
Object customization | Computer by DevRev | DevRev
ART-1275_KNOWLEDGE_NODE-18
= `Ticket created at ${date.toLocaleString()}`; |\n| 14 | const ticketBody = `This ticket was created by a snap-in at ${date.toLocaleString()}`; |\n| 15 |  |\n| 16 | const response = await devrevSDK.worksCreate({ |\n| 17 | title: ticketName, |\n| 18 | body: ticketBody, |\n| 19 | // The ticket is created in the PROD-1 part. Rename this to match your part. |\n| 20 | applies_to_part: "PROD-1", |\n| 21 | // The ticket is owned by the DEVU-1 user. Rename this to match the required user. |\n| 22 |
Using a snap-in to perform a DevRev action | DevRev | Docs
ART-1483_KNOWLEDGE_NODE-21
devrevSDK.worksCreate({  \n    17|       title: ticketName,  \n    18|       body: ticketBody,  \n    19|       // The ticket is created in the PROD-1 part. Rename this to match your part.  \n    20|       applies_to_part: "PROD-1",  \n    21|       // The ticket is owned by the DEVU-1 user. Rename this to match the required user.  \n    22|       owned_by: ["DEVU-1"],  \n    23|       type: publicSDK.WorkType.Ticket,  \n    24|     });  \n    25|   \n    26|     console.log(response);  \n
Using a snap-in to perform a DevRev action — DevRev | Docs
ART-1979_KNOWLEDGE_NODE-38
the top-right corner of your screen.\n3. Add a title and description for your new ticket. You can also attach files related to the ticket in the description.\n4. Select which part of the company/product this ticket is related to.\n\n   ![]()\n5. Enter other attributes for the ticket: change the assignee or accept the default; enter the severity; add any relevant tags to help employees identify any relevant traits of the ticket; select the workspace that the ticket pertains to.\n6. If there are
Tickets | Computer for Support Teams | DevRev
ART-15989_KNOWLEDGE_NODE-24
[Snap-ins](/docs/snapins)\n[Automate](/docs/automate)\n[Automated part update](/docs/automations/automated-part-update)\n\nAutomated part update\n=====================\n\nThe Automated part update snap-in streamlines the updating of issue or ticket parts based on the initial part and target field defined in its configuration. It monitors the creation events of issues and tickets, ensuring that new entries match the part specified in the **Initial Part of Issue/Ticket** input field. Upon
Automated part update | Automate | Snap-ins | DevRev
ART-1950_KNOWLEDGE_NODE-25
be recursively made of smaller parts. Events and work items must be related to parts. In general, parts are the core objects that almost all other objects are linked to, which helps enforce the notion of tying everything back to the product or service.\n\n\xf0\x9f\x8e\xa5 Video: Trails\n\n*Trails* is an extensible interface that allows you to view and manage your part hierarchy and related items. Think of it like a graph canvas that\'s rendering linkages among items\xe2\x80\x94including
Parts & trails | Computer by DevRev | DevRev
ART-17231_KNOWLEDGE_NODE-102
to which the issue belongs. |\n| `stage` | enum | \xe2\x9c\x94\xef\xb8\x8e | Stage of the object |\n| `tags` | reference (collection)\xe2\x86\x92[#record:tag] |  | Tags associated with the object |\n| `target_close_date` | timestamp |  | Timestamp when the work is expected to be complete |\n| `target_start_date` | timestamp |  | Target start date for the object |\n| `title` | text | \xe2\x9c\x94\xef\xb8\x8e | Title of the work object |\n\n#### Enum values\n\n**priority**\n\n| Value | Name |
Supported DevRev object types | DevRev | Docs
ART-17231_KNOWLEDGE_NODE-99
User ID of the user that created the object |\n| `estimated_effort` | float |  | Estimated effort to complete the issue |\n| `fallback_parts` | reference\xe2\x86\x92[#category:part] |  | Other values that could serve as part if apples\\_to\\_part\\_id is found to be invalid. |\n| `item_url_field` | text |  | Link to the item in the origin system |\n| `modified_by_id` | reference\xe2\x86\x92[#category:user] |  | User ID of the user that last modified the object |\n| `owned_by_ids` | reference
Supported DevRev object types | DevRev | Docs
ART-1637_KNOWLEDGE_NODE-437
object.\nIssue Show 19 properties\nOR\nOpportunity Show 21 properties\nOR\nTask Show 17 properties\nOR\nTicket Show 21 properties\nResponse.\n\nThis endpoint returns an object.\nwork object\nShow 4 variants\nPOST / works.create\ncURL\n$ curl -X POST https://api.devrev.ai/works.create \\ > -H " Authorization: Bearer <token> " \\ > -H " Content-Type: application/json " \\ > -d \' { > "type": "issue", > "applies_to_part": "string", > "owned_by": [ > "string" > ], > "title": "string" > } \'\n200
Delete — DevRev | Docs
ART-2010_KNOWLEDGE_NODE-25
from a CSV file. The CSV file supports the following columns:\n\n```\n```\n1 Title,Description,Owners,Part,Tags,Subtype,WorkType\n\n\n\n2 Front page not loading,"This is a sample ticket body with \xe2\x80\x9c\xe2\x80\x9d quotes",youremail@example.com,PROD-1,frontend,subtype1,Ticket\n\n\n\n3 APIs returning errors,"The user.get API is returning 500",youremail@example.com,PROD-2,backend,subtype2,Issue\n```\n```\n\nThe Title column is required, while the others are optional. If the WorkType column
Bulk work item uploader | Automate | Snap-ins | DevRev