Browse Snap-Ins
stage-breach-notifier
Stage Breach Notifier
by DevRev

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.
  1. In the snap-in Discussion tab, enter the /upload_stage_csv command.
  2. 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.
  3. Reload the page to see the changes in the Configuration tab.
  4. 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