Page MenuHomePhabricator

phragile needs to switch to using the new maniphest.search method because the maniphest.points field is not exposed in maniphest.query results.
Closed, DuplicatePublic

Description

The maniphest.points field is not exposed through the old maniphest.query method. Phragile need to switch to using the new maniphest.search method instead of maniphest.query.

Event Timeline

Jakob_WMDE raised the priority of this task from to High.
Jakob_WMDE updated the task description. (Show Details)
Jakob_WMDE added a project: Phragile.
Restricted Application added a subscriber: Aklapper. · View Herald Transcript

See https://gerrit.wikimedia.org/r/#/c/270791/.

I modified the maniphest cónduit controller and added the points field to the TaskInfoDictionaries.

I forked the maniphest.query and maniphest,info methods and added them as sprint.query and sprint.info.

This is assumed to be a temporary measure until upstream does this officially.

It's exposed through maniphest.search. This post has some discussion and links about the modern endpoints:

https://secure.phabricator.com/phame/post/view/752/reading_and_writing_paths_in_owners/

See https://secure.phabricator.com/D15244 for the upstream implementation.

(The post discusses owners, but all the new *.search and *.edit endpoints expose the same APIs and work the same way.)

( I'm removing Phabricator from the project tags, as points are exposed according to T126982#2029910 )

mmodell renamed this task from Projects V3 does not expose maniphest.points through the API to phragile needs to switch to using the new maniphest.search method because the maniphest.points field is not exposed in maniphest.query results..Feb 29 2016, 2:22 AM
mmodell updated the task description. (Show Details)