Add support for Issue (as in rietveld) and origin (as in CI/TS) related metadata associated to a task request

[GoogleCodeExporter]

In practice, it would be nice to have information about all the tasks that have 
been run for a specific issue, for example.

Right now the meta data associated to a TaskRequest are 'user', 'name' and 
that's it. It'd be good for management purpose to make this more extensible, 
where meta data like 'issue', 'patchset', 'type' (where it could be 'cq', 'ci', 
'ts' or 'manual'), etc. What needs to be decided is if this is implemented in a 
purely extensible model or we simply define all the metadata we care about 
upfront as TaskRequest properties. I think it's better to hard code these.

Original issue reported on code.google.com by maruel@chromium.org on 21 May 2014 at 1:31

[GoogleCodeExporter]

Renamed title to clarify since I don't think going full arbitrary is a good 
idea, it'd be a pain front the 'search' perspective.

Original comment by maruel@chromium.org on 21 May 2014 at 1:34

• Changed title: Add support for Issue (as in rietveld) and origin (as in CI/TS) related metadata associated to a task request

[GoogleCodeExporter]

Also add "project". This would include general umbrella project. An idea about 
the layout for this value is:

project = ndb.StringProperty(repeated=True)

then use:

project = 'google/chromium/layout'
task.project = ['google', 'google/chromium', 'google/chromium/layout']
so a user can search for broad project scope or more focused on, as long as the 
strings are somewhat standardized (or even maybe use a whitelist?)

Original comment by maruel@chromium.org on 25 Jul 2014 at 4:18

• Added labels: Usability

[GoogleCodeExporter]

Used a tag instead. Good enough for now.

Original comment by maruel@chromium.org on 17 Nov 2014 at 1:24

• Changed state: Fixed