feat: add feedback endpoint for bug reports and feature requests (BDMS-897)

[jeremyzilar]

What this does

Adds POST /feedback, a new authenticated endpoint that accepts a bug report or feature request submitted from the Ocotillo UI and does two things:

1. Creates a Jira issue in the BDMS project via the Jira API
2. Posts a Slack notification to a configurable webhook (optional)

Endpoint

POST /feedback
Authorization: Bearer <token>   (any authenticated Ocotillo user)

Bug report payload

{
  "type": "bug",
  "page_url": "https://ocotillo.nmbgmr.nmt.edu/ocotillo/well",
  "reporter_name": "Jane Field",
  "reporter_email": "jane@nmt.edu",
  "browser": "Chrome 125",
  "submitted_at": "2026-06-11T20:00:00Z",
  "what_happened": "The export button does nothing when I click it.",
  "severity": "High"
}

Feature request payload

{
  "type": "feature",
  "page_url": "https://ocotillo.nmbgmr.nmt.edu/ocotillo/well",
  "reporter_name": "Jane Field",
  "problem": "I can't filter wells by aquifer.",
  "who_would_use": "Hydrogeologists running regional studies",
  "what_it_should_do": "Add an aquifer dropdown to the wells filter bar."
}

Response

{
  "jira_key": "BDMS-999",
  "jira_url": "https://nmbgmr.atlassian.net/browse/BDMS-999"
}

What gets created in Jira

• Bug → Jira issue type Bug, priority mapped from severity (Low/Medium/High), description includes what happened, severity, and context (page, reporter, browser, timestamp)
• Feature request → Jira issue type Task, priority Medium, description includes the problem, who would use it, and what it should do

What gets posted to Slack

A formatted Slack message with the Jira ticket link, reporter name, page URL, and a summary of the report. The Slack notification is best-effort — if the webhook call fails, the endpoint still returns the Jira key to the UI so the user sees confirmation.

Files changed

File	Change
api/feedback.py	New router — schema, Jira builder, Slack builder, POST endpoint
core/initializers.py	Register the feedback router
.env.example	Document the four new env vars

Environment variables

Three are required for the endpoint to work. One is optional.

Variable	Required	Description
JIRA_BASE_URL	Yes	e.g. https://nmbgmr.atlassian.net
JIRA_EMAIL	Yes	Jira account email used for API auth
JIRA_API_TOKEN	Yes	Jira API token (not your password)
JIRA_DEFAULT_PROJECT	No	Jira project key, defaults to BDMS
SLACK_FEEDBACK_WEBHOOK_URL	No	Slack incoming webhook URL — will be provided separately. Leave blank to skip Slack.

These need to be added to the staging and production Secret Manager / environment config before deploying. The SLACK_FEEDBACK_WEBHOOK_URL will be provided outside of this PR.

Auth

The endpoint uses viewer_dependency — any logged-in Ocotillo user can submit feedback. Anonymous submissions are not accepted.