Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add IncidentIdIn filter to HistoricProcessInstanceQuery #4587

Open
1 task
Tracked by #4586
venetrius opened this issue Sep 6, 2024 · 0 comments
Open
1 task
Tracked by #4586

Add IncidentIdIn filter to HistoricProcessInstanceQuery #4587

venetrius opened this issue Sep 6, 2024 · 0 comments
Assignees
Labels
type:subtask Issues that are subtasks of another issue. Must always be part of the breakdown of the parent issue. version:7.22.0

Comments

@venetrius
Copy link
Member

venetrius commented Sep 6, 2024

Acceptance Criteria (Required on creation)

Hints

Java API

add a new method incidentIdIn(String... incidentIds); to the HistoricProcessInstanceQuery API
add a new field incidentIds with setter /getter to HistoricProcessInstanceQueryDto(impl)

SQL

incidentId is available in ACT_HI_INCIDENT the logic to join ACT_HI_INCIDENT is already present in HistoricProcessInstanceQuery and only needed to be updated with a check on the new field.

Links

parent ticket

Breakdown

Pull Requests

  1. ci:all-db ci:default-build ci:rest-api
    venetrius
@venetrius venetrius added the type:subtask Issues that are subtasks of another issue. Must always be part of the breakdown of the parent issue. label Sep 6, 2024
@venetrius venetrius self-assigned this Sep 6, 2024
@venetrius venetrius assigned yanavasileva and unassigned venetrius Sep 18, 2024
@tasso94 tasso94 assigned tasso94 and venetrius and unassigned yanavasileva and tasso94 Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:subtask Issues that are subtasks of another issue. Must always be part of the breakdown of the parent issue. version:7.22.0
Projects
None yet
Development

No branches or pull requests

3 participants