Page MenuHomePhabricator

Object creation is often accompanied by transaction records which aren't of much use
Closed, ResolvedPublic

Description

Creating a task doesn't set the value to the default in a custom field. When anything in the task is changed the default value is set as normal. This results in history looking like this:
User created this task.
User added a subscriber: User.

and after some time

User edited the task description. (Show Details)
User set Custom Field to Default.

Event Timeline

jdloft updated the task description. (Show Details)Mar 25 2015, 5:34 PM
jdloft added projects: Custom Fields, Maniphest.
jdloft added a subscriber: jdloft.
jdloft created this task.
jdloft raised the priority of this task from to Needs Triage.
qgil added a comment.Mar 26 2015, 8:59 AM

Ah, now I see that @jdloft here and Negative24 in Wikimedia might be the same user. :)

Yea. Maybe I should explicitly say that somewhere to avoid confusion. :)

qgil added a comment.Mar 26 2015, 2:21 PM

I don't think the "without a description" part is correct. I think just creating a normal task with a normal description is enough to seed the problem. The custom field value is not set at creation, but only when someone edits the task (even without touching the custom field at all).

That is correct (reproduced with https://phab-02.wmflabs.org/T17). Updating the task...

jdloft updated the task description. (Show Details)Mar 26 2015, 3:23 PM
jdloft renamed this task from Custom field default isn't populated until description is set to Custom field default isn't populated at creation.
qgil added a comment.Mar 27 2015, 12:20 PM

This new bug sounds like a different manifestation of the same problem: https://phabricator.wikimedia.org/T94155

scfc added a subscriber: scfc.Jun 26 2015, 2:16 PM

I'm experiencing something a little different using a custom select field.

If I create a task, via UI or conduit, without explicitly setting the custom field, it appears to be set to NULL instead of the default value. This is based on the fact that the custom field is not displayed in the web UI for the task.

Later if I edit the task, the custom field's dropdown box is populated with the first option, instead of the default (which is actually the last item specified in the custom field definition).

epriestley moved this task from Backlog to vNext on the Maniphest board.Dec 4 2015, 7:10 PM
epriestley renamed this task from Custom field default isn't populated at creation to Object creation is often accompanied by transaction records which aren't of much use.

This is related to T5158, I'm going to split things up like this:

  • Transaction record having not-useful records: this task.
  • Actual values not getting set properly: T5158