Bug #5966: Add a warning message to warn that rollback in change request mode doesn't create a change request - Rudder - Issue Tracker

Custom queries

8.1 beta
Bugs triage
CS - by priority
CS - to review
My TR
Need technical review
Open bugs (all)
Open bugs (UI - UX)
Open UX defects (all)
Opened by users

Actions

Copy link

Bug #5966

closed

Add a warning message to warn that rollback in change request mode doesn't create a change request

Added by Benoît PECCATTE almost 10 years ago. Updated almost 3 years ago.

Status:

Resolved

Priority:

N/A

Assignee:

Elaad FURREEDAN

Category:

Web - Config management

Target version:

6.1.19

Pull Request:

Severity:

Minor - inconvenience | misleading | easy workaround

UX impact:

User visibility:

Operational - other Techniques | Technique editor | Rudder settings

Effort required:

Very Small

Priority:

Name check:

Fix check:

Regression:

Description

This is surprising since it can be an important change.

Related issues 1 (1 open — 0 closed)

Related to Rudder - User story #7923: Combine multiple Change Requests into a bundled one in the Change- and Validation workflow

New

2016-02-15

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by François ARMAND almost 10 years ago

The rationnal behind that was: rollback are only available to Rudder admin, they are more likelly needed in urgency situation, so let just the admin do what he wants. So no change request.

Actions

Copy link

Updated by François ARMAND almost 10 years ago

Status changed from New to Discussion
Target version changed from 3.0.0~beta2 to Ideas (not version specific)

I will let it in discussion for now, but in any case, such a modification won't go in 3.0

Actions

Copy link

Updated by Janos Mattyasovszky about 8 years ago

Related to User story #7923: Combine multiple Change Requests into a bundled one in the Change- and Validation workflow added

Actions

Copy link

Updated by Janos Mattyasovszky almost 8 years ago

Is there a separate role on who can rollback a change?
I might not want to give complete admin priv's to someone just to rollback a change :-/

Actions

Copy link

Updated by Jonathan CLARKE over 7 years ago

Severity set to Major - prevents use of part of Rudder | no simple workaround

Actions

Copy link

Updated by Jonathan CLARKE over 7 years ago

Status changed from Discussion to New
Priority set to 0

Actions

Copy link

Updated by Jonathan CLARKE over 7 years ago

Assignee deleted (~~François ARMAND~~)

Actions

Copy link

Updated by Benoît PECCATTE over 7 years ago

Severity changed from Major - prevents use of part of Rudder | no simple workaround to Minor - inconvenience | misleading | easy workaround
User visibility set to Operational - other Techniques | Technique editor | Rudder settings
Priority changed from 0 to 14

This is the expected behaviour.
We should add a warning in the application to make sure the user doing this understands what will happen before clicking OK.

Actions

Copy link

Updated by Benoît PECCATTE over 7 years ago

Priority changed from 14 to 27

Actions

Copy link

#10

Updated by François ARMAND about 6 years ago

Subject changed from Rollback in change request mode doesn't create a change request to Add a warning message to warn that rollback in change request mode doesn't create a change request
Priority changed from 27 to 0