bulk upload of bugs on devrev
ART-2010_KNOWLEDGE_NODE-24
uploader](#how-to-use-bulk-ticket-uploader)\n\n1. [Documentation](/docs)\n3. [Snap-ins](/docs/snapins)\n[Automate](/docs/automate)\n[Bulk work item uploader](/docs/automations/bulk-upload)\n\nBulk work item uploader\n=======================\n\nThe [bulk work item uploader](/marketplace/bulk-ticket-uploader) enables you to upload multiple tickets or issues from a CSV file to DevRev. It\'s useful when migrating work items from a third-party system to DevRev or creating tickets or issues in bulk
Bulk work item uploader | Automate | Snap-ins | DevRev
ART-2010_KNOWLEDGE_NODE-28
user ID mentioned in a row doesn\'t exist. Other work items aren\'t impacted by this.\n* The workspace ID is only used for associating tickets to the workspace and not issues.\n* If the CSV lists multiple owners, only the first is set as the owner in the DevRev work item.\n\nHow to use bulk ticket uploader\n-------------------------------\n\n1. In the **Discussion** tab of an account, ticket, part, or issue, enter /upload\\_workitems.\n   A **Bulk Uploader Bot** form appears.\n2. From the
Bulk work item uploader | Automate | Snap-ins | DevRev
ART-2010_KNOWLEDGE_NODE-27
issues, refer to [Issues](https://docs.devrev.ai/product/issues).\n\nValidations while creating work items\n-------------------------------------\n\nThe following validations are done while importing or creating a work item in DevRev:\n\n* A maximum of 50 work items can be created at once. If more than 50 work items are listed in a CSV file, the system doesn\'t upload any work items.\n* The title field is mandatory. Rows with blank titles are skipped.\n* A work item isn\'t created if a part or
Bulk work item uploader | Automate | Snap-ins | DevRev
ART-2010_KNOWLEDGE_NODE-30
ID** drop-down menu.\n5. Click **Upload**, browse, and select the file. The CSV file is uploaded.\n6. Click **Submit**.\n\n   The **Bulk Uploader Bot** processes the CSV file and creates tickets or issues with the defined parameters. The newly created work items are listed displaying the work item number and title.\n\n[PreviousBulk delete data](/docs/automations/bulk-delete)[NextCommands surface expander](/docs/automations/commands-surface-expander)\n\n#### On this page\n\n* [Validations while
Bulk work item uploader | Automate | Snap-ins | DevRev
ART-4022_KNOWLEDGE_NODE-29
validations are done while updating or creating a work item in DevRev:\n\n1. Mandatory fields need to be filled in accordance with the sample CSV file.\n2. In single run of the snap-in, users can either perform create or update operation.\n3. Do not re-run the command until a timeline is initiated for re-execution, and click the submit button only once.\n\nUpload work items from CSV\n--------------------------\n\n1. Add the **CSV Work Item Uploader** snap-in from the DevRev Marketplace to your
CSV work item uploader | Automate | Snap-ins | DevRev
ART-16355_KNOWLEDGE_NODE-28
to be updated.\n\n![]()\n\nThe maximum row limit for the input CSV is 5,000.\n\nValidations for uploading CSV\n-----------------------------\n\nThe following validations are done while updating or creating a work item in DevRev:\n\n1. Mandatory fields must be filled in accordance with the sample CSV file.\n2. In a single run of the snap-in, users can perform either a create or an update operation, not both.\n3. Do not re-run the command until a timeline is initiated for re-execution, and click
CSV commands uploader | Automate | Snap-ins | DevRev
ART-2053_KNOWLEDGE_NODE-37
imported issue changes are synced to and from the Jira project.\n\nProject import\n--------------\n\nTo ease the transition from Jira to DevRev, you can import your Jira projects into DevRev. The project import is a 1-time bulk import of a Jira project into DevRev. Once this import is complete, several options are made available for that project, such as resyncing changes, syncing back to Jira, and bidirectional syncing.\n\n![]()\n\nFor best results, imports should be done using an
Jira Software AirSync | AirSync | Snap-ins | DevRev
ART-16355_KNOWLEDGE_NODE-29
the submit button only once.\n\nUpload commands from CSV\n------------------------\n\n1. Add the **CSV Work Commands Uploader** snap-in from the DevRev Marketplace to your environment.\n2. In the snap-in configuration, select the appropriate group you want to give access to run the snap-in.\n3. In the **Discussion** tab of the snap-in, enter /upload\\_commands.\n4. A snapkit with a drop-down appears in the **Discussion** tab of the snap-in. In the drop-down, select the type of work item you
CSV commands uploader | Automate | Snap-ins | DevRev
ART-4277_KNOWLEDGE_NODE-28
successfully.\n6. Once the connection is established, select the Google Drive you want to import and specify the DevRev part that should be used for any imported work (future releases make use of this). This initiates a bulk import of the selected drive.\n7. DevRev makes an effort to automatically map the fields from Google Drive to the corresponding fields in DevRev. However, you may be prompted to manually map certain fields if needed.\n\nThe duration of the import depends on the size of the
Google Drive | AirSync | Snap-ins | DevRev
ART-15716_KNOWLEDGE_NODE-4
supports importing data from platforms like Zendesk, Intercom, Freshdesk, Confluence, and more.\n\n[Airdrop supported sources](https://devrev.ai/docs/import#airdrop-features)\n\n8. Airdrop Integration Capabilities\n\nWith Airdrop, you can import tickets, articles, and other data from Zendesk, Intercom, Freshdesk, Confluence, and CSV files.\n\n[Airdrop integration options](https://devrev.ai/docs/import)Ticketing System\n\n1. Merging Tickets in DevRev You can merge tickets by opening the primary
Support queries related playbook
ART-2053_KNOWLEDGE_NODE-40
development work.\n  + Choose tickets if you use the Jira project to track only customer requests.\n  + There is also an option to import Jira epics as DevRev enhancements. This is useful if you use epics to track large features or projects.\n* What Jira types to import?\n  + Typically, Jira projects contain multiple types: epics, stories, bugs, and tasks are common.\n  + You can configure which types to import from Jira.\n* How to map Jira fields to DevRev fields?\n  + DevRev tries to
Jira Software AirSync | AirSync | Snap-ins | DevRev
ART-2992_KNOWLEDGE_NODE-24
[Snap-ins](/docs/snapins)\n[AirSync](/docs/import)\n[GitHub Issues AirSync](/docs/integrations/github-airdrop)\n\nGitHub Issues AirSync\n=====================\n\nTo ease the transition from GitHub issues to DevRev, you can import and sync GitHub issues with DevRev.\n\n### Supported objects\n\n| GitHub Object | DevRev Object | Sync to DevRev | Sync to GitHub |\n| --- | --- | --- | --- |\n| Issue | Issue | \xe2\x9c\x85 | \xe2\x9c\x85 |\n| Comment on Issue | Comment on Issue | \xe2\x9c\x85 |
GitHub Issues AirSync | AirSync | Snap-ins | DevRev
ART-4966_KNOWLEDGE_NODE-25
Objects marked as **Sync to DevRev** are eligible for import and sync.\n\nZoho Projects Object| DevRev Object| Sync to DevRev  \n---|---|---  \nUsers| DevUser| \xe2\x9c\x85  \nIssues / Bugs| Issues| \xe2\x9c\x85  \nTasks| Issues| \xe2\x9c\x85  \nIssues\xe2\x80\x99 Comments| Comments| \xe2\x9c\x85  \nTasks\xe2\x80\x99 Comments| Comments| \xe2\x9c\x85  \nAttachments| Attachments| \xe2\x9d\x8c  \n  \n## Import from Zoho Projects\n\nFollow the steps below to import from Zoho Projects:\n\n  1. Go to
Zoho Projects Airdrop | Airdrop | Snap-ins | DevRev
ART-4983_KNOWLEDGE_NODE-0
b'[](/public/airdrop)\n\nPublic\n\n#\n\nAirdrop\n\n _Airdrop_ is DevRev\xe2\x80\x99s solution for migrating data between DevRev and an external system. It allows our users to import their existing data from an external system, export any changes in DevRev back to the external system, and keep data in sync.\n\nDevRev provides a range of snap-ins available through the DevRev marketplace for integration with various external systems like Jira and Zendesk. These DevRev provided snap-ins are also
Airdrop — DevRev | Docs
ART-2010_KNOWLEDGE_NODE-29
**Select work items\' owners (max 1)** drop-down menu, select the work item\'s owner name.\n3. From the **Select a part to assign to work items** drop-down menu, select a part for the work items. If the bulk work item upload is done using a part, the part is automatically selected.\n4. In the **Customer ID** drop-down menu, select from the available workspaces associated with this account. If the bulk ticket upload is done using an account, the relevant workspaces are shown in the **Customer
Bulk work item uploader | Automate | Snap-ins | DevRev
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
ART-4022_KNOWLEDGE_NODE-24
CSV](#validations-for-uploading-csv)\n* [Upload work items from CSV](#upload-work-items-from-csv)\n* [Resetting the snap-in](#resetting-the-snapin)\n\n1. [Documentation](/docs)\n3. [Snap-ins](/docs/snapins)\n[Automate](/docs/automate)\n[CSV work item uploader](/docs/automations/csv-work-item-uploader)\n\nCSV work item uploader\n======================\n\nThe CSV Work Item Uploader is a snap-in designed to streamline the process of creating and updating work items in bulk through a CSV file. It
CSV work item uploader | Automate | Snap-ins | DevRev
ART-2010_KNOWLEDGE_NODE-26
is not specified or empty, the work item is created as a ticket.\n\n![]()\n\nIf the CSV lists multiple owners, only the first is set as the owner in the DevRev ticket. Update the owner value to the email. In the Subtype column, write the name of the subtype instead of the display name. Default work item created is a ticket if not specified.\n\nFor detailed information about DevRev tickets, refer to [Tickets](https://docs.devrev.ai/product/tickets).\n\nFor detailed information about DevRev
Bulk work item uploader | Automate | Snap-ins | DevRev
ART-3208_KNOWLEDGE_NODE-25
the target organization. Those marked as **Supported** are eligible for import.\n\n| DevRev Object | Sync to DevRev |\n| --- | --- |\n| Issue | \xe2\x9c\x85 |\n| Ticket | \xe2\x9c\x85 |\n| DevUser | \xe2\x9c\x85 |\n| Customer | \xe2\x9c\x85 |\n| Tag | \xe2\x9c\x85 |\n| Product | \xe2\x9c\x85 |\n| Capability | \xe2\x9c\x85 |\n| Enhancement | \xe2\x9c\x85 |\n| Feature | \xe2\x9c\x85 |\n| Runnable | \xe2\x9c\x85 |\n| Links on works | \xe2\x9c\x85 |\n| Timeline Comment | \xe2\x9c\x85 |\n| Account |
DevRev AirSync | AirSync | Snap-ins | DevRev
ART-15533_KNOWLEDGE_NODE-0
b'Airdrop | DevRev | Docs\n\nPublic\n\nPublic\n\nAirdrop\n=======\n\nCopy page\n\n*Airdrop* is DevRev\xe2\x80\x99s solution for migrating data between DevRev and an external system.\nIt allows our users to import their existing data from an external system,\nexport any changes in DevRev back to the external system, and keep data in sync.\n\nDevRev provides a range of snap-ins available through the DevRev marketplace for integration with\nvarious external systems like Jira and Zendesk.\nThese
Airdrop | DevRev | Docs
ART-4022_KNOWLEDGE_NODE-30
environment.\n2. In the snap-in configuration, select the appropriate group you want to give access to run the snap-in\n3. In the **Discussion** tab of the snap-in, enter /upload\\_workitems.\n4. A snapkit with two dropdowns appears in the discussion tab of the snap-in. In the first dropdown, select the type of operation you want to perform, and in the second dropdown, select the type of work item you want to perform the operation on.\n5. A sample CSV file is generated, with some mandatory
CSV work item uploader | Automate | Snap-ins | DevRev