Skip to content

Redirect to consumer group page after offset reset #1099

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

Open
2 tasks done
Gleb-Shipilov opened this issue May 26, 2025 · 0 comments
Open
2 tasks done

Redirect to consumer group page after offset reset #1099

Gleb-Shipilov opened this issue May 26, 2025 · 0 comments
Labels
area/ux User experiense issues status/triage/completed Automatic triage completed status/triage/manual Manual triage in progress type/enhancement En enhancement/improvement to an already existing feature

Comments

@Gleb-Shipilov
Copy link

Issue submitter TODO list

  • I've searched for an already existing issues here
  • I'm running a supported version of the application which is listed here and the feature is not present there

Is your proposal related to a problem?

No response

Describe the feature you're interested in

Prerequisites
When a user resets consumer group offsets, the user is being redirected to the list of all consumer groups.

I, as a Kafka UI user, want to be redirected back to the consumer group page after resetting offsets for a topic, so I can reset offsets for other topics.

To do
After resetting consumer group offsets for a topic redirect back to the page of the consumer group

Acceptance criteria
Scenario 1: Successful redirection to the specific consumer group page after resetting offsets for a topic.

Given

A Kafka UI user is viewing the details of a specific consumer group.
The user initiates the action to reset offsets for one topic within that consumer group.
The offset reset operation for that topic completes successfully.

When

The offset reset operation for the specified topic finishes.

Then

The user MUST be redirected back to the page of the specific consumer group they were previously viewing (i.e., not to the list of all consumer groups).
The consumer group page MUST display the updated offset information for the topic(s) affected by the reset.
The user SHOULD see a confirmation message indicating the successful offset reset (e.g., "Offsets reset for topic [Topic Name]").

Scenario 2: Error handling during offset reset does not disrupt redirection behavior.

Given

A Kafka UI user is viewing the details of a specific consumer group.
The user initiates the action to reset offsets for one topic within that consumer group.
The offset reset operation for that topic encounters an error (e.g., Kafka connection issue, invalid parameters).

When

The offset reset operation for the specified topic fails.

Then

The user MUST be redirected back to the page of the specific consumer group they were previously viewing.
The user MUST see an error message clearly explaining that the offset reset failed for the topic (e.g., "Failed to reset offsets for topic [Topic Name]: [Error Details]").
The consumer group page MUST display the current, un-reset offset information for the topic.

Describe alternatives you've considered

No response

Version you're running

1.2.0

Additional context

No response

@Gleb-Shipilov Gleb-Shipilov added status/triage Issues pending maintainers triage type/feature A brand new feature labels May 26, 2025
@kapybro kapybro bot added status/triage/manual Manual triage in progress status/triage/completed Automatic triage completed and removed status/triage Issues pending maintainers triage labels May 26, 2025
@Haarolean Haarolean added type/enhancement En enhancement/improvement to an already existing feature area/ux User experiense issues and removed type/feature A brand new feature labels May 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ux User experiense issues status/triage/completed Automatic triage completed status/triage/manual Manual triage in progress type/enhancement En enhancement/improvement to an already existing feature
Projects
None yet
Development

No branches or pull requests

2 participants