The Jira Airdrop Snap-in enables you to keep track of your work no matter where it happens. You can migrate issues and users for an easier onboarding experience or sync Jira issues so you can leverage both systems.

## How it works

Jira Airdrop provides various options for importing and synchronizing issues and users from Jira. Whether you need to import one project or multiple, choose between one-way sync from Jira to DevRev or bi-directional to keep both systems in sync.

## Features

**Recipe mapping**

Recipe mapping ensures no critical Jira fields, even custom ones, are overlooked. You can select what to migrate and let our recommendations guide you on how to optimize the migration process for your Jira projects.

**Import**

The import feature allows for a one-time bulk migration of a Jira project. It utilizes recipe mapping, ensuring you bring over only what's essential and leave unnecessary data behind.

**Sync to DevRev**

Using the sync to DevRev functionality, you can re-synchronize a prior import to incorporate any new issues or modifications to previously imported items from a Jira project.

**Sync to Jira**

The sync to Jira functionality enables you to update modifications made in DevRev to Jira projects that were previously imported. Additionally, you can synchronize new work items created in DevRev to Jira.

## Installation

For detailed installation and configuration instructions, refer to the [Jira Airdrop documentation](https://docs.devrev.ai/integrations/jira).


jira.svg

DevRev Marketplace

Jira

Bidirectional sync to coexist delightfully with Jira, and transition to DevRev at your own pace.

## StageFlow Automator

The stageflow automator snap-in is a subset of the convergence snap-in that provides updates on custom stages of issues-tickets and enhancements-tickets.

## Features

* Stage-based notifications on tickets or issues.
* Subtype support.
* Custom stages support.

## How to use StageFlow automator snap-in

1. Create the mapping in the CSV file using the format shown below. Ensure the CSV file includes the following columns:
    * Issue <-> Ticket Mapping
        | Issue Subtype | Issue Stage | Ticket Stage | Ticket Subtype |
        | ------- | ----------- | ------------ | ------------ |
        |         | triage      | queued       |              |
        |         | Live        | Live         |              |
        | AI/ML   | in_development      | awaiting_development       |              |
        | AI/ML   | in_development      | awaiting_development       | Project      |
        | AI/ML   | Live      | UAT       | Project      |
    
    * Issue <-> Enhancement Mapping
        | Issue Subtype | Issue Stage | Enhancement Stage |
        | ------- | ----------- | ------------ | 
        |         | triage      | ideation       |        
        |         | Live        | general_availability |             
        | AI/ML   | prioritized | prioritized |
        | AI/ML   | wont_fix    | wont_do       |       

    
    * Ticket <-> Issue Mapping
        | Ticket Subtype | Ticket Stage | Issue Stage | Issue Subtype |
        | ------- | ----------- | ------------ | ------------ |
        |         | queued      | triage       |              |
        |         | Live        | Live         |              |
        | Project   | awaiting_development      | in_development       | AI/ML      |
        | Project   | UAT      | Live       | AI/ML      |
        | Project   | INQA      | in_testing       |      |

    * Ticket <-> Enhancement Mapping
        | Ticket Subtype | Ticket Stage | Enhancement Stage |
        | ------- | ----------- | ------------ |
        |         | ideation      | triage  |            
        |         | general_availability| Live | 
        | Project   | prioritized | prioritized |
        | Project   | canceled      | wont_fix |  



Refer to the default stages documentation for each product feature:
   - [Issue Stages](https://docs.devrev.ai/product/issues#stages)
   - [Ticket Stages](https://docs.devrev.ai/product/tickets#stages)
   - [Enhancement Stages](https://docs.devrev.ai/product/enhancements#stages)

2. In the snap-in **Discussion** tab, enter `/UploadCSV`.
3. Click **Upload** to select the CSV file you created in step 1. After the file is uploaded, the "File uploaded successfully" message is displayed.
4. Reload the page.
5. In the **Configuration** tab, you can see the mapping that was created in step 1, select the toggle button to enable the mapping.
6. Navigate to **Issues** or **Roadmap**, make the necessary updates, and the linked tickets will automatically reflect the changes configured in the CSV file, notifying the ticket owner.
7. You can also determine the appropriate stage for the ticket based on the message provided by a rev user or dev user.
8. In the snap-in **Discussion** tab, enter `/StageConfig`.
9. Select the values from the dropdown for the stage transition whenever a message is given by a rev user or dev user.
10. Click **Save** to save the configuration.

DevRev.svg

StageFlow Automator

A snapin which provides stage transition on tickets based on various events.

# DSAT Survey:

The DSAT Survey snap-in enables you to automatically post a DSAT (Developer Satisfaction) survey to dev-users at the end of every sprint or at fixed time intervals, collecting valuable feedback and insights to improve your development process.

## Features

### Automated survey posting

Your DSAT surveys are automatically posted at the end of every sprint or at fixed time intervals, ensuring that feedback is collected without manual intervention.

### Customizable survey questions

Tailor your survey questions to suit your team's needs in the snap-in configuration, ensuring the feedback collected is relevant and actionable.

### Integration with Developer360 Dashboard

The DSAT Survey results are seamlessly integrated into the Developer360 Dashboard, allowing you to view and analyze the feedback directly within your usual workflow.


DSAT Survey

Post a Developer Satisfaction(DSAT) survey to dev-users at the end of every sprint or at fixed time intervals.

# Ticket age in engineering

This snap-in adds a new attribute to tickets which automatically calculates the time spent on engineering for that ticket. The duration can be shown in hours or days.

## Features

- **Create ticket age in engineering custom fields**

  Upon snap-in installation, a custom field for **Ticket Age in Engineering** is created for the ticket object. Two additional hidden attributes are also automatically created for internal snap-in usage.

- **Automatically calculate ticket age in engineering**

  When a ticket moves into an engineering stage, the timer is started, when you move out of an engineering stage, the timer is stopped. This can be repeated through multiple sessions. Sessions are started when the ticket moves into an engineering stage from a non-engineering stage and they end when the ticket moves out of an engineering stage into a non-engineering stage.

- **Select ticket stages that reflect engineering work**

  You can select which ticket stages reflect that the ticket is in engineering.

- **Display ticket age in engineering in hours or days**

  Choose if the work duration should be shown in hours or days.

## Installation

For detailed installation and configuration instructions, refer to the [Ticket Age in Engineering documentation](https://docs.devrev.ai/automations/ticket-age-in-engineering).


Ticket Age in Engineering

Track total time spent on engineering for a ticket, based on the stage transitions of the ticket.

# Stage Breach Notifier

The stage breach notifier functionality notifies the owner and list of users when a stage of a work item is breached.

## **Features**

* **Stage-specific time-based triggers**:  It enables you to set up stage-specific time thresholds for each work item or ticket stage. This customization allows you to tailor the automation to the specific needs and priorities of different stages in your workflow.
* **Automated notification and communication**: When a work item exceeds the defined time period for a particular stage, automation automatically generates and sends updates to the internal discussion of the work item. This feature ensures that relevant team members are promptly informed of delays or potential issues, facilitating better communication and collaboration.

# How to use stage breach notifier

1. Take the data from the table below and create a CSV file. Make the required changes, such as adding custom stages, adjusting turnaround times for specific subtypes if required and deleting rows where turnaround times do not apply to stages. 
   * For example, if you want to add a custom stage called `uat` for the `Ticket` work item, you can add a row with `Ticket,uat,2` to the CSV file. Similarly, if you do not want to set a turnaround time for the `in_development` stage, you can remove the row with `Ticket,in_development,2` from the CSV file. 
   * If you want to set a different turnaround time for a specific subtype, you can add a row with `work_item,stage_name,turn_around_time,subtype_name` to the CSV file. For example, if you want to set a turnaround time of 3 days for the `work_in_progress` stage for the `Ticket` work item with the `Support` subtype, you can add a row with `Ticket,work_in_progress,3,Support` to the CSV file.
2. In the snap-in **Discussion** tab, enter the `/upload_stage_csv` command.
3. Click the **Upload** button to select the CSV file you created in step 1. After the file is uploaded, the "File uploaded successfully" message is displayed.
4. Reload the page to see the changes in the **Configuration** tab.
5. In the **Configuration** tab, select which users should be notified and click on the **Save** button to save the configuration.

## **CSV file format**
| work_item   | stage_name                 | turn_around_time (days) | subtype                 |
| ----------- | -------------------------- | ----------------------- | ----------------------- |
| Ticket      | queued                     | 2                       |                         |
| Ticket      | work_in_progress           | 2                       |                         |
| Ticket      | awaiting_product_assist    | 2                       |                         |
| Ticket      | awaiting_development       | 2                       |                         |
| Ticket      | in_development             | 2                       |                         |
| Ticket      | awaiting_customer_response | 2                       |                         |
| Issue       | triage                     | 2                       |                         |
| Issue       | backlog                    | 2                       |                         |
| Issue       | prioritized                | 2                       |                         |
| Issue       | in_development             | 2                       |                         |
| Issue       | in_review                  | 2                       |                         |
| Issue       | in_testing                 | 2                       |                         |
| Issue       | in_deployment              | 2                       |                         |
| Opportunity | qualification              | 2                       |                         |
| Opportunity | stalled                    | 2                       |                         |
| Opportunity | validation                 | 2                       |                         |
| Opportunity | negotiation                | 2                       |                         |
| Opportunity | contract                   | 2                       |                         |

Stage Breach Notifier

Timely notification of stage breaches for tickets, issues, and opportunities

# Link preview

The link preview snap-in generates previews of hyperlinks and links to the issues, tickets, and parts in real time, providing you with an overview of the linked content.

## Features

* **Automatic preview**: The link preview snap-in eliminates the hassle of manually navigating hyperlinks and referencing issues or tickets. You can view the overview of the link content without navigating to it.

* **Reference context**: The context-rich presentation simplifies discussion related to project management, support, and development by providing details such as title, description, status, owner(s), priority, stage, etc.

## Installation

For detailed installation and configuration instructions, refer to the [link preview documentation](https://devrev.ai/docs/automations/link-preview).


Link Preview

Generates previews of hyperlinks and links to issues, tickets, and parts in real-time, providing you with an overview of the linked content.

# Work duration for issues and tickets

This snap-in adds a new attribute to tickets and issues which automatically calculates the work duration for that item when it is closed (time elapsed from creation to closure). The duration can be shown in hours or days.

## Features

- **Create work duration custom fields**

  Upon snap-in installation, a custom field for **Work Duration** is created for ticket and issue objects. Two additional hidden attributes are also automatically created for internal snap-in usage.

- **Automatically calculate work duration**

  When an issue or ticket is created or reopened, the work duration timer is started. When the work item is closed the timer is stopped and the work duration attribute is automatically added, displaying the time elapsed. This can be repeated through multiple sessions. If the work item is reopened, the work duration attribute is removed and will be readded once the item is closed again.

- **Display work duration in hours or days**

  The snap-in can be configured to display the work duration in hours or days.

## Installation

For detailed installation and configuration instructions, refer to the [Work Duration documentation](https://docs.devrev.ai/automations/work-duration).


Work Duration

Automatically calculate work duration for tickets and issues.

This snap-in automatically manages security issues in DevRev by notifying owners and handling sprint assignments for high and critical severity security issues.

## Features

- Monitors security issue creation and ownership changes.
- Automatically notifies owners when high or critical severity issues are created or reassigned.
- Intelligently assigns security issues to appropriate sprint boards based on:
  1. Active sprints where the owner is a member.
  2. Most commonly used sprint board in recent issues.
- Posts timeline comments when sprint assignment isn't possible.

## Usage

No manual configuration is needed. The snap-in automatically:

1. Monitors security issues with `SECURITY_ISSUES` subtype.
2. Processes high and critical severity issues.
3. Notifies owners via timeline comments.
4. Attempts sprint assignment.
5. Posts additional guidance if sprint assignment fails.

## Error handling

The snap-in includes comprehensive error handling and logging:

- Failed API calls are logged with detailed error messages.
- Processing errors are caught and logged.
- Successful notifications and assignments are confirmed in logs.


OLA Breach Notifier for Security Issues

This snap-in auto-manages DevRev security issues by notifying owners and assigning high/critical issues to sprints.

The ClickUp Airdrop snap-in provides a seamless way to transfer your tasks from ClickUp to DevRev, either as tickets in [DevRev Support](https://devrev.ai/support) or issues in [DevRev Build](https://devrev.ai/build).

## Features

**Import**

The import feature enables a one-time bulk transfer of ClickUp tasks, users, tags, and task comments into DevRev.

**Sync to DevRev**

Using Sync to DevRev, you can re-synchronize an import to incorporate any new entries or updates to previously imported ClickUp records.

## **Installation**
Once you click on **Install**, navigate to the **Imports** page and start the **Import**. 
For detailed installation and configuration instructions, refer to the [ClickUp Airdrop documentation](https://docs.devrev.ai/integrations/clickup).


Clickup.svg

ClickUp

# Enhancement approval workflow

The enhancement approval workflow automates the approval process for system enhancements, ensuring that all necessary approvals are secured before an enhancement advances through its various stages.

## Key Features

- **Automated approvals**: Automatically triggers product and design approvals based on the enhancement stage.
- **Custom configurations**: Allows tailored configurations for product and design approval processes.
- **Snap-Kit actions**: Enables approvers to approve or reject enhancements directly through snap-kit actions.
- **Re-Trigger commands**: Provides commands to re-initiate approval processes as needed.
- **Rollback mechanism**: Rolls back enhancements that lack the necessary approvals.
- **Approval status tracking**: Creates custom fields to store and track approval statuses.

## Configuration

The workflow supports the following configurable inputs:

- **`product_approval_config`**: Approval config for product.
- **`design_approval_config`**: Approval config for design.
- **`product_approval_trigger_stage_name`**: Name of the stage that triggers product approval.
- **`design_approval_trigger_stage_name`**: Name of the stage that triggers design approval.
- **`disallowed_transition_stage_name`**: Name of the stage where transitions are blocked without proper approvals.

## Commands

- **`product_reapproval`**: Re-initiates the product approval process.
- **`design_reapproval`**: Re-initiates the design approval process.

## How to Use

1. **Configure inputs**: Set up the workflow inputs on the DevRev platform as per your requirements.
2. **Automated approvals**: The workflow will trigger approvals when enhancements reach the configured stages.
3. **Approval actions**: Approvers can use snap-kit actions to approve or reject enhancements.
4. **Re-Trigger approvals**: If necessary, use the re-trigger commands to restart the approval processes if it gets rejected.
5. **Rollback unapproved enhancements**: The system will automatically roll back enhancements that fail to obtain approvals.


Enhancement Approval Workflow

The Enhancement Approval Workflow snap-in automates the approval process for enhancements.


Using the slash commands you can access specific actions quickly and use DevRev's Turing AI to perform some useful functions, such as remind, rephrase, summarize, and clone.

## How it works

In the **Discussion** section, enter '/' in the text field to see a list of commands that apply to the source item.

## Usage

For usage instructions, refer to the [Slash commands documentation](https://devrev.ai/docs/automations/slash-commands).


Slash Commands

Slash commands in DevRev powered by Turing AI for more productivity.

The Trello Snap-in will enable seamless data import from task management and project tracking workflows into your application. By integrating this add-on, users will be able to sync boards, lists, cards, and activity logs directly into your platform for improved workflow visibility and team collaboration.

## Features

- **Automated Task & Board Data Import**

  Trello boards, lists, cards, and task details will be automatically imported into your application, ensuring real-time access to project updates.

- **Integration with Existing Project Management & Workflow Tools**

  Imported Trello data will be mapped to your platform’s task management, collaboration, or reporting systems, ensuring smooth synchronization with team workflows.

- **Customizable Task & Status Mapping**

  Users will be able to define how Trello’s lists, labels, due dates, and checklists correspond to fields in your application, ensuring structured task tracking.

- **Real-Time Syncing for Task & Status Updates**

  Any changes to boards, cards, or task assignments in Trello will be reflected in your platform, ensuring teams stay aligned and informed.


trello.svg

Trello

Enhance task management with deeper customer and development context.

The Wrike Snap-in will enable seamless data import from project management and team collaboration workflows into your application. By integrating this add-on, users will be able to sync tasks, project timelines, resource allocation, and collaboration data directly into your platform for improved project tracking and team coordination.

## Features

- **Automated Task & Project Data Import**

  Tasks, projects, timelines, and resource allocation from Wrike will be automatically imported into your application, ensuring that project details are always up to date.

- **Integration with Existing Project Management & Collaboration Tools**

  Imported project data will be mapped to your platform’s project management, collaboration, or resource planning systems, ensuring smooth synchronization with ongoing workflows.

- **Customizable Task & Status Mapping**

  Users will be able to define how Wrike’s task fields, statuses, and timelines correspond to fields in your application, ensuring structured project management and reporting.

- **Real-Time Syncing for Task & Project Updates**

  Any changes to tasks, project statuses, or timelines in Wrike will be reflected in your platform, keeping teams aligned with the latest project information.


wrike.svg

Wrike

Improve collaboration between product, support, and engineering teams.

The Productboard Snap-in will enable seamless data import from product management and feedback workflows into your application. By integrating this add-on, users will be able to sync product insights, feature requests, roadmap updates, and customer feedback directly into your platform for improved product planning and prioritization.

## Features

- **Automated Product Data Import**

  Feature ideas, customer feedback, and roadmap updates from Productboard will be automatically imported into your application, ensuring that product teams have access to the latest insights.

- **Integration with Existing Product Management & Development Tools**

  Imported data will be mapped to your platform’s product management, development, or customer feedback systems, ensuring smooth synchronization with ongoing planning and execution.

- **Customizable Feedback & Roadmap Mapping**

  Users will be able to define how Productboard’s feature requests, prioritization scores, and customer inputs correspond to fields in your application, enabling structured decision-making.

- **Real-Time Syncing for Product Updates**

  Any new feedback, priority changes, or roadmap adjustments in Productboard will be reflected in your platform, ensuring alignment between product teams and stakeholders.


productboard.svg

ProductBoard

Ensure customer-driven product development with streamlined feedback management.

The Asana Snap-in will enable seamless data import from project and task management workflows into your application. By integrating this add-on, users will be able to sync tasks, projects, and team collaboration data directly into your platform for better workflow management.

## Features

- **Automated Task & Project Import**

  Tasks, projects, and milestones will be automatically imported into your application, ensuring teams stay aligned with their work.

- **Integration with Existing Workflow Systems**

  Imported data will be structured to fit within your platform’s workflow, allowing for seamless tracking and management.

- **Customizable Field Mapping**

  Users will be able to define how Asana’s data fields correspond to fields in your application, ensuring flexible and accurate data transfer.

- **Real-Time Updates & Syncing**

  Any changes made in Asana will be reflected in your platform, keeping project information up to date across tools.

- **Access Control & Security Compliance**

  Role-based access control will ensure that imported data is only accessible to authorized users.


asana.svg

Asana

Align cross-functional teams with seamless task and project tracking.

The Smartsheet Snap-in will enable seamless data import from project management and workflow automation processes into your application. By integrating this add-on, users will be able to sync spreadsheets, tasks, project timelines, and collaboration data directly into your platform for improved planning and execution.

## Features

- **Automated Spreadsheet & Project Data Import**

  Task lists, project timelines, resource allocations, and collaboration updates from Smartsheet will be automatically imported into your application, ensuring real-time project visibility.

- **Integration with Existing Project Management & Business Tools**

  Imported data will be mapped to your platform’s task management, workflow automation, or reporting systems, enabling seamless synchronization with ongoing projects.

- **Customizable Field Mapping & Workflow Automation**

  Users will be able to define how Smartsheet’s rows, columns, task statuses, and dependencies align with fields in your application, ensuring structured project tracking.

- **Real-Time Syncing for Task & Status Updates**

  Any changes to sheets, project schedules, or task assignments in Smartsheet will be reflected in your platform, keeping teams aligned with the latest updates.


smartsheet.svg

Smartsheet

Optimize project execution with agile tracking and collaboration.

The Aha! Software Snap-in will enable seamless data import from product management workflows into your application. By integrating this add-on, users will be able to transfer roadmaps, ideas, and feature plans directly into your platform for enhanced collaboration and decision-making.

## Features

- **Automated Product Data Import**

  Roadmaps, feature plans, and strategic objectives will be automatically imported into your application, ensuring alignment with product development processes.

- **Integration with Existing Project Management Tools**

  Imported data will be mapped to your platform’s structure, allowing for synchronization with project management workflows.

- **Customizable Field Mapping**

  Users will have the flexibility to define how Aha! data fields correspond to relevant fields in your application, ensuring a smooth data transfer.

- **Real-Time Updates & Syncing**

  Changes made in Aha! will be reflected in your platform, keeping all stakeholders up to date with the latest product strategy.

- **Data Security & Access Control**

  Imported data will be handled securely, with role-based access controls ensuring that only authorized users can view or modify information.


aha.svg

Aha!

Connect product roadmaps with real-time customer insights for smarter decision-making.


Supercharge cross-functional work with this set of default automations, propagating information across various entities at DevRev–including conversations, tickets, product enhancements, and development issues.

DevRev's shared system of record opens up doors for the machine to take over and intelligently ensure that heartbeats from various functions of your DevRev workspace travel across each other.

DevRev's system of record converges multiple functions in an organization–touching everything from customer conversations to support tickets to planned product enhancements and then developer issues. Because the system of record is shared, it paves the way for the machine to take on menial, repetitive work, especially around bringing together (or converging) these cross-functional entities (and thus the teams that work on them).

_Convergence with DevRev_ is a set of default automations that powers cross-functional information snap-in in your DevRev workspace, such that updates from product teams' issues and enhancements make their way to tickets in the customer-facing functions and vice versa with little human intervention. Let machines be the messenger of updates so they arrive before the next "Any progress on this?".

## Features

This automation is powerful and has a series of individual, configurable behaviors.

The power is in the defaults! With this pre-enabled snap-in come DevRev's proven defaults. You always have the option to adjust further.

**Automatic customer updates from tickets**

Propagate updates from tickets to related customer conversations so your customer is never in the dark.

- When a ticket is linked to a conversation, autonomously update the conversation and provide a follow-up reference to the customer.
- When a ticket is updated with relevant information, post a notification to the conversation.
- When a ticket is closed, post an autonomous update to any related PLuG conversations.

**Automatic updates between tickets to issues**

Leveraging the association between customer tickets and your product team's issues, this automation focuses on keeping issues aware of changes to tickets and vice-versa so the dev team is kept in the loop.

- When the severity of a ticket changes, autonomously update the issue priority and stage accordingly.
- When progress is made on an issue, update the status on dependent tickets.
- When underlying issues are resolved, advance tickets to the next stage.

**Autonomous issue management**

Parent issues, child issues, dependent issues, and blocked issues are every dev's nightmare. With this set of autonomous convergence behaviors, issues, and their hierarchy become manageable.

- Watch children issues and automatically update a parent issue when a dev starts working on it.
- As children issues make progress, send state updates to parent issues along with information on progress towards completion.
- When parent issues are closed, update child issues automatically.

**Automatic updates between Issues and Enhancements**

Synergizing Parts and work has been made easier by ensuring through automated reminders and suggested actions that your product enhancements and the work items or issues linked to them are always in sync.

- Remind the owners by automatically posting a comment to create and link issues to an enhancement that is ‘In Progress’ state without any linked issue.
- Remind the owners by automatically posting a comment to create and link issues to an enhancement that has been in the ‘Prioritised’ stage for a while.
- Remind the owners through an automatically suggested action to move an open enhancement to ‘In Progress’ when any issue linked to it is moved to the ‘In Progress’.
- Remind the owners by automatically posting a comment to move listed issues out of the triage stage for an enhancement.

**Automatic update between Tickets and Enhancement**

When your customer tickets are linked to an ongoing product enhancement, it is best to provide absolute clarity to the support team on what's happening on the product front through an automatic update system. 

- Automatically subscribe ticket owners to the enhancement that is attached to the ticket so that they stay informed.
- Automatically post comments on tickets whenever the stage is updated in the attached enhancement.

**Automatic resolution and archival of conversations**

When your authenticated customers do not respond to a conversation within a specific period of time set as the resolution timeout, the conversation is automatically marked as resolved. Even though the conversation is resolved, the customer still has the option to reopen it if necessary. However, if the customer does not reply within another specified period of time set as the archival timeout, the conversation is automatically archived and cannot be reopened. The customer can always initiate a new conversation for any follow-up needs.

Please note that these configuration settings only apply to authenticated users. For conversations with guests or visitors, if the customer doesn't respond within 3 days while the conversation is in the _Waiting on user_ stage, it is automatically resolved. After 7 days, it is archived automatically.

## Installation

For detailed installation and configuration instructions, refer to the [Convergence documentation](https://docs.devrev.ai/automations/converge).


Convergence

Real-time updates between customer conversations, support tickets, Product enhancements and developer issues.

# Bitbucket for DevRev

Connect Bitbucket with DevRev to sync your work and get real-time issue and status updates based on code activity.

The Bitbucket snap-in removes the need for manual issue management by connecting DevRev issues with Git actions. By automating issue handling, developers can focus on meaningful work rather than administrative tasks. This approach resonates with those who've encountered issues like delivering patches without proper tracking, spending time updating issue statuses, or finding issue management distracting.

You can link your Bitbucket commits, branches, and pull requests with existing DevRev issues without creating issues automatically in DevRev. The issues' statuses are guided by Bitbucket activity, transitioning from _In Development_ to _In Review_ and _Closed_ stages. This ensures comprehensive work tracking and enhances team visibility, minimizing disruptions.

However, if you choose to work in Bitbucket and never create or link an issue, you shouldn’t have to sweat it. This snap-in can automatically create issues that track all associated commits, branches, and pull requests. The auto-created issue is auto-populated with the PR description and related Bitbucket events. The status of these issues is driven by Bitbucket activity, and the issues will auto-transition stages, from _In Development_ to _In Review_, and _Closed_. Your work is always accounted for and more importantly, your team members have visibility and know what you’ve been up to, resulting in fewer interruptions.

## Features

**Automatic status updates**

Associate your Bitbucket commits, branches, and pull requests with the corresponding DevRev issues and tickets to integrate with the relevant DevRev issue or ticket. This integration enables you to take action on Bitbucket events within the DevRev issue/ticket, automating manual tasks. Mention DevRev issues or tickets in Bitbucket using either display IDs (for example, ISS-34) or object IDs (for example, ticket:34), with case insensitivity. You can include a DevRev issue/ticket reference in branch names, commit messages, or PR titles. You can define which stage an issue is updated to in the configuration screen for each Bitbucket event like new commit, new pull request open, new branch creation, and PR close. 

**Autocreate issues from Bitbucket branch**

If you do not explicitly associate your DevRev issue to Bitbucket branches, commits, or PRs, then we can auto-create your issues so you have an account of all your Bitbucket activity. This feature automatically creates an issue when a new branch is created, and tracks all associated commits and pull requests on this issue. The auto-created issues will move status based on Bitbucket activity, to _In Development_ based on branch and commit activity, and _In Review_ when PRs are created. When PRs are merged, the issue will be automatically closed, though this behavior is configurable.

**Autocreate issues from Bitbucket PRs**

You can choose to automatically create issues when a new PR is created, and it is not linked to an existing DevRev Issue. The behavior is similar to how issues are auto-created with new branches. The auto-created issues will move status based on Bitbucket activity, and events are posted on the DevRev issue timeline.

Issues auto-created from Bitbucket branches or PRs are called autonomous issues, and have the tag `autonomous`.

**Attribute part to 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.

**Auto-populate autonomous work descriptions**

When a new Bitbucket PR is opened or edited, then the related autonomous issue description is updated with the latest PR description. If the user has removed the auto-generated text, then the automation will no longer update the description from PRs. Similarly, autonomous work titles are updated with the PR title, if the user hasn’t already updated it.

**Link autonomous work with related issue**

Create a related link between the work items mentioned in the PR body and the autonomous issues tagged with the branch/PR. When a new Bitbucket PR is opened/edited, for all the autonomous tagged work items(by branch/PR), automatically mark the issues mentioned in the PR as related.

**Automatically close autonomous work**

Autonomous work gets closed when its related PR is merged. However, if there is no PR activity on this work, then the autonomous work is closed after a configurable period.

**Bitbucket Commands**

Enable quick actions to close or attribute a PR to a DevRev issue with the slash command.

- `/towards`: Use the `/towards` command in the PR description to associate the related Bitbucket activity to the issue. This will ensure that the PR and issue are linked such that related events are posted and issue status is driven by Bitbucket events.
- `/close {work-id}`: Use `/close ISS-3 ISS-4` in a PR body to automatically close a specific issue when the PR is merged. You can also use `/close #work` to close all associated issues with a PR when that PR is merged without knowing the specific IDs.

**Automatic PR tasks**

When a pull request is requested or reopened, a DevRev task is created for you. For this automation to be triggered, you'll need to link your pull requests to DevRev issues. If your PR is removed, merged, or closed, then the Task gets deleted. However, if you submit your PR review, then the task is closed.

**Automatic PR reminders**

When a pull request is inactive for more than a specified number of days, then this automation will post a message in all related DevRev issues. You'll need to link your Bitbucket pull request to the DevRev issue to enable these reminders. There are several ways to link your Bitbucket pull requests to DevRev Issues. You can do so by mentioning the DevRev issue ID in the pull requests title or body, or mentioning it in the branch name or commit message. Reminders are also posted for issues created autonomously.

You can choose to set up the inactive period in the number of days through the setting to specify the number of days before sending PR reminders.

## Installation

For detailed installation and configuration instructions, refer to the [Bitbucket snap-in](https://docs.devrev.ai/integrations/bitbucket#installation) documentation.


Bitbucket.svg

Bitbucket

Sync Bitbucket and DevRev so issue status is always real time and driven by code.

# GitHub for DevRev
Sync GitHub and DevRev so issue status is always real-time and driven by code.
## **Overview**

<img src="https://raw.githubusercontent.com/shashankcube/image/main/github-automation.png" align="center"/> 
 
Connect GitHub with DevRev, and ensure your work stays in sync between the two systems, such that issues and statuses are always real-time and driven by code activity. GitHub for DevRev is a snap-in that has been used by several organizations and ties DevRev issues closely with GitHub activity, eliminating the need for humans to manage issues.

Why should you un-manage your work? You should use this snap-in if you want to reduce work about work. Let machines manage issues, including creating and updating statuses, so developers can focus on work that matters. You’ll resonate with this if you have ever:

- Delivered a hot-patch and realized you never had an issue to track it
- Wasted time just updating your team on the status of an issue
- Or just felt that creating and managing issues is a distraction

If your team’s best practice is to link your GitHub activity to an existing issue ID during branch creation, commits, and PRs, then this snap-in will honor that and enable a GitHub-driven issue state, without auto-creating issues. [Here](https://devrev.ai/docs/integrations/github#github-events) are the different ways you can link your DevRev issue to GitHub branches, commits and PRs. 

However, if you choose to work in GitHub and never created or linked an issue, you shouldn’t have to sweat it. This snap-in will automatically create issues that track all associated commits, branches, and pull requests. The auto-created issue is enriched with PR description and related GitHub events. The status of these issues is driven by GitHub activity, and the issues will auto-transition stages, from In Development to In Review, and Closed. Your work is always accounted for and more importantly, your team members have visibility and know what you’ve been up to, resulting in fewer interruptions. 

## **How it works**

To enable GitHub for DevRev, click on **Install** and we'll walk you through a few simple steps including connecting with GitHub. You'll have a default set of configuration settings and the option to further personalize this snap-in. Learn more about the features in this snap-in.

## **Features** 
This snap-in is powerful and has several configurable features. As they say, the power is in the defaults! When you install this snap-in, we'll configure defaults that are tried and tested. You always have the option to personalize further.

**Automatic status updates**

You can associate GitHub commits, branches, and pull requests with the DevRev issue they correspond to. Doing so allows you to see GitHub activity in the corresponding DevRev issue and to act on those events, allowing you to automate away your manual tasks. Mention DevRev issues in GitHub, and route the relevant GitHub events to this issue. They can be mentioned either as display IDs (ISS-34) or object IDs (issue:34), case-insensitively. A DevRev issue can be mentioned in branch names, commit messages, or PR titles.

**Autocreate issues from GitHub branch / PRs**

To make use of this feature, go to **My settings** on the **Configuration** screen of the snap-in and toggle **Enable for me**. This setting is not applied across the entire organization, each user must enable it.
You can enable the **Create DevRev issue when a new branch is created** or **Create DevRev issue when a new PR is opened**, depending on your preferences. It would be ideal if you enabled one of them rather than both.

**Autocreate issues from GitHub branch**

If you do not explicitly associate your DevRev issue to GitHub branches, commits, or PRs, then we can auto-create your issues so you have an account of all your GitHub activity. This feature automatically creates an issue when a new branch is created, and tracks all associated commits and pull requests on this issue. The auto-created issues will move status based on Git activity, to in development based on branch and commit activity, and in review when PRs are created. When PRs are merged, the issue will be automatically closed, though this behavior is configurable.

**Autocreate issues from GitHub PRs**

You can choose to automatically create issues when a new PR is created, and it is not linked to an existing DevRev Issue. The behavior is similar to how issues are auto-created with new branches. The auto-created issues will move status based on Git activity, and events are posted on the DevRev issue timeline.

Issues auto-created from GitHub branches or PRs are called autonomous issues, and have the tag `autonomous`.

**Attribute part to autonomous work**

Autonomous issues originating from GitHub 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.

**Enrich autonomous work descriptions**

Enrich autonomous issues with information derived from GitHub PR events. The title and description of an auto-created issue are enriched with the PR data. When a new GitHub PR is opened or edited, then the related autonomous issue description is updated with the latest PR description. If the user has removed the auto-generated text, then the automation will no longer update the description from PRs. Similarly, autonomous work titles are updated with the PR title, if the user hasn’t already updated it.

**Link autonomous work with related issue**

Create a related link between the work items mentioned in the PR body and the autonomous issues tagged with the branch/PR. When a new GitHub PR is opened/edited, for all the autonomous tagged work items(by branch/PR), automatically mark the issues mentioned in the PR as related.

**Automatically close autonomous work**

Autonomous work gets closed when its related PR is merged. However, if there is no PR activity on this work, then the autonomous work is closed after a configurable period.

**GitHub Commands**

Enable quick actions to close or attribute a PR to DevRev issue(s) with the slash command.

* `/towards` - Use the `/towards`  command in the PR description to associate the related GitHub activity to the issue(s). This will ensure that the PR and issue are linked such that related events are posted and issue status is driven by GitHub events.

* `/close {work-id}` - Use `/close ISS-3 ISS-4` in a PR body to automatically close a specific issue(s) when the PR is merged. You can also use `/close #work` to close all associated issues with a PR when that PR is merged without knowing the specific IDs.

**Automatic PR tasks**

When a pull request is requested or reopened, a DevRev task is created for you. For this automation to be triggered, you'll need to link your Pull Requests to DevRev issues. If your PR is removed, merged, or closed, then the Task gets deleted. However, if you submit your PR review, then the task is closed.

**Automatic PR reminders**

When a pull request is inactive for more than a specified number of days, then this automation will post a message in all related DevRev issues. You'll need to link your GitHub Pull Request to the DevRev issue to enable these reminders. There are several ways to link your GitHub Pull Requests to DevRev Issues. You can do so by mentioning the DevRev issue ID in the pull requests title or body, or mentioning it in the branch name or commit message. Reminders are also posted for issues created autonomously.

You can choose to set up the inactive period in the number of days through the max_inactive_days setting.

**Automatic programming language skill identification for dev users**

When a pull request is merged, the automation identifies the programming languages used in the PR and adds them as skills to the Dev user who submitted the request. To enable this feature, reach out to the DevRev customer experience team.

**Installation**

For detailed installation and configuration instructions, refer to the [Github documentation](https://docs.devrev.ai/integrations/github).


github.svg

GitHub

Your issues on Autopilot. Sync GitHub and DevRev so issue and status is always real time and driven by code.

# Harness

The Harness integration snap-in streamlines the development and deployment process by facilitating communication between DevRev, GitHub, and the Harness platform. 

It automatically updates the issues' status based on the progress of CI/CD pipelines, removing the need for manual interventions. This snap-in also offers visibility into deployment pipeline stages directly within related issues.

To enable, click on **Install** and follow the steps, including connecting with Harness. Default configurations are available with further personalization options. Learn more about the features in this snap-in.

## Features

### Automatic status updates

- Automatically update DevRev issue status based on Harness pipeline events.
- Mention DevRev issues in GitHub to route relevant Harness events.

### Decide which events to capture

- Configure the snap-in to capture specific pipeline events.
- Select from **start**, **success**, and **failed** events.

### Configurable mapping

- Map DevRev stage updates to specific Harness events.

### Get notified for each stage

- Timeline comments for each stage in the pipeline process.

## Benefits

- Reduced context switching and real-time updates.
- Automated notifications for key deployment events.
- Reduced errors through automated workflows and visibility.

## Installation

For detailed installation and configuration instructions, refer to the [Harness snap-in documentation](https://docs.devrev.ai//integrations/harness).


harness.svg

Harness

Automate GitHub, and Harness communication, updating issue statuses and providing visibility.

# Qase integration

## Overview
The Qase integration is designed to seamlessly connect Qase test case management with DevRev Build, facilitating collaboration between product development and QA teams. This integration aims to improve visibility, communication, and workflow efficiency by linking test cases and runs to DevRev issues and enhancements.

## How it works
The integration enables users to map test cases and test runs to specific DevRev issues and enhancements, create issues with tags from Qase defects, view test case details, and run statistics directly within DevRev. It leverages authentication mechanisms like OAuth, Tokens, or API Keys for secure connections.

## Features
- **Mapping functionality:** Easily link test cases and runs to DevRev issues and enhancements by embedding DevRev IDs in the Qase test case and running titles or descriptions.
- **Issue creation:** Create DevRev issues with specific tags from defects found in Qase, ensuring seamless bug tracking and resolution.
- **View test case details:** Access comprehensive information about linked test cases in DevRev, including ID, title, severity, owner, status, last run, and more.

## Summary
The Qase integration streamlines collaboration between development and QA teams by bridging Qase's test case management with DevRev's issue tracking and enhancement management. It enhances visibility, facilitates bug tracking, and improves overall workflow efficiency for teams using these platforms in tandem.


qase.svg

Qase

Connect Qase test management with DevRev for streamlined QA workflows.

Connect Azure Repos with DevRev, and ensure your work stays in sync between the two systems, such that issues and statuses are always real-time and driven by code activity. Azure Repos for DevRev is a snap-in that has been used by several organizations, and ties DevRev issues closely with Git activities, eliminating the need for humans to manage issues.

Why should you un-manage your work? You should use this snap-in if you want to reduce work about work. Let machines manage issues, including creating and updating statuses, so developers can focus on work that matters. You'll resonate with this if you have ever:

- Delivered a hotfix and realized you never had an issue to track it
- Wasted time just updating your team on the status of an issue
- Or just felt that creating and managing issues is a distraction

If your team's best practice is to link your Azure Repos activity to an existing issue-ID during branch creation, commits, and PRs, then this automation will honor that and enable an Azure Repos-driven issue state, without auto-creating issues. We can link your DevRev issue to Azure Repos activity through mention of issue-ID in branches, commits, and PRs.

However, if you choose to work in Azure Repos and never created or linked an issue, you shouldn't have to worry. This automation will automatically create issues that track all associated commits, branches, and pull requests. The auto-created issue is enriched with PR descriptions and related Azure Repos events. The status of these issues is driven by Azure Repos activity, and the issues will auto-transition through stages, from _In Development_ to _In Review_ and _Closed_. Your work is always accounted for, and more importantly, your team members have visibility and know what you have been up to, resulting in fewer interruptions.

## How it works

To enable Azure Repos for DevRev, click on **Install** and we will walk you through a few simple steps, including connecting with Azure Repos. You will have a default set of configuration settings and the option to further personalize this automation. Learn more about the features in this automation.

## Features

This automation is powerful and has several configurable features. Upon installing this snap-in, you'll receive tried-and-tested default settings, with the flexibility to customize further as needed.

### Automatic status updates

You can associate Azure Repos commits, branches, and pull requests with the DevRev issue they correspond to. Doing so allows you to see Azure Repos activity in the corresponding DevRev issue and to act on those events, allowing you to automate away your manual tasks. Mention DevRev issues in Azure Repos, and route the relevant Azure Repos events to this issue. They can be mentioned either as display IDs (`ISS-34`) or object IDs (`issue:34`), case insensitively. A DevRev issue can be mentioned in branch names, commit messages, or PR titles.

### Autocreate issues from Azure Repos branch

If you do not explicitly associate your DevRev issue to Azure Repos branches, commits, or PRs, then we can auto create your issues so you have an account of all your Azure Repos activity. This feature automatically creates an issue when a new branch is created and tracks all associated commits and pull requests on this issue. The auto-created issues will move status based on Git activity, transitioning to _In Development_ based on branch and commit activity, and _In Review_ when PRs are created and merged. If desired, when PRs are merged, you can personalize the automation to move the issue to _Closed_ status. However, this template by default will keep the issue in an open state.

### Autocreate issues from Azure Repos PRs

You can choose to automatically create issues when a new PR is created, and it is not linked to an existing DevRev Issue. The behavior is similar to how issues are auto-created with new branches. The auto-created issues will move status based on Git activity, and events are posted on the DevRev issue timeline. If desired, when PRs are merged, you can personalize the automation to move the issue to _Closed_ status. However, this automation by default will keep the issue in an open state.

Issues autocreated from Azure Repos branches or PRs are called autonomous issues. They have the tag `autonomous`.

### Attribute part to autonomous work

This automation will infer the part from a repository if possible. If not, the issue is created with a specified default part. You can configure the default part while setting up this snap-in. Every issue on DevRev must have a part attribution.

### Enrich autonomous work descriptions

Enrich autonomous issues with information derived from Azure Repos PR events. The title and description of an auto-created issue are enriched with the PR data. When a new Azure Repos PR is opened or edited, then the related autonomous issue description is updated with the latest PR description. If the user has removed the auto-generated text, then the automation will no longer update the description from PRs. Similarly, autonomous work titles are updated with the PR title if the user has not already updated it.

### Link autonomous work with related issue

Create a parent-child link between the work-items mentioned in the PR body and the autonomous issues tagged with the branch/PR. When a new Azure Repos PR is opened/edited, for all the autonomous tagged work items (by branch/PR), automatically make the issues mentioned in the PR as parents.

### Automatically close autonomous work

Autonomous work gets closed when its related PR is merged. However, if there is no PR activity on this work, then the autonomous work is closed after a configurable period.

### Automatic PR reminders

When a pull request is inactive for more than a specified number of days, then this automation will post a message in all related DevRev issues. You'll need to link your Azure Repos pull request to a DevRev issue to enable these reminders. There are several ways to link your Azure Repos pull requests to DevRev Issues. You can do so by mentioning the DevRev issue ID in pull request titles or bodies, or mention it in the branch name or commit message. Reminders are also posted for issues created autonomously.

You can choose to set up the inactive period in number of days through the `max_inactive_days` setting.


azure-repos-icon.png

Azure Repos (Beta)

Sync Azure Repos and DevRev so issue status is always real-time and driven by code.

This snap-in allows for the seamless migration of Linear issues to DevRev. Once integrated, the Linear Snap-in ensures continuous synchronization by receiving real-time updates from Linear and automatically syncing them with DevRev. It maps issue fields to DevRev attributes for efficient tracking and utilizes DevRev’s collaboration tools to streamline issue management.

## Features

- **Import**

  The basic import allows you to perform a 1-time import of Linear issues and users from a team.

- **Sync to DevRev**

  With sync to DevRev, you can resync a previous import to pull in any new issues or changes to previously imported issues from a Linear team.

- **Sync to Linear**

  The sync to Linear feature enables changes made in DevRev to be reflected back in Linear, ensuring complete synchronization between both platforms and allowing teams to work in their preferred environment.

## Installation

To use Linear Import, go to **Settings &gt; Imports** and select **Start Import** or **Import**. For details, see the [Linear Import docs](https://devrev.ai/docs/integrations/linear).

Linear.svg

Linear

Sync Linear issues for a seamless DevRev onboarding experience.

The Jira Service Management Airdrop Snap-in enables you to import your service desks from Jira Service Management into DevRev. You can migrate issues, users, customers, and more for an easier onboarding experience. Import one project or multiple from Jira Service Management to DevRev.

## Features

- **Recipe mapping**

  Recipe mapping ensures no critical Jira Service Management fields, even custom ones, are overlooked. You can select what to migrate and let our recommendations guide you on how to optimize the migration process for your Jira Service Management projects.

- **Import**

  The import feature allows for a one-time bulk migration of a Jira Service Management project. It utilizes recipe mapping, ensuring you bring over only what's essential and leave unnecessary data behind.

- **Sync to DevRev**

  Using the sync to DevRev functionality, you can re-synchronize a prior import to incorporate any new issues or modifications to previously imported items from a Jira Service Management project.

## Installation

For detailed installation and configuration instructions, refer to the [Jira Service Management Airdrop documentation](https://docs.devrev.ai/integrations/jsm).

jsm_logo.webp

Jira Service Management

Import your Jira Service Management issues as DevRev tickets.

The Microsoft Dynamics 365 Snap-in will enable seamless data import from customer relationship management (CRM) and enterprise resource planning (ERP) workflows into your application. By integrating this add-on, users will be able to sync customer data, sales opportunities, financial records, and service management data directly into your platform for improved business operations and decision-making.

## Features

- **Automated CRM & ERP Data Import**

  Customer records, sales opportunities, and financial data from Microsoft Dynamics 365 will be automatically imported into your application, ensuring real-time updates and accurate business insights.

- **Integration with Existing Business Systems**

  Imported data will be mapped to your platform’s CRM, ERP, or other business management tools, ensuring smooth synchronization with existing records and workflows.

- **Customizable Data Mapping & Field Synchronization**

  Users will be able to define how Microsoft Dynamics 365 data fields correspond to fields in your application, ensuring compatibility and flexibility in the integration.

- **Real-Time Syncing for Sales, Service, and Finance**

  Any updates to customer records, sales opportunities, or financial transactions in Dynamics 365 will be reflected in your platform, keeping all systems aligned and up to date.


microsoft-dynamics-365.svg

Microsoft Dynamics 365

Align sales, support, and product teams with a shared customer view.

The Microsoft Outlook Snap-in will enable seamless data import from email workflows into your application. By integrating this add-on, users will be able to sync emails, attachments, and metadata directly into your platform for enhanced communication management and productivity.

## Features

- **Automated Email Import**

  Emails, including content, attachments, and metadata, will be automatically imported into your application, enabling users to access and manage their email communications directly within your platform.

- **Integration with Existing Communication Systems**

  Imported email data will be mapped to your platform’s messaging or CRM systems, ensuring smooth synchronization with ongoing communication workflows.

- **Customizable Email Data Mapping**

  Users will be able to define how Outlook email fields, such as sender, subject, and timestamps, correspond to fields in your application, ensuring flexible email management and processing.

- **Real-Time Email Syncing**

  Any new emails or updates to existing threads in Outlook will be reflected in your platform, ensuring up-to-date access to the latest messages and communication.


microsoft-outlook.svg

Microsoft Outlook

Track customer emails and streamline collaboration across teams.

The Pipedrive Snap-in will enable seamless data import from sales and customer relationship management (CRM) workflows into your application. By integrating this add-on, users will be able to sync deals, contacts, activities, and pipeline data directly into your platform for improved sales tracking and customer management.

## Features

- **Automated CRM Data Import**

  Deals, contacts, organizations, and activity logs from Pipedrive will be automatically imported into your application, ensuring that sales teams always have up-to-date information.

- **Integration with Existing Sales & CRM Systems**

  Imported data will be mapped to your platform’s CRM or sales management tools, enabling smooth synchronization with lead tracking and pipeline workflows.

- **Customizable Field Mapping & Data Organization**

  Users will be able to define how Pipedrive’s data fields, such as deal stages, contact details, and activity types, correspond to fields in your application for a tailored sales process.

- **Real-Time Syncing for Sales Pipeline Updates**

  Any changes to deals, contacts, or activities in Pipedrive will be reflected in your platform, ensuring accurate sales reporting and pipeline forecasting.


pipedrive.svg

Pipedrive

Empower sales and support teams with real-time customer insights and lifecycle tracking.

The Zoom Transcript Snap-in will enable seamless data import from Zoom meetings and webinars into your application. By integrating this add-on, users will be able to sync meeting transcripts, participant details, and audio-to-text data directly into your platform for improved meeting management and collaboration.

## Features

- **Automated Meeting Transcript Import**

  Meeting transcripts, including audio-to-text conversion, timestamps, and speaker identification from Zoom will be automatically imported into your application, ensuring that all meeting content is captured and accessible.

- **Integration with Existing Collaboration & CRM Systems**

  Imported meeting transcripts and participant data will be mapped to your platform’s collaboration, CRM, or project management tools, enabling smooth synchronization with ongoing communication and tasks.

- **Customizable Transcript Data Mapping**

  Users will be able to define how Zoom’s transcript fields, such as speaker labels, conversation timestamps, and discussion points, correspond to fields in your application, allowing for tailored reporting and meeting follow-up.

- **Real-Time Syncing for Meeting & Transcript Updates**

  Any new meeting transcripts or updates to existing ones in Zoom will be reflected in your platform, ensuring that all meeting-related data remains current and accessible.


zoom-transcript.svg

Zoom Transcript

Turn customer conversations into actionable insights with automated transcripts.

This snap-in works as a connector with Glean, the enterprise search platform. It indexes DevRev objects into Glean, enabling them to be searched using filters and keywords.

The snap-in runs on a timed schedule and incrementally indexes DevRev objects. During each scheduled run, the snap-in intelligently identifies objects that have not been indexed yet or have been updated since their last indexing. Once an object is loaded into Glean, it becomes discoverable through the platform.

Ensure the Glean dataset specified in the snap-in's configuration does not already exist or contains no object definitions, as these would be overwritten with the definitions for DevRev objects.

## Features

- **Objects supported**\
  Configure which DevRev objects should be indexed into Glean, such as tickets, issues, accounts, external users, articles, and others.

- **Filtering**\
  Object type, keywords, and stock fields can be used as filters on Glean out of the box.

- **Custom field filtering**\
  Configure which custom fields should be displayed as filters on Glean's UI.

## Installation

For detailed installation and configuration instructions, refer to the [Glean connector documentation](https://devrev.ai/docs/integrations/glean).

glean.svg

Glean Connector

Index DevRev objects into Glean to enable your global search.

# SLA breach notifier for conversation

The snap-in notifies the configured users via Slack in the specified channel whenever a conversation is nearing breach or has breached the SLA.

## **Connections**

### 1. Slack bot pat

- Create a Slack app for your workspace at https://api.slack.com/apps
- In App features, generate bot token in OAuth & Permissions
- Give the app bot Channel-Read, groups-read, user.profile:read, users:read, users.read:email,chat-write access and userGroup-read access
- Invite the bot to the workspace
- Save the bot access token as a connection(snap-in secret) in the DevRev app.

## **Features**

* It sends a Slack message whenever a conversation gets breached or close to breaching its SLA.
* It tags the owner of the conversation and the configured members.
* It adds a first-response-breach tag to the conversation when it breaches the First response SLA.
* It adds a second-response-breach tag to the conversation when it breaches the Second response SLA and adds the value of the tag for further breaches.

## How to use SLA breach notifier for conversation snap-in

1. In the **Configuration** tab, input the slack channel ID where the notifications are to be sent and select the tag to be added for the first response breach, and input the member emails whom to be notified on the first response breach.
2. Also, select the tag to be added for the next response breach and input the member emails of whom to be notified on the next response breach.
3. Install the snap-in.


SLA-Breach-Notifier-Conversation

Notifies the slack channel when a conversation breaches SLA

The Slack Broadcaster snap-in is a specialised automation tool designed to streamline the process of posting broadcast messages, both for customers and within your organization.

## Features

- **Customer Release Notes**\
  Automatically posts release notes to customers via Slack Connect channels, ensuring timely and consistent updates.

- **Account Linking**\
  Allows easy linking of Slack channels to DevRev accounts using the `/slack_broadcaster_link <channel_id>` command within the account timeline. To unlink, use `/slack_broadcaster_link invalid`.

- **Bulk Account Update**\
  Enables linking multiple accounts to Slack channels by uploading a CSV file with account display names and channel IDs. Use `/slack_broadcaster_upload external` or `/slack_broadcaster_upload internal` depending on the audience.

- **Internal Release Notes**\
  Facilitates sharing of release updates within the organization. Upload a CSV file with internal Slack channel names and IDs using the `/slack_broadcaster_upload internal` command.

- **Configuration Management**\
  Restricts broadcast access to authorised users in specific groups, ensuring controlled and secure message delivery.

  &nbsp;

## Installation

For detailed installation and configuration instructions, refer to the [Slack Broadcaster snap-in documentation](https://devrev.ai/docs/automations/slack-broadcaster)

slack.svg

Slack Broadcaster

Slack Broadcaster streamlines the process of sharing broadcast messages with customers and internal teams via Slack

The Calendly snap-in improves scheduling and customer engagement by integrating Calendly bookings into DevRev, preventing missed leads or appointments. It simplifies the process, enabling you to focus on building strong client and prospect relationships.

## Features

- **Automated meeting capture**: Instantly records every meeting in DevRev, eliminating manual data entry.
- **Enhanced engagement tracking**: Easily monitor all customer interactions and appointments in one centralized location, preventing oversight of crucial details.
- **Real-time updates**: Stay informed with real-time updates on scheduled meetings.

## Installation

For detailed installation and configuration instructions, refer to the [Calendly documentation](https://docs.devrev.ai/integrations/calendly).


calendly.svg

Calendly

Streamline prospect meetings with Calendly & DevRev

# Twilio

With the aim of having a single source of truth for all customer problems, DevRev has integrated with Twilio so as to record the customer support requests raised via phone. Customers can now raise their concerns by calling the provided support number on Twilio. Each call creates a support ticket with the call recording, caller identity, and call transcript, enabling the support team to maintain a complete context of the customer's problem.

## Prerequisites

- Ensure you have a Twilio account and a Twilio Flex account for support engineer access.
- Familiarize yourself with Twilio Flex to manage incoming support calls efficiently.
- Configure the required IVR and routing rules on Twilio.

## Features

- **Ticket Creation:** Automatically creates a ticket for each call, enabling support engineers to track and manage customer inquiries.
- **Caller Identity:** If the customer's phone number is available with DevRev, the caller identity will be mapped with the customer identity on the ticket, enabling the support engineer to identify the customer.
- **Capturing Call Details:** The call transcript, call recording, caller details, call duration, and other call-related information are added to the ticket created from the call.

## Installation

For detailed installation and configuration instructions, refer to the [Twilio snap-in](https://docs.devrev.ai/integrations/twilio) documentation.


Twilio.svg

Twilio

Connect Twilio with DevRev for real-time updates on your voice communications.

With the aim of bringing support closer to your customers, DevRev has integrated WhatsApp as a communication channel. Customer concerns raised via WhatsApp messages will sync with the DevRev inbox, allowing you to maintain an unified view of ongoing conversations with your customers for better support management and efficiency.

Learn more about WhatsApp for Business at https://developers.facebook.com/docs/whatsapp/overview#about-the-platform.

## Features

* **Unified Customer Communication**: With the addition of WhatsApp as a communication channel, end customers can conveniently send their queries, bug reports, and feature requests about the DevRev product via WhatsApp. These messages are seamlessly synced with the DevRev inbox, providing a unified view of all customer interactions and minimizing the need for context switching between different communication platforms.
  
* **Automated Template Messages for Efficient Support**: DevRev understands the limitations of the WhatsApp for Business API, which restricts direct agent communication after 24 hours without a response. To address this, DevRev offers support for template messages. When a customer's message remains unanswered for 24 hours, DevRev provides a mechanism to send template messages, ensuring continuous communication and streamlining the support process. These template messages need pre-approval from Meta. To ease the approval process, DevRev automatically sends two templates for approval on installation of the snap-in.

* **Enhanced Support Agent Productivity**: By integrating WhatsApp as a communication channel, DevRev empowers support agents to efficiently manage customer inquiries. When a support agent replies via the DevRev inbox, the update is seamlessly sent to the customer via WhatsApp. This streamlined approach not only keeps customers informed promptly but also boosts support agent productivity by centralizing all customer communications within the DevRev system of record.

## Installation

For detailed installation and configuration instructions, refer to the [WhatsApp documentation](https://docs.devrev.ai/integrations/whatsapp).

### Prerequisites

1. If you do not have an existing Business Account in Meta Business Manager, it is recommended to create one [here](https://business.facebook.com/overview). To get more information about Business Manager, please refer to the article on [Create a Business Manager](https://www.facebook.com/business/help/1710077379203657).

2. If the number is associated with another WhatsApp Account, delete the existing account. To know more, refer to the guide on [Migrate an Existing WhatsApp Number to a Business Account](https://developers.facebook.com/docs/whatsapp/cloud-api/get-started/migrate-existing-whatsapp-number-to-a-business-account/).

3. If you have an existing WhatsApp for Business Account, migrate to 360dialog by following these steps on [Migrating phone numbers](https://docs.360dialog.com/partner/account-setup/migrating-phone-numbers).

### Limitations

1. Group conversations are not supported by WhatsApp for Business API. 
2. If you do not respond to the customer’s message within 24 hours, you can only respond to the conversation using Meta-approved template messages. Know more [here](https://developers.facebook.com/docs/whatsapp/message-templates/guidelines).


whatsapp.svg

WhatsApp

Enable your customers to raise their concerns using WhatsApp. WhatsApp messages will be synced with DevRev inbox thus minimizing context switching and streamlining your support operations.

The Zendesk Airdrop Snap-in simplifies importing contacts, tickets, and users from Zendesk into DevRev. It enables you to review customer support data or link customer tickets to DevRev's build app to streamline development and review processes. You can also keep your Zendesk tickets and DevRev tickets in sync, allowing you to work out of DevRev seamlessly.

## Features

**Import**

A one-time import enables you to quickly transfer essential contacts, tickets, and user information from Zendesk to DevRev, sparing you manual data entry across multiple systems, and ultimately saving time and effort.

**Sync to DevRev**

The sync to DevRev enables you to synchronize new items and updates since the last import, ensuring that your DevRev data remains current without the need for frequent manual imports.

**Sync to Zendesk**

The sync to Zendesk feature allows you to apply modifications made in DevRev to previously imported Zendesk items. You also have the option to create new items in DevRev for synchronization with Zendesk.

## Installation

For detailed installation and configuration instructions, refer to the [Zendesk Airdrop documentation](https://devrev.ai/docs/integrations/zendesk).


zendesk.svg

Zendesk

Get started with DevRev support or build with real data from Zendesk.

The Salesforce Airdrop Snap-in simplifies importing accounts, cases, and users from Salesforce into DevRev, offering comprehensive customer insights. This data empowers you to prioritize development efforts and enhance customer support. Additionally, it enables seamless workflow by synchronizing Salesforce cases and DevRev tickets, allowing you to work efficiently within DevRev.

## Features

**Import**

A one-time import streamlines the process of importing all relevant accounts, cases, and user data from Salesforce into DevRev. Eliminating manual data entry across multiple systems saves you time and effort.

**Sync to DevRev**

The sync to DevRev enables you to synchronize new items and updates since the last import, ensuring that your DevRev data remains current without the need for frequent manual imports.

**Sync to Salesforce**

The sync to Salesforce feature allows you to apply modifications made in DevRev to previously imported Salesforce items. You also have the option to create new items in DevRev for synchronization with Salesforce.

## Getting Started

For detailed installation and configuration instructions, refer to the  [Salesforce Airdrop documentation](https://docs.devrev.ai/integrations/salesforce).


salesforce.svg

Salesforce

Import your Salesforce accounts, cases and users.

The Email integration snap-in automatically transforms incoming emails into a conversation or a ticket, providing a centralized platform for handling, responding to, and tracking customer interactions.

Bid farewell to juggling between numerous tabs and platforms. With DevRev, you can efficiently manage all your support tickets and conversations in one place.

## Features

- **Get tickets or conversations from support email**
 
  Whenever a customer sends an email to your support address, an automated process generates a new ticket or a conversation, automatically populating it with customer information. Subsequent customer email replies update the ticket or conversation with new comments.

- **Reply to the customer through Customer Messages tab**

  Each time a customer experience team member posts a comment within the ticket's customer messages tab, an email containing that reply is sent to the respective customer through your integrated support email. The email thread follows the structure of the initial email received at your support email address.

- **Enable bot replies**
 
  By enabling bot replies, the email integration bot sends an automated reply, borrowing some time for response and requesting any additional information that may help with the customer’s inquiry. It also allows you to decide whether or not to send emails to the customer for comments added by other bots in the customer messages tab.

- **Assign tickets or conversations to a part and owner**
 
  When you set up the snap-in, you can assign tickets or conversations to a default owner and part.

- **Support for attachments and raw email**

  Attachments sent by customers are visible in the customer messages section, alongside ticket comments. You can include attachments (with a maximum size limit of 25 MB) in your responses to comments, and these attachments will be sent to the customer via email.

- **Support for multiple providers**
 
  This snap-in works with a variety of email providers, including Google Workspace, Microsoft Outlook, Yahoo Mail, Zoho Mail, and custom domain emails.

## Installation

For more information about this snap-in, refer to the [Email integration documentation](https://devrev.ai/docs/integrations/email).


email-icon.webp

Email Integration

Enable your customers to create conversations and tickets using email.

Enable Slack users to reduce context switching and interact with DevRev from within Slack. Create DevRev tickets from Slack conversations and keep your customers up to date.

## Features

Connect with Slack and ensure your customer or internal conversations are always in sync with DevRev tickets.

- **Conversation tracking**

  With conversation tracking, you can track your Slack conversations with customers and the resulting tickets so you don't lose context. Keep the conversation going in Slack or DevRev and never miss an update.
- **Create tickets**

  Use the ⋮ actions menu to create a ticket from an existing Slack conversation. When you use this action, your ticket will contain a link back to the Slack conversations.
- **Preview record**

  Slack shows a title, description, status, and owner preview any time you post a DevRev URL.
- **Ticket updates**

  Updates on DevRev tickets can be posted in Slack, so conversations are in sync. If you have customer conversations over Slack, then this automation enables automatic status updates.
- **Personal view of tickets**

  With `/devrev view` ticket ID or issue ID, the user can display a preview of the work items. This view is private to the user who uses this command and is not available for everyone on the Slack channel or direct message.
- **Share ticket**

  With `/devrev show` ticket ID or issue ID, the user can display a preview of the work items to everyone in that channel or direct message.

## Installation

For detailed installation and configuration instructions, refer to the [Slack documentation](https://devrev.ai/docs/integrations/slack).

Slack

Scale your customer support in Slack! Enable real-time bidirectional sync with Slack and bring order to the chaos.

The GoodMeetings snap-in enables you to transform your meetings into actionable items by intelligently aligning discussions with tasks assigned at a user level. It streamlines your workflow, allowing you to focus on business growth and nurturing client relationships.

## Features

### Automated meeting sync:

Your meeting recordings and relevant metadata seamlessly integrate into DevRev’s Engagements without manual input.

### Fully autonomous to-do list:

Each day, wake up to discover your Tasks automatically curated based on commitments established in both customer and internal meetings, all within DevRev.

## Installation

For detailed installation and configuration instructions, refer to [here](https://goodmeetings.ai/devrev-snap-in/).

## Contact

To contact the developers , send an email to hello@goodmeetings.ai

logo1.webp

Goodmeetings

Streamline your customers meetings, create summary and action items with Goodmeetings and DevRev

## Review Ingestion Snap-in
This Snap-in extracts reviews from the Google Play Store using scraper and creates tickets.

**For Initial extraction**
    - Initial extraction can be invoked by the command `extract_initial_playstore_reviews` in the snap-in discussions.
    - The snap-in creates a subtype along with the necessary custom fields under it.
    - The snap-in ingests the number of reviews mentioned by the user in the configuration.
    - The extraction always starts from the latest.


Review Ingestion

Extracts reviews from the Google Play Store and creates tickets for them.

The sentiment evaluator snap-in uses advanced sentiment analysis algorithms to evaluate the customer sentiment of every resolved conversation and classify it into one of the following categories:  
* Delighted
* Happy
* Neutral
* Unhappy
* Frustrated

Additionally, it provides a concise justification for its analysis, empowering customer experience engineers with actionable insights into customer sentiment.

>Note: The sentiment evaluator snap-in is only available for the dev users.

## How it works

Once a conversation is resolved, the sentiment evaluator snap-in analyzes the customer messages, catching nuanced emotional cues, and categorizes the sentiment accordingly.

## Features

- **Immediate analysis**

    It provides fast and accurate sentiment analysis once a ticket is resolved.
 
- **Sentiment breakdown**

    It doesn't just classify sentiments, it also provides a clear justification for its analysis, helping you understand your customers better.
 
 - **Cross-platform compatibility**

     It can analyze customer interactions via email, PLuG, Slack, or any other medium.

- **High accuracy**

    It minimizes errors by only assigning sentiments when it has high confidence.

## Installation

For detailed installation and configuration instructions, refer to the [Sentiment evaluator documentation](https://devrev.ai/docs/automations/sentiment-evaluator).


Sentiment Evaluator

Evaluate the sentiment of every resolved conversation and provide a brief justification, classifying them into one of five categories: `frustrated`, `unhappy`, `neutral`, `happy` or `delighted`.

# Spam Shield snap-in

The spam shield snap-in is a sophisticated tool designed to analyze the first customer message and determine whether a ticket or conversation is spam. It uses advanced algorithms to identify patterns indicative of spam content, ensuring that customer support teams can focus their efforts on genuine customer interactions.

## How it works

Once a ticket or conversation is created, the spam shield snap-in analyzes the customer message that created the conversation or ticket for spam indicators, such as marketing content, meaningless words or phrases, or out-of-office messages. It then flags the conversation or tickets as spam if it meets the predefined criteria.

## Features

- **User-controlled spam management**: Users can select the option whether to directly mark a conversation or ticket as spam or to provide a suggestion, allowing for a more nuanced approach to spam management.
  
- **Efficient spam detection**: The snap-in swiftly detects and flags spam messages, reducing the time spent by support agents on spammy conversations.

- **Cross-Channel Compatibility**:  It can analyze customer messages from various channels, providing comprehensive spam management across all customer touchpoints.


Spam Shield

The spam shield snap-in detects and flags spam messages across multiple channels, allowing support teams to focus on genuine customer interactions.

Make it snappy

Start building your own Snap-ins

Get started with SnapKit