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

Create new endpoint to return Listener jobs list for a selected node #18549

Open
6 tasks
Tracked by #18026
vitorwtavares opened this issue May 15, 2024 · 0 comments
Open
6 tasks
Tracked by #18026
Assignees
Labels
component/operate Related to the Operate component/team kind/task Categorizes an issue as a breakdown of low-level implementation detail from a parent issue

Comments

@vitorwtavares
Copy link
Contributor

vitorwtavares commented May 15, 2024

Description

This issue is part of #18026 Listener Visibility in Operate epic.

Create a new endpoint to be consumed by the frontend that will return the list of Listeners in any given flow node.

Endpoint name: /api/process-instances/:instanceId/listeners
Payload received:

{
  pageSize: Int
  flowNodeId: String
}

Expected return:

{
  listenerType
  listenerKey
  state
  jobType
  event
  time
}

TODO

Additional Information

  • time property should be the end time.
  • Results should be returned sorted by the time property in chronological order. This is important because for right now there will not be any sorting functionally on the frontend.
  • Epic link: 🎯 Listener Visibility in Operate #18026

Acceptance Criteria

  • Checked if the specific data needs to be provided for the QA process

Definition of Ready - Checklist

  • The issue has a meaningful title, description and testable acceptance criteria
  • If documentation needs to be updated, an issue is created in the camunda-docs repo, and the issue is added to our Operate project board.
  • If HELM charts need to be updated, an issue is created in the camunda-platform-heml repo, and the issue is added to our Operate project board.
  • Potential Security risks have been considered
  • Cross-team dependencies have been considered
@vitorwtavares vitorwtavares added kind/task Categorizes an issue as a breakdown of low-level implementation detail from a parent issue component/operate Related to the Operate component/team labels May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/operate Related to the Operate component/team kind/task Categorizes an issue as a breakdown of low-level implementation detail from a parent issue
Projects
None yet
Development

No branches or pull requests

2 participants