Project

General

Profile

Actions

Bug #14288

closed

Deleted techniques still visible in Directives library

Added by Krzysztof Pogłodziński over 5 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
N/A
Assignee:
-
Category:
Web - Technique editor
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Small
Priority:
40
Name check:
Fix check:
Regression:

Description

Steps to reproduce:
1. Create custom technique
2. Save it
3. Delete that technique
4. Goto "Configuration Policy -> Directives"

Result:
Deleted technique is visible in "Directive library" tree.

Expected result:
If technique is not being used by any directive it should be deleted from "Directive library" during deletion from "Technique library".

Current workaround:
Delete unused technique from "Settings -> Active Tree".

Proposed solution:
Deletion of technique should trigger action: "Check if technique is being used by any directive - if not , delete technique from directive library".
To keep system coherent, deletion of last directive of technique should trigger action: "Check if technique still exist Technique library - if not , delete technique from directive library".

Actions #1

Updated by François ARMAND about 5 years ago

  • Translation missing: en.field_tag_list set to community

Sorry for the mmissed feedback I can't agree more with both your analysis and proposed decision process.

Actions #2

Updated by François ARMAND about 5 years ago

  • Target version set to 5.0.10
  • Effort required set to Small
  • Priority changed from 32 to 47
Actions #3

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.10 to 5.0.11
  • Priority changed from 47 to 46
Actions #4

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.11 to 5.0.12
Actions #5

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 5.0.12 to 5.0.13
  • Priority changed from 46 to 45
Actions #6

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 5.0.13 to 5.0.14
  • Priority changed from 45 to 44
Actions #7

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.14 to 5.0.15
  • Priority changed from 44 to 43
Actions #8

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.15 to 5.0.16
  • Priority changed from 43 to 41
Actions #9

Updated by Alexis Mousset over 4 years ago

  • Target version changed from 5.0.16 to 5.0.17
  • Priority changed from 41 to 40
Actions #10

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 5.0.17 to 5.0.18
Actions #11

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 5.0.18 to 5.0.19
Actions #12

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 5.0.19 to 5.0.20
Actions #13

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 5.0.20 to 797
Actions #14

Updated by Benoît PECCATTE almost 3 years ago

  • Target version changed from 797 to 6.1.14
Actions #15

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.14 to 6.1.15
Actions #16

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.15 to 6.1.16
Actions #17

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.16 to 6.1.17
Actions #18

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.17 to 6.1.18
Actions #19

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.18 to 6.1.19
Actions #20

Updated by François ARMAND over 2 years ago

  • Status changed from New to Resolved

This is now correctly handled (in 6.2 and above).

Actions

Also available in: Atom PDF