1 Open a Chat with Reva
In Microsoft Teams, find Reva in your app list (or search for it). Open a 1:1 chat.
If Reva doesn't appear, your Teams admin may need to approve the sideloaded app. See the installation guide for details.
2 Say Hello
Send a greeting in German or English — Reva auto-detects the language and responds accordingly.
| You type | Reva responds with |
|---|---|
Hallo | A German greeting and overview of capabilities |
Hello | An English greeting and overview of capabilities |
3 Try These Example Queries
Release Management
Queries about your Digital.ai Release instance:
English
“List all active releases”
Shows releases with status, dates, and IDs
Deutsch
“Zeige alle aktiven Releases”
Listet Releases mit Status, Datum und ID
English
“My dashboard”
Personal overview — releases where you’re on a team
Deutsch
“Meine Releases”
Persönliche Übersicht deiner zugewiesenen Releases
English
“Show release Q2 Deploy”
Detailed view of a specific release
Deutsch
“Zeige Release Q2 Deploy”
Detailansicht eines bestimmten Releases
English
“What tasks are open in release X?”
Lists open tasks for a specific release
Deutsch
“Welche Aufgaben sind offen in Release X?”
Offene Aufgaben eines bestimmten Releases
Jira Integration
Queries about your Jira Cloud instance (if configured):
English
“Search Jira issues in project REVA”
Lists issues from a Jira project
Deutsch
“Suche Jira-Tickets im Projekt REVA”
Listet Issues eines Jira-Projekts
English
“Show Jira issue REVA-42”
Full details of a specific issue
Deutsch
“Zeige Jira-Ticket REVA-42”
Detailansicht eines bestimmten Tickets
4 Follow Up Naturally
Reva remembers context within a conversation. After listing releases, you can follow up without repeating yourself:
You
“List active releases”
Reva
[shows 5 releases]
You
“Tell me more about the second one”
Reva
[shows details of that release]
You
“Who’s on the team?”
Reva
[shows team members for that release]
5 Tips for Best Results
- Be specific — “Show release Q2-Deploy-2026” works better than “show me stuff”
- Use release names or IDs — Reva resolves them via the Release API
- Switch languages freely — you can mix German and English queries in the same conversation
- Reset when stuck — type
forgetto clear conversation history and start fresh
| Command | What it does |
|---|---|
forget / vergiss | Clears conversation history — start fresh |
My dashboard / Meine Releases | Personal release overview |
6 Troubleshooting
Reva doesn’t respond
- Check the health endpoint:
curl http://<host>/api/health - Verify
adapter_initializedistruein the health response - Check logs:
docker compose logs -f revaorkubectl logs -n reva deploy/reva -c reva
“I couldn’t find any releases”
- Verify Digital.ai Release connectivity:
mcp.release.connected: truein health check - Ensure the Release API URL and credentials are correct
- Try a broader query:
List all releases
“I don’t have access to Jira”
- Check
mcp.jira.connectedin the health endpoint - Verify Jira URL, username, and API token are configured
- Jira is optional — Release features work without it
Slow responses
- Typical response time is 15–25 seconds with
qwen3:14bon a 16 GB GPU - Ensure Ollama is running and the GPU is not shared with other workloads
- Do not set
OLLAMA_NUM_PARALLEL> 1 with less than 24 GB VRAM
Next Steps
- Compatibility Matrix — supported versions of Release, Jira, Kubernetes, and more
- Optional Integrations — LDAP, notifications, monitoring, memory
- Operations Guide — backups, support bundles, monitoring
- Contact us — questions, feedback, or demo requests