Skip to content

feat: Issue resolution confirmation button and rag solution dialog#68

Merged
sachmii merged 7 commits into
mainfrom
feat/53/issue-resolution-confirmation-button-and-rag-solution-dialog
Jun 21, 2026
Merged

feat: Issue resolution confirmation button and rag solution dialog#68
sachmii merged 7 commits into
mainfrom
feat/53/issue-resolution-confirmation-button-and-rag-solution-dialog

Conversation

@sachmii

@sachmii sachmii commented Jun 16, 2026

Copy link
Copy Markdown
Collaborator

Summary

‼️ Based on PR #67 ‼️

Here is the PR description formatted in Markdown, ready to be pasted into your GitHub Pull Request:


feat: Add Issue Resolution and RAG Feedback Workflow

Description

This PR introduces a structured workflow for resolving incidents within the DevPulse dashboard. It replaces an instant-close action with a confirmation mechanism, ensuring incidents are handled deliberately and allowing users to contribute custom solutions to our RAG knowledge base.

Key Changes

UI/UX

  • Resolution Modal: Introduced ResolveModal.jsx and ResolveModal.css to provide a clean interface for finalizing incident resolution.
  • Insights Integration: Updated InsightsPanel.jsx to include the new resolution trigger, supported by new icons like AnalyzeIcon.jsx.
  • Styling: Added shared component styles to App.css and LogList.css to maintain consistent design across the dashboard.

Functionality

  • Dual Resolution Paths: Users can now choose between a simple "Mark as Resolved" action or submitting a custom fix via the RAG feedback text area.
  • API Integration: Implemented necessary backend communication logic in client/src/lib/api.js to support the new resolution endpoints.

Component

  • Client: client/
  • API contract: api/
  • Spring ingestion: services/spring-ingestion/
  • Spring logbook: services/spring-logbook/
  • Spring alerts: services/spring-alerts/
  • GenAI: services/py-intelligence/
  • Infrastructure: infra/
  • CI/CD: .github/workflows/
  • Documentation

API Impact

  • This changes the API.
  • api/openapi.yaml was updated.
  • This does not change the API.

Testing

  • I tested this locally.
  • I added or updated tests.
  • Tests are not applicable for this change.

Checklist

  • Branch name follows (feat|fix)/(issue_id)/(name_of_issue).
  • The change is limited to the intended component(s).
  • Documentation was updated if needed.

Related Issue

Closes #53

Screenshot 2026-06-21 at 20 46 38 Screenshot 2026-06-21 at 20 50 31 Screenshot 2026-06-21 at 20 50 52 Screenshot 2026-06-21 at 20 51 17

@sachmii sachmii linked an issue Jun 16, 2026 that may be closed by this pull request
14 tasks
@sachmii sachmii self-assigned this Jun 16, 2026
@sachmii sachmii requested review from memreo and tahahundekari June 16, 2026 14:25
@sachmii sachmii added feature New features client Pull requests that update client code labels Jun 16, 2026

@tahahundekari tahahundekari left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thank you for these changes!

@memreo memreo left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@sachmii sachmii merged commit 022eeec into main Jun 21, 2026
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

client Pull requests that update client code feature New features

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add issue resolution confirmation button and RAG solution dialog

3 participants