Project

General

Profile

Actions

Bug #21295

open

When files from a deleted technique are still on fs, creation of technique with same name is impossible

Added by François ARMAND over 2 years ago. Updated 5 months ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Web - Technique editor
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
I dislike using that feature
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
63
Name check:
To do
Fix check:
To do
Regression:

Description

If a technique deletion went wrong and some of its files are still present in the file system, then a technique with the same name (derived id actually) can't be created.
This is extremely disturbing because the user doesn't have any lever about what to do to correct the problem, or what the pb is actually: from his PoV, everything is fine:

This is related to #21119

The expected behavior would be that Rudder automatically check if the technique really exists for real, and if not (ie if we are observing remaining of an old technique badly deleted), rudder should clean things up and save the new technique.
A minima, Rudder should tell the user how he could achieve his action.


Files

clipboard-202206201537-bynmd.png (55.9 KB) clipboard-202206201537-bynmd.png François ARMAND, 2022-06-20 15:37

Related issues 1 (0 open1 closed)

Related to Rudder - Bug #21119: When a technique is not in the active techique tree, it can't be deleted in editorReleasedElaad FURREEDANActions
Actions #1

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.2.15 to 6.2.16
Actions #2

Updated by François ARMAND over 2 years ago

  • Related to Bug #21119: When a technique is not in the active techique tree, it can't be deleted in editor added
Actions #3

Updated by Alexis Mousset over 2 years ago

  • Target version changed from 6.2.16 to 6.2.17
  • Priority changed from 52 to 51
Actions #4

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 6.2.17 to 997
  • Priority changed from 51 to 74
Actions #5

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 997 to 6.2.18
Actions #6

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 6.2.18 to 6.2.19
Actions #7

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 6.2.19 to 6.2.20
Actions #8

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 6.2.20 to old 6.2 issues to relocate
  • Priority changed from 74 to 72
Actions #9

Updated by Alexis Mousset over 1 year ago

  • Target version changed from old 6.2 issues to relocate to 7.2.10
  • Priority changed from 72 to 63
Actions #10

Updated by Alexis Mousset over 1 year ago

  • Target version changed from 7.2.10 to 7.2.11
Actions #11

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 7.2.11 to 1046
Actions #12

Updated by Alexis Mousset about 1 year ago

  • Target version changed from 1046 to 7.3.8
Actions #13

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 7.3.8 to 7.3.9
Actions #14

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 7.3.9 to 7.3.10
Actions #15

Updated by Vincent MEMBRÉ 12 months ago

  • Target version changed from 7.3.10 to 7.3.11
Actions #16

Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 7.3.11 to 7.3.12
Actions #17

Updated by Vincent MEMBRÉ 9 months ago

  • Target version changed from 7.3.12 to 7.3.13
Actions #18

Updated by Vincent MEMBRÉ 9 months ago

  • Target version changed from 7.3.13 to 7.3.14
Actions #19

Updated by Vincent MEMBRÉ 7 months ago

  • Target version changed from 7.3.14 to 7.3.15
Actions #20

Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 7.3.15 to 7.3.16
Actions #21

Updated by Vincent MEMBRÉ 5 months ago

  • Target version changed from 7.3.16 to 7.3.17
Actions

Also available in: Atom PDF