Project

General

Profile

Actions

Bug #1676

closed

Trying to disable or delete a PI after creation is not taken into account

Added by François ARMAND over 13 years ago. Updated over 12 years ago.

Status:
Released
Priority:
3
Assignee:
Jean VILVER
Category:
Web - Config management
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

If one creates a policy instance, update its form and save, close the success pop-up and then try to disable or delete it, there is a success pop-up but the action is not taken into account.

If the newly created PI is loaded back with a click on it from the tree, delete/disable work again.


Related issues 1 (0 open1 closed)

Has duplicate Rudder - Bug #2529: No event log when a Directive is disabledRejectedFrançois ARMAND2012-06-05Actions
Actions #1

Updated by Jonathan CLARKE over 13 years ago

  • Target version changed from 20 to 19
Actions #2

Updated by Jonathan CLARKE over 13 years ago

  • Target version changed from 19 to 21
Actions #3

Updated by Jonathan CLARKE over 13 years ago

  • Target version changed from 21 to 23
Actions #4

Updated by Jonathan CLARKE over 13 years ago

  • Category set to 9
  • Priority changed from 2 to 4

This is a rare case, with a simple workaround, downgrading priority

Actions #5

Updated by Jonathan CLARKE about 13 years ago

  • Target version changed from 23 to 2.3.0
Actions #6

Updated by Jonathan CLARKE about 13 years ago

  • Assignee set to François ARMAND
Actions #7

Updated by François ARMAND about 13 years ago

  • Target version changed from 2.3.0 to 18
Actions #8

Updated by François ARMAND about 13 years ago

  • Target version changed from 18 to 2.4.0~alpha1
Actions #9

Updated by Jonathan CLARKE about 13 years ago

  • Target version changed from 2.4.0~alpha1 to 2.4.0~alpha2
Actions #10

Updated by Jonathan CLARKE almost 13 years ago

  • Target version changed from 2.4.0~alpha2 to 2.4.0~alpha3
Actions #11

Updated by Jonathan CLARKE almost 13 years ago

  • Target version changed from 2.4.0~alpha3 to 2.4.0~alpha4
Actions #12

Updated by François ARMAND almost 13 years ago

  • Target version changed from 2.4.0~alpha4 to 2.4.0~alpha5
Actions #13

Updated by Jonathan CLARKE almost 13 years ago

  • Target version changed from 2.4.0~alpha5 to 2.4.0~alpha6
Actions #14

Updated by Jonathan CLARKE over 12 years ago

  • Status changed from New to 2
  • Priority changed from 4 to 3
  • Target version changed from 2.4.0~alpha6 to 2.4.0~beta1
Actions #15

Updated by Jonathan CLARKE over 12 years ago

  • Target version changed from 2.4.0~beta1 to 2.4.0~beta2
Actions #16

Updated by François ARMAND over 12 years ago

  • Status changed from 2 to Discussion

This bug does not seems to be here anymore, perhaps due to #2632 correction.

Actions #17

Updated by François ARMAND over 12 years ago

Moreover, #2529 is also corrected, and an event log is done on disable.

Actions #18

Updated by Nicolas PERRON over 12 years ago

  • Target version changed from 2.4.0~beta2 to 2.4.0~beta3

2.4.0~beta2 has been released. This ticket must be moved to 2.4.0~beta3.

Actions #19

Updated by Jean VILVER over 12 years ago

  • Status changed from Discussion to In progress
  • Assignee changed from François ARMAND to Jean VILVER
Actions #20

Updated by Jean VILVER over 12 years ago

  • Status changed from In progress to Pending technical review

François ARMAND wrote:

This bug does not seems to be here anymore, perhaps due to #2632 correction.

Yeah I just tried, it's not. But If we reload the page we lost the directive selection in the tree. I'm creating a ticket for this behavior.

Actions #21

Updated by François ARMAND over 12 years ago

  • Status changed from Pending technical review to Released
Actions

Also available in: Atom PDF