Ticket #7569 (closed: worksforme)

Opened 7 years ago

Last modified 5 years ago

Renaming workspaces not delete previous workspace

Reported by: Jay Rainey Owned by: Nick Draper
Priority: major Milestone: Release 3.2
Component: Framework Keywords:
Cc: Blocked By:
Blocking: Tester: Karl Palmen

Description

When a workspace within a group workspace is renamed the same as another workspace in that group it is overridden. However, it does not delete the previous workspace that was overridden.

To replicate this:

  1. Load a .raw file (E.g. CSP79590.raw).
  2. Plot spectrum.
  3. Rename both sub-workspaces the same.
  4. Plot spectrum (proves that the workspace was overridden).
  5. Two sub-workspaces exist (So the one overridden was not deleted).

Change History

comment:1 Changed 7 years ago by Jay Rainey

  • Owner set to Anyone
  • Summary changed from Renaming to Renaming workspaces not delete previous workspace

comment:2 Changed 7 years ago by Nick Draper

  • Status changed from new to assigned

Bulk move to assigned at the introduction of the triage step

comment:3 Changed 6 years ago by Nick Draper

  • Status changed from assigned to verify
  • Owner changed from Anyone to Nick Draper
  • Resolution set to worksforme
  • Milestone changed from Backlog to Release 3.2

This has been resolved and the example above does not shoe the problem in R3.2

comment:4 Changed 6 years ago by Karl Palmen

  • Status changed from verify to verifying
  • Tester set to Karl Palmen

comment:5 Changed 6 years ago by Karl Palmen

  • Status changed from verifying to closed

I find that after renaming two workspaces in the group the same, both instances remain present in the workspaces window, but seem to refer to the same workspace, because when I crop one of them I don't have the choice of which one to crop and then find both instances are cropped.

I take the existence of two instances in the workspaces window to be a separate issue.

comment:6 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​8414

Note: See TracTickets for help on using tickets.