Defect #16299

Custom Issue field is not saved while issue is created

Added by Grzegorz Kuligowski over 7 years ago. Updated about 6 years ago.

Status:Needs feedbackStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Resolution:Cant reproduce Affected version:2.4.3

Description

Steps to reproduce:
- Add custom field in "Issue" section (Administration->Custom Fields->Issues->New Custom Field). Assign this custom field to some project, for example "TestPr"
- Go to "TestPr", click "New issue"
- Fill the issue, fill created custom field
- Click "Create"

Expected outcome:

The custom field has value equal to the filled one

Percieved outcome:

The custom field has no value (it is empty)

Additional information:

After issue is created I can click "update" and then I can edit and save this custom field without any problems.

Environment:
Redmine version 2.4.3.stable
Ruby version 2.0.0-p353 (2013-11-22) [x86_64-linux]
Rails version 3.2.16
Environment development
Database adapter Mysql2


Related issues

Related to Redmine - Defect #12377: Custom (issue) fields are not saved on new issue New

History

#1 Updated by Grzegorz Kuligowski over 7 years ago

I'm sorry, I have forgotten to fill-in affected version 2.4.3. No I cannot edit this field :(.

#2 Updated by Jean-Philippe Lang over 7 years ago

  • Status changed from New to Needs feedback
  • Resolution set to Cant reproduce

It just works for me, do you have any plugins installed?

#3 Updated by Toshi MARUYAMA over 7 years ago

  • Affected version set to 2.4.3

#4 Updated by Michal Kowalski about 6 years ago

Problem still exists.

#5 Updated by Toshi MARUYAMA about 6 years ago

  • Related to Defect #12377: Custom (issue) fields are not saved on new issue added

Also available in: Atom PDF