Project

General

Profile

Actions

Bug #2128

closed

xmera Omnia - Collection #2125: Bug Fixing: Project Types, Tables

Integrating sheets into an existing project may complain that the sheet already exist even if not

Added by liaham about 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Affected Version:
Compatible Redmine Version:

Description

I observed that the validation about unique data sheet names fails even if there is no table for a given project.

This needs to be reproduced by the following steps:

  1. Create a table.
  2. Create a project type.
  3. Create a project based on that type.
  4. Create a datasheet in the newly created project type.
  5. Add content to the datasheet.
  6. Navigate into the table module of the project.
  7. Fetch the datasheet.

Related issues 1 (0 open1 closed)

Related to Redmine Table Calculation - Improvement #1855: Validate project_id more explicitlyClosedliaham

Actions
Actions #1

Updated by liaham about 1 year ago

  • Status changed from New to Closed
  • Assignee set to liaham
  • Parent task set to #2125

During the copy process some attributes including project_id were lost what leads to saving a spreadsheet without project id. If that was happened the uniqueness requirement failed afterwards.

This is solved by requiring the project id to avoid such 'blocking' table entries without project is.

Actions #2

Updated by liaham about 1 year ago

Actions #3

Updated by liaham about 1 year ago

  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF