Building a Custom Jira Assistant with Moveworks: From OOB to Tailored Experience
🚀 Building a Jira Assistant with Moveworks
Â
📌The Need
Switching between a conversational assistant and Jira to find issues, review details, or add updates can interrupt productivity.
We leveraged the OOB Jira plugin capability as a foundation and enhanced it to meet our specific business use cases and user experience requirements.
The result is a tailored Jira experience that allows users to retrieve and update Jira information directly through natural-language conversations.
Â
đź”§ What We Built
Our Jira Assistant supports four common scenarios:
- View Jira tasks assigned to the current user
- Retrieve details of a specific Jira issue
- Add a comment to a Jira issue
- Search assigned Jira issues using keywords
Users can simply ask:
- 💬 “Show my Jira tasks”
- 💬 “Show details for Jira PROD-2110”
- 💬 “Add a comment to Jira PROD-2110”
- 💬 “Find my Jira issues related to VPN”
Â
🏗️ Solution Architecture
Â
User Utterance → Moveworks Plugin → Conversational Process → HTTP Action → Jira REST API → Script Action → Formatted Response
Each request starts with a natural-language user utterance. Moveworks identifies the appropriate capability, collects the required inputs through a Conversational Process, and passes them to an HTTP Action.
The HTTP Action communicates with the Jira REST API, while a Script Action transforms the API response into a concise, user-friendly conversational response.
Â
đź’ˇ Key Challenges & Learnings
Â
1. Slot mapping matters
Even when a Conversational Process captures the correct value, explicitly mapping the slot to the HTTP Action is critical to ensure the value reaches the API request.
2. Design for the conversational experience
Instead of displaying hundreds of Jira issues, we return the 50 most recently updated open issues and provide keyword search for finding specific issues.
3. Keep capabilities focused
Breaking the solution into focused capabilities makes the experience easier to maintain, troubleshoot, and extend.
4. Make user utterances intentional
Including “Jira” in sample utterances helped make the intended capability clear and improved the overall user experience.
Â
🎯 The Result
Users can now search, view, and update Jira issues without leaving Moveworks, reducing the need to switch between applications for common Jira tasks.
Â
From “Show my Jira tasks” to “Add a comment to Jira PROD-2110” — users can now get it done directly in Moveworks. 🚀