Page MenuHomePhabricator

Allowing custom fields to be passed in over get for new tasks
Needs RevisionPublic

Authored by bluehawk on Jul 22 2014, 11:21 PM.
Tags
None
Referenced Files
F12851963: D10025.id24113.diff
Fri, Mar 29, 6:59 AM
Unknown Object (File)
Sat, Mar 16, 6:16 AM
Unknown Object (File)
Feb 7 2024, 2:50 PM
Unknown Object (File)
Feb 3 2024, 12:09 AM
Unknown Object (File)
Jan 9 2024, 12:24 PM
Unknown Object (File)
Dec 28 2023, 5:33 PM
Unknown Object (File)
Dec 26 2023, 10:17 AM
Unknown Object (File)
Dec 20 2023, 2:38 PM

Details

Reviewers
epriestley
Group Reviewers
Blessed Reviewers
Summary

Pass in custom fields to tasks in the url e.g. &custom:field=blah

Test Plan

Try creating a task by going to a url and put some custom fields in the url

Diff Detail

Repository
rP Phabricator
Branch
custom-field-url
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 1865
Build 1866: [Placeholder Plan] Wait for 30 Seconds

Event Timeline

bluehawk retitled this revision from to Allowing custom fields to be passed in over get for new tasks.
bluehawk updated this object.
bluehawk edited the test plan for this revision. (Show Details)
bluehawk added a reviewer: epriestley.

Okay just kidding, this is very bad.

When you edit a task, it sets all custom fields to blank. (Because it's not a post, it tries to read it from the request, but the request has no data). I'll investigate a fix shortly.

bluehawk edited edge metadata.

Fix so that custom fields don't show up empty when editing

epriestley edited edge metadata.

The upstream path for this lies beyond T9132.

This revision now requires changes to proceed.Nov 2 2015, 4:51 PM