Skip to content

feat: store and display helpdesk actor on posts and resource state transitions - #1248

Open
ondraholis wants to merge 16 commits into
feature/helpdesk-integration-rolefrom
feature/helpdesk-actor
Open

feat: store and display helpdesk actor on posts and resource state transitions#1248
ondraholis wants to merge 16 commits into
feature/helpdesk-integration-rolefrom
feature/helpdesk-actor

Conversation

@ondraholis

@ondraholis ondraholis commented Jul 31, 2026

Copy link
Copy Markdown
Collaborator

Description:

When a resource state transition or a post is created via the helpdesk integration role, the name of the human actor behind the action was not recorded or visible — only the technical integration user appeared. This PR introduces a helpdesk_actor field on both post and negotiation_resource_lifecycle_record tables. When a request comes in via ROLE_HELPDESK_INTEGRATION, the caller can pass the actor's name which is persisted and used as the display name in the negotiation timeline, replacing the generic integration user name.

The actor name is provided in two ways depending on the operation:

  • Resource state transitions — via the X-Helpdesk-Actor request header on the POST /v3/negotiations/{id}/resources/{resourceId}/lifecycle/{event} endpoint
  • Posts — via the helpdeskActor field in the request body

The value is only applied when the authenticated user holds ROLE_HELPDESK_INTEGRATION; it is silently ignored for all other roles.

The PR covers Change 2 and 3 from integration plan as described in helpdesk-integration-plan.md.

Checklist:

Required for all pull requests:

  • I have performed a self-review of my code
  • I have made my code as simple as possible
  • I have removed all commented code
  • I have described the PR and added a meaningful title in the Conventional Commits format
  • I have added relevant tests for my changes and the code coverage has not dropped substantially
  • I have updated the documentation in all relevant places (Javadoc, Swagger, MDs...)

@sonarqubecloud

sonarqubecloud Bot commented Aug 3, 2026

Copy link
Copy Markdown

Quality Gate Failed Quality Gate failed

Failed conditions
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

@sonarqubecloud

sonarqubecloud Bot commented Aug 3, 2026

Copy link
Copy Markdown

@ondraholis ondraholis self-assigned this Aug 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant