Defect #12377
Custom (issue) fields are not saved on new issue
| Status: | New | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Custom fields | |||
| Target version: | - | |||
| 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
History
#1
Updated by Etienne Massip over 9 years ago
how is defined your custom field?
#2
Updated by Jean-Philippe Lang over 9 years ago
- Resolution set to Cant reproduce
#3
Updated by Philipp Schüttlöffel over 9 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.
#4
Updated by Michal Kowalski almost 7 years ago
Confirming this.
#5
Updated by Toshi MARUYAMA almost 7 years ago
- Related to Defect #16299: Custom Issue field is not saved while issue is created added