Managing task progress and deadline overruns with DevRev's Issues, Agent, and OLA
This page has been translated by machine translation. View original
Introduction
In this article, we will check the basic usage of progress management using the Issues Gantt chart display in DevRev. Next, we will explain how to use Agents to query the status of Issues in natural language, and finally, we will configure a mechanism to detect work period overruns using the OLA Metrics On Issues snap-in and OLA settings.
What is DevRev?
DevRev is a platform that can automate business workflows by connecting external services with Triggers/Actions. It can integrate content obtained from multiple channels as profiles linked to the same person, enabling automation with context preservation even when points of contact are dispersed.
Target Audience
- Those considering implementing DevRev and wanting to know specific use cases for task management
- Those who want to manage task progress using Issues with AI support
- Those who want to implement a system that sets rules for task work periods and automatically issues warnings when they are violated
References
- https://support.devrev.ai/en-US/devrev/article/ART-21870
- https://marketplace.devrev.ai/ola-metric-on-issues
Issues Overview
In DevRev, you can manage tasks at the Issue level. You can view the list of Issues from Work > Issues in the left navigation.
Let's try creating a few Issues.
By switching the View type to Gantt view, you can display Issues in Gantt chart format.
On the Gantt chart, bars are displayed based on the start and end dates of each Issue. Issues with no start or end date specified are marked with an "!" sign, making it easy to find Issues with missing date settings.
Agent Integration
To enable querying the status of Issues in natural language, we set up an Agent. An Agent is a bot that answers questions in chat format while accessing objects on DevRev.
Creating and Overview of an Agent
I created a new Agent from Settings > Agents and configured it to answer questions about Issues. As explained in the settings below, it has been given permissions to access contexts such as Issues and Tasks. This allows you to simply ask questions like "Please tell me the Issues I'm currently responsible for" in the browser chat and get a list in response.
Various Configuration Values
Instructions
Adhere strictly to the following guidelines:
- Provide only factual, evidence-based information
- Never fabricate, guess, or hallucinate information
- If uncertain or lacking knowledge, explicitly state "I don't know" or "I don't have enough information"
- Cite uncertainty when information may be incomplete or outdated
- Prioritize accuracy over completeness
Skills & Tools
FetchObjectContext (Object ID: auto)
Knowledge
DevUser
Issue
Product
Tag
Task
Workspace
Account
Contact
Dashboard
Operation Check
This time, I sent the following question in Japanese.
私の現在の Issue の状況を教えて
The Agent responded with the following:
現在、あなたが所有している Issue の状況は以下の通りです。
1. データインポートツールの本番リリース
- 状態: Open
- ステージ: Triage
- 作成日: 2025-12-11
- 最終更新日: 2025-12-11
2. データインポートツールの開発
- 状態: In Progress
- ステージ: In Development
- 作成日: 2025-12-11
- 最終更新日: 2025-12-11
- 目標終了日: 2025-12-17
3. Python スクリプトの不具合修正
- 状態: In Progress
- ステージ: In Development
- 作成日: 2025-12-11
- 最終更新日: 2025-12-11
- 目標終了日: 2025-12-12
4. データインポートツールの動作検証
- 状態: Open
- ステージ: Triage
- 作成日: 2025-12-11
- 最終更新日: 2025-12-11
- 目標終了日: 2025-12-24
5. データインポートツールの受け入れ試験
- 状態: Open
- ステージ: Triage
- 作成日: 2025-12-11
- 最終更新日: 2025-12-11
- 目標終了日: 2026-01-08
6. 社内ドキュメント整備
- 状態: In Progress
- ステージ: In Development
- 作成日: 2025-12-11
- 最終更新日: 2025-12-11
- 目標終了日: 2025-12-24
これらの Issue の中で、特に詳細が必要なものがあれば教えてください。
OLA Settings
I'll explain how to set up OLA for Issues work periods and how to issue warnings when periods are exceeded.
DevRev's OLA is a function that defines an internal target time for "when you want to respond to" target objects. By enabling the OLA Metrics On Issues snap-in, you can treat Issues as targets for this OLA.
The general flow is as follows:
- Enable the OLA Metrics On Issues snap-in
- Create an OLA for Issues and set Breach Target and Warning time
- Publish the OLA to activate it
Enable OLA Metrics On Issues
To make Issues targets for OLA, enable the OLA Metrics On Issues snap-in. Open Settings > Integrations > Snap-ins and select OLA Metrics On Issues from the list.
Click the Add button on the details screen to add it to your Workspace.
Then, configure which Subtypes and Statuses to target.
Once the configuration is complete, OLA Metrics On Issues will show as Activate in the list view.
Create OLA
Create an OLA and set target times and warning times for Issues.
Open Settings > Support > OLAs and create a new OLA. Then, to define a policy for Issues, click + Issue Policy.
On the policy details screen, click + Add Metric to add metrics to apply to Issues.
On the metrics configuration screen, specify the Breach Target (the period until considered a violation) and Warning time (when to issue a warning).
For example, for an Issue that you want to address within 3 days of creation, if you set the Breach Target to 3 days and the Warning time to 2 days, a Warning will be displayed after 2 days from creation, and it will be treated as a Breach if it exceeds 3 days.
When the configuration is complete, press the Publish button to activate the OLA.
Summary
In this article, we explained how to streamline task management by combining DevRev's Issues feature with Agents and OLA Metrics On Issues. It would be good to adjust the Subtypes and Statuses of Issues to target, and the Breach Target values according to your organization's operations.
