On this page

Jan 09 to Feb 09, 2024

9 new enhancements; 11 resolved issues

What's new

  • Airdrop Manage Recipe Introducing Multi-step Recipe Mapping!

    Now, DevRev users can effortlessly tailor their migration or sync processes by handpicking included/excluded types and specific fields, empowering precise control over data transitions.

  • Auth Platform Now you can find all your connections in Settings > Integrations > Snap-ins or Import in the top-right corner. In addition, the Connections page now has a better interface and search.

  • Custom Field Groups Custom Field Groups

    We have introduced the ability for end-users to define groups for custom fields, allowing for better rendering in the UI.

    New Features:

    • Expand group accordion if it has a required field: Added functionality to automatically expand the group accordion if it contains a required field.

    What's improved:

    • Web UI: Group names for related custom fields: Implemented the ability to assign group names to related custom fields in the web UI.
  • Email Integration We are pleased to announce significant improvements to DevRev's email integration capabilities.

    Simplified Gmail Connection: For organizations utilizing Gmail, setting up email connections has been simplified. Link your organization's Gmail account directly within DevRev with just a few clicks, without any requirements for DNS record addition. For more information, please refer here: Creating a Gmail Connection.

    Email Summarization: Ticket descriptions generated from email integration have undergone a significant overhaul. Instead of presenting only the initial email message, we now offer a comprehensive summary of the entire email thread. This improvement facilitates faster and more effective issue diagnosis.

    Improved Customer Inference: Our customer identification process has been refined, enabling us to accurately discern the original customer sender in a thread forwarded by a DevUser to support. This refinement streamlines SLA application and customer tracking, without necessitating direct customer involvement in the email thread.

    Enhanced Email Viewer: We've upgraded our email viewer for better clarity and convenience. Now, easily identify senders and recipients for each message, view complete formatted emails along with inline images directly in the timeline, and access forwarded emails without using "Show Original Email".

    👉 For more information about Email Integration, refer to the following articles: ‣ Customer email notificationsEmail

  • My Snap-Ins User level snap-ins and UI revamp: Now snap-in builders can create snap-ins that have user-level configuration. Snap-in users can now have user-level preferences after this update. The Snap-in config page also has a brand-new, intuitive, and sleek UI.

  • Per DevOrg Stock Field Overrides Stock Overrides are here!

    This feature allows customers to define specific properties on a stock field. Currently, we've extended this feature to cover three properties:

    • Display name of the field

    • Optionality of a field (only making it optional or mandatory is allowed)

    • These overrides will impact various views like list/filter/side-panel/customize-col/sort-by/group-by/info-tooltips/link-widgets/bulk-actions, and more. Essentially, any of the stock fields can now be marked as mandatory, the field can be hidden from UI etc.

    NOTE: These overrides can currently be set through API only. While we work on the UI component, you can use the same fragment set APIs to add stock overrides.

  • Search Search v2

    1. UI is now revamped which is cleaner and packed with more utility

    2. Recent recommended items are now visible when set to search 'Everywhere' without any filters.

    3. When more contexts are added, they are now neatly stowed away within a dropdown

    4. Filters can now be accessed through UI without having to write a query.

    5. Search commands documentation is now available to help discover operators and fields that are supported with search

    👉 For more information about Search, refer to the following article: Search

  • Sprint mode Sprint board creation and management are more flexible and dynamic than before. Here are the key new additions:

    1. A brand new page for showing all sprint boards so that you don't have to go digging for them by visiting Trails and then Parts . It also has a quick call to action on top to create a new sprint board easily from here.

    2. Sprint boards are no longer just tied to a single-part hierarchy. You can create team-based sprint boards or a board to work across part hierarchies. You can use any combination of issue filters to define the backlog which makes sprint backlog management super specific to your team's needs.

    3. There is a settings page on the sprint board that allows you to change the backlog filters at any time post creation to keep up with your team's evolving needs to manage the work.

    4. Issues can be assigned to any sprint board from the searchable sprint drop-down on the issue side-pane and not restricted to sprint boards on a specific part anymore.

    5. It is super beneficial to know which teams are working on a certain product part currently, so we have retained the ability to see sprint boards on a certain Part but unlike before, it is much smarter and up-to-date data by showing only those sprint boards where in active sprint, work is happening on the Part actually in terms of issues assigned

    👉 For more information about Sprint mode, refer to the following article: Sprint mode

  • Support Turing Bot Interactive Search on Customer Portal and PLuG

    Enhancement includes generative AI search on PLuG and Portal, backed by Turing. The goal is to provide a more conversational and delightful search experience, differentiating from competitors and anticipating future trends in chat-based search.

    This will reduce the pain of users going into a hierarchical structure of the KB and then spending time to find the right article. Instead, they can just use the Turing conversational search to get their answers instantly.

    This can be enabled on both PLuG and Portal by going to the respective PLuG/Portal settings and enabling the "Turing Search" section.

    👉 For more information about Support Turing Bot, refer to the following article: Turing bot

What's fixed

  • PLuG Widget The toggle theme method allows you to dynamically modify the PLuG SDK's theme, even after initializing the PLuG widget. This functionality enables real-time adjustments to the PLuG widget's theme based on diverse themes preferred by your users.

  • PLuG Widget The start conversation method is utilized to open the PLuG widget with the conversation creation view activated. It essentially replicates the action of clicking the Send us a message button, launching the widget directly to the conversation initiation screen.

    The method also accepts an optional input parameter, allowing you to pre-fill a message in the conversation creation screen. This provides your users with a prompt to initiate a conversation with your team.

  • Part customization Customizing your parts for streamlining day-to-day operations has never been easier as now you can manage custom fields for parts from our Object customization UI on our Settings page. We have also added much-needed support for filtering, sorting, and grouping on custom fields for Parts so that you can use Parts in our app just the way you want.

  • Roadmap We are thrilled to introduce several key enhancements to our Gantt-View, designed to boost your productivity while ensuring a smooth user experience:

    1. Direct Date Additions: Now, add target dates directly via the chart, bypassing multiple interfaces and setting target dates without needing to access the side panel.

    2. Markers for Non-Visible Nodes: Get a snapshot of target dates for non-visible nodes courtesy of our new markers. A click takes you right to the respective enhancement.

    3. Group-by Mode: We've adopted the 'group by' mode from list-view to Gantt-View for efficient task categorization and management.

  • SLA Added support for Ticket subtypes when creating SLA policies.

  • SLA Fixed a bug where org schedule was off by one day.

  • SLA Added ability to mark an SLA as default. If an SLA is marked as default, all customers that are not added specifically to an SLA will fall under the default SLA.

  • SLA Fixed a bug where SLA would show completed even when no SLA was applied to a ticket.

  • SLA Fixed a bug where next response SLA was not showing up on tickets. This is now fixed.

  • Social Stop notifications for all low-priority updates, including bot-triggered field updates. This is to reduce the noise from the Updates page.

  • Timeline Now users can mention a Group on the discussions timeline and everyone who is part of the group gets notified. All the users of the group would receive this as an Important notification. This resolves the problem of finding the right person to tag or tagging everyone in a team individually.