Let's face it, you had work to do. Now you can spend more of it doing work and less time wrangling Jira data into a presentable format for the daily updates. This project automatically creates status reports of newly closed and in-progress issues – delivering a steady stream of reassuring information that minimizes the chances of 'urgent' requests and performance check-ins. Consider it strategic risk management-specifically, minimizing management friction. Bonus: you might even get a 'good job' (we’re not guaranteeing it).
- python 3.14
- Ollama running on your local machine with eg Llama 3.2 model
- create your own version of .env from .env.local
- and then run:
uv run --env-file .env -- python src/main.py
when running in corporate environment with local index, use:
uv run -i url_of_private_index --env-file .env -- python src/main.py
- JIRA_API_KEY - your personal API token
- JIRA_API_VERSION - ("2" or "3")
- 3 – Jira Cloud (recommended, modern API)
- 2 – legacy Jira / Jira Server / older Cloud instances
- JIRA_AUTH_TYPE - Authentication method used to access Jira.
- basic – email + API token (standard for Jira Cloud)
- bearer – legacy Bearer token authentication (older Jira / Server)
- JIRA_EMAIL- Email address associated with your Jira account.
- Required only when: JIRA_AUTH_TYPE=basic
- JIRA_BASE_URL - eg. https://jira.mycompany.com
- MODEL_NAME - local Ollama model for status report generating
- VERIFY_SSL - needs to be set to 'true' when dealing with self signed certificates
**Status Report**
**Closed Issues:**
1. Ticket: TEST-123 - Resolution: Fixed
2. Ticket: TEST-124 - Resolution: Cancelled
3. Ticket: TEST-125 - Resolution: Cancelled
**Open Issue:**
1. Ticket: TEST-126 - Description: server is crashing because of OOM. Progress: Deployment Backlog - 0