Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Blank Location vs. Default Location

Description

If you create a new node in the Provisioning Requisitions section, using some arbitrary value for the Location, and then, later on, decide to try to switch it over to the Default location by clearing that Location field and re-synchronizing, you end up with a new "blank" named location in the database.

Attempting to delete that location seems to also delete the Default location, and all nodes attached to it.

Environment

CentOS Linux release 7.3.1611 (Core)

Acceptance / Success Criteria

None

Attachments

1
  • 23 Feb 2017, 05:52 PM

Lucidchart Diagrams

Activity

Show:

Mark Mahacek March 23, 2017 at 4:35 PM

I was hit by this bug. Deleting the blank location deleted all my locations, not just the Default.
Suggestion - make the Location field in the requisition editor a drop down.

Christian Pape March 2, 2017 at 7:17 AM

Seth Leger February 23, 2017 at 5:52 PM

The blank location ends up being persisted to the database and shows up in the location list.

Fixed

Details

Assignee

Reporter

Components

Sprint

Fix versions

Affects versions

Priority

PagerDuty

Created February 23, 2017 at 5:31 PM
Updated March 23, 2017 at 4:35 PM
Resolved March 9, 2017 at 3:21 PM

Flag notifications