Project

General

Profile

Actions
Copy link

Defect #12377

open

Custom (issue) fields are not saved on new issue

Added by Philipp Schüttlöffel over 11 years ago. Updated almost 9 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Custom fields
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Cant reproduce
Affected version:
2.0.2

Description

When creating a new issue, the values of custom fields are not saved. When editing an issue, the values are saved.

Environment:
Redmine version 2.0.2.stable
Ruby version 1.8.7 (x86_64-linux)
Rails version 3.2.5
Environment production
Database adapter MySQL
Redmine plugins:
redmine_lightbox 0.0.1

Related issues

Related to Redmine - Defect #16299: Custom Issue field is not saved while issue is createdNeeds feedback

Actions
Actions
Copy link
 #1

Updated by Etienne Massip over 11 years ago

how is defined your custom field?

Actions
Copy link
 #2

Updated by Jean-Philippe Lang over 11 years ago

  • Resolution set to Cant reproduce
Actions
Copy link
 #3

Updated by Philipp Schüttlöffel over 11 years ago

Type: issue
Format: text
Length: 5-7
Reg-Expr: [0-9]{5,7}
It got 2 trackers and is required, for all projects, used as filter and searchable.

Actions
Copy link
 #4

Updated by Michal Kowalski almost 9 years ago

Confirming this.

Actions
Copy link
 #5

Updated by Toshi MARUYAMA over 8 years ago

  • Related to Defect #16299: Custom Issue field is not saved while issue is created added
Actions
Copy link

Also available in: Atom PDF