We could set up a Discovery-ops-sprint project/workboard. Then you could have columns for backlog, in progress, in review, done, etc.
Otherwise, you can just do the same thing within the search sprint, but your tasks will be mixed in with the other search work. No other methods come to mind. Kevin Smith Agile Coach, Wikimedia Foundation On Thu, Mar 10, 2016 at 2:50 AM, Guillaume Lederrey <[email protected] > wrote: > I should probably be able to give visibility on what I'm doing (and > what I'm planning to do) not in emails, but directly in Phabricator. > I'm not sure on how to do that. Any idea? Do you need that visibility? > > On Thu, Mar 10, 2016 at 6:23 AM, Dan Garry <[email protected]> wrote: > > On 9 March 2016 at 17:53, Dan Garry <[email protected]> wrote: > >> > >> I may drop a task your way in a day or two to investigate some possible > >> performance regression. You may need to pair with a non-ops engineer to > >> investigate it fully, I don't know. More details will be in the ticket > when > >> I get around to filing it. :-) > > > > > > As promised: T129441 > > > > Thanks again! > > > > Dan > > > > -- > > Dan Garry > > Lead Product Manager, Discovery > > Wikimedia Foundation > > > > _______________________________________________ > > discovery mailing list > > [email protected] > > https://lists.wikimedia.org/mailman/listinfo/discovery > > > > _______________________________________________ > discovery mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/discovery >
_______________________________________________ discovery mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/discovery
