Open Stack

Hi,

I've been investigating how we could track the repository and the branch
where a given task should land in Maniphest. This is a feature gap we
have compared to Launchpad, and being able to clearly track complex
stories with subtasks that affect different projects/branches is a key
requirement for OpenStack task tracking.

Ideally the targeted project/branch would appear in the subtask lists,
as well as be searchable.

In this episode, I looked into how we could leverage CustomFields to
achieve that. In particular, CustomFields have a renderOnListItem()
method which promised to give you a handle on how tasks are represented
in lists. However, I quickly realized that this method is actually never
called for ManiphestCustomFields, so a custom field can't affect how a
task appears in list views.

I then tried to see how we could alter the views so that the content of
a specific custom field of a task would appear in the displayed task
name, but that is non-trivial due to the way custom fields are hooked
into an object. The object itself basically can't directly access the
value of custom fields (Maniphest does it from the presentation layer),
which makes it rather difficult to display the value of a custom field
of a linked object (like the project/branch of a subtask). I'm still
investigating this, and I suspect it is possible, but I fear it will be
a heavy patch that we'd likely not carry (and that upstream is not
likely to accept).

Stay tuned for episode 2...

-- 
Thierry Carrez (ttx)