The problem is not “ChatGPT on Jira.” The problem is years of ICIS support tickets and
.msg attachments that keyword search cannot recall. SRAG ingests Jira Cloud REST
v3 only (v2 search is HTTP 410 on this instance), parses .msg via extract-msg,
chunks with overlap, embeds nomic-embed-text at 768 dims through
local Ollama, stores srag_chunks.embedding vector(768). Query: cosine nearest
chunks, optional MiniMax-Text-01 synthesis via shared.llm.dispatch — model is
hardcoded, not an env knob. Changing the embedder means re-ingest. Login for ingest/query/chunks/health
UI; public landing. This is not SRM2’s workspace and not Herald. If Ollama or pgvector is down,
retrieval is empty — not a hallucinated policy.
Ingest is a job. Query is a cosine search. Synthesis is optional and must cite chunks.
Not Jira’s own search. Not SRM2 Review Board.
v2 search 410 — this app already moved to v3.
embedder.py hardcodes the model. Health UI is login-gated.
SRM/SRM2 write Jira. SRAG reads history. Do not paste workspace screenshots here.
Will not invent an answer when the index is empty. Public landing lists no ticket bodies.
People who remember “we saw this in 2023” and cannot find it.
Cards match SRAG README files.
Login for /srag/app. This page is not your ticket index.
Open SRAGRequires a MelTuc account. Create one free.
Support Request RAG System — Jira ticket ingestion, email parsing, natural language search. Health stays cheap. If this page disagrees with the signed-in app, trust the app — the product contract and tests enforce that rule.