Page MenuHomePhabricator

Maniphest custom field refuses to use non-empty default value
Closed, ResolvedPublic

Description

We have a custom field defined like this:

"ushahidi:task-type" : {
  "name"    : "Task Type",
  "type"    : "select",
  "copy"    : true,
  "search"  : true,
  "default" : "bug",
  "options" : {
    ""          : "None",
    "bug"       : "Bug",
    "feature"   : "Feature",
    "design"    : "Design/UI",
    "faq"       : "Question",
    "doc"       : "Documentation",
    "milestone" : "Milestone"
  }
},

But when I create a new task without changing the Task Type field, no Task Type appears, even though the default is "Bug".

Event Timeline

shadowhand raised the priority of this task from to Needs Triage.
shadowhand updated the task description. (Show Details)
shadowhand added a project: Maniphest.

getOldValueForApplicationTransactions() ends up returning the default value, so we no-op the transaction.

btrahan renamed this task from Manifest custom field refuses to use non-empty default value to Maniphest custom field refuses to use non-empty default value.May 22 2014, 6:11 PM

@btrahan good catch on the title. :)

I have like half a diff for this.

This no longer reproduces for me at HEAD in EditEngine (see T9905), although I can't immediately reproduce it in the old editor either. Since it seems like it got fixed somewhere I'm not going to worry about it too much.

Ah, I figured out how to reproduce this.