Project

General

Profile

Actions
Copy link

Bug #5966

closed

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

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

Added by Benoît PECCATTE about 11 years ago. Updated about 4 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:
0
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 workflowNewActions

Updated by François ARMAND about 11 years ago Actions
Copy link
 #1

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.

Updated by François ARMAND about 11 years ago Actions
Copy link
 #2

  • 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

Updated by Janos Mattyasovszky over 9 years ago Actions
Copy link
 #3

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

Updated by Janos Mattyasovszky about 9 years ago Actions
Copy link
 #4

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 :-/

Updated by Jonathan CLARKE about 9 years ago Actions
Copy link
 #5

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

Updated by Jonathan CLARKE almost 9 years ago Actions
Copy link
 #6

  • Status changed from Discussion to New
  • Priority set to 0

Updated by Jonathan CLARKE almost 9 years ago Actions
Copy link
 #7

  • Assignee deleted (François ARMAND)

Updated by Benoît PECCATTE over 8 years ago Actions
Copy link
 #8

  • 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.

Updated by Benoît PECCATTE over 8 years ago Actions
Copy link
 #9

  • Priority changed from 14 to 27

Updated by François ARMAND over 7 years ago Actions
Copy link
 #10

  • 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

Updated by François ARMAND over 6 years ago Actions
Copy link
 #11

  • Assignee set to Elaad FURREEDAN
  • Target version changed from Ideas (not version specific) to 5.0.15
  • Effort required set to Very Small

Updated by Vincent MEMBRÉ over 6 years ago Actions
Copy link
 #12

  • Target version changed from 5.0.15 to 5.0.16

Updated by Alexis Mousset about 6 years ago Actions
Copy link
 #13

  • Target version changed from 5.0.16 to 5.0.17

Updated by Vincent MEMBRÉ almost 6 years ago Actions
Copy link
 #14

  • Target version changed from 5.0.17 to 5.0.18

Updated by Vincent MEMBRÉ over 5 years ago Actions
Copy link
 #15

  • Target version changed from 5.0.18 to 5.0.19

Updated by Vincent MEMBRÉ over 5 years ago Actions
Copy link
 #16

  • Target version changed from 5.0.19 to 5.0.20

Updated by Vincent MEMBRÉ over 5 years ago Actions
Copy link
 #17

  • Target version changed from 5.0.20 to 797

Updated by Benoît PECCATTE over 4 years ago Actions
Copy link
 #18

  • Target version changed from 797 to 6.1.14

Updated by Vincent MEMBRÉ over 4 years ago Actions
Copy link
 #19

  • Target version changed from 6.1.14 to 6.1.15

Updated by Vincent MEMBRÉ over 4 years ago Actions
Copy link
 #20

  • Target version changed from 6.1.15 to 6.1.16

Updated by Vincent MEMBRÉ over 4 years ago Actions
Copy link
 #21

  • Target version changed from 6.1.16 to 6.1.17

Updated by Vincent MEMBRÉ over 4 years ago Actions
Copy link
 #22

  • Target version changed from 6.1.17 to 6.1.18

Updated by Vincent MEMBRÉ about 4 years ago Actions
Copy link
 #23

  • Target version changed from 6.1.18 to 6.1.19

Updated by François ARMAND about 4 years ago Actions
Copy link
 #24

  • Status changed from New to Resolved

There is now a confirmation message.

Actions
Copy link

Also available in: PDF Atom