| *** alexismonville has joined #storyboard | 00:34 | |
| *** alexismonville has quit IRC | 00:35 | |
| *** alexismonville has joined #storyboard | 00:50 | |
| SotK | zara_the_lemur__: the issue with the tasks thing is that it needs a q parameter in order to return any results I think | 00:53 |
|---|---|---|
| SotK | which is fine by me for now since if one doesn't want to set a q parameter the browse endpoint can be used | 00:53 |
| SotK | (that is what the webclient does, only uses /v1/tasks/search if a q parameter is needed) | 00:54 |
| zara_the_lemur__ | okay, in that case I think that bit just needs to be commented so that it's obvious that's what's going on | 01:02 |
| zara_the_lemur__ | since I read it as 'q or filters' , which actually thinking about it makes no sense, but I would assume someone else reading might be as distracted as me. | 01:04 |
| zara_the_lemur__ | (because yeah, browse is a thing) | 01:04 |
| *** alexismonville has quit IRC | 01:13 | |
| *** chatter has joined #storyboard | 02:55 | |
| *** chatter has quit IRC | 02:56 | |
| *** zara_the_lemur__ has quit IRC | 03:35 | |
| *** dhellmann has quit IRC | 05:39 | |
| *** dhellmann has joined #storyboard | 05:39 | |
| *** fay_ has joined #storyboard | 08:14 | |
| *** openstackgerrit has quit IRC | 10:18 | |
| Zara | not-quite-morning, storyboard! | 12:14 |
| *** alexismonville has joined #storyboard | 12:18 | |
| Zara | tristanC: I tried to look at one of your patches yesterday and discovered in the process that there's some network weirdness on my end and I can't test anything notifications-related at the moment. I can probably sort something out but it could take a while, so I'm wondering if you have anyone around who's likely to be able to try those patches out and check notifications behave as expected? | 12:20 |
| SotK | morningish | 12:20 |
| *** alexismonville has quit IRC | 12:23 | |
| * SotK can try out tristanC's patch later if you like | 12:41 | |
| Zara | that'd be good if possible | 12:51 |
| Zara | it looks fine; I'm just wary around notifications things | 12:52 |
| *** fay_ has quit IRC | 14:10 | |
| *** fay_ has joined #storyboard | 14:12 | |
| *** alexismonville has joined #storyboard | 16:09 | |
| *** diablo_rojo has joined #storyboard | 16:10 | |
| *** alexismonville has quit IRC | 16:22 | |
| *** diablo_rojo has quit IRC | 17:04 | |
| *** alexismonville has joined #storyboard | 17:12 | |
| *** alexismonville has quit IRC | 17:29 | |
| *** alexismonville has joined #storyboard | 17:29 | |
| *** diablo_rojo has joined #storyboard | 17:42 | |
| *** alexismonville has quit IRC | 18:34 | |
| *** prometheanfire has joined #storyboard | 18:37 | |
| prometheanfire | odyssey4me: what are you doing here? | 18:37 |
| *** zara_the_lemur__ has joined #storyboard | 18:37 | |
| prometheanfire | can storyboard do deps between tasks/stories? | 18:44 |
| zara_the_lemur__ | there's nothing automated; it doesn't record anything internally along the lines of 'this task depends on that task' or 'this story depends on that story'. users can note dependencies in the story description (or in the 'task notes' field for tasks) | 18:47 |
| zara_the_lemur__ | or could put stories in dependency order in a worklist or something like that, though I've never used them that way (myself) | 18:48 |
| prometheanfire | thanks | 18:48 |
| zara_the_lemur__ | prometheanfire: I think there are historical reasons why it was avoided, so if that's interesting to you it could be worth talking to ttx (I think) for some context around that | 18:51 |
| prometheanfire | we were looking at something along those lines for the requirements project | 18:52 |
| prometheanfire | I know bugzi can do it, but not many people like that :P | 18:52 |
| zara_the_lemur__ | heh :) I've heard mixed things about the feature itself (from 'this would be really useful' to 'that is far more complicated to implement than it is useful' to 'if you're managing a task actively enough you don't need it') | 18:56 |
| *** diablo_rojo has quit IRC | 18:57 | |
| *** openstackgerrit has joined #storyboard | 18:57 | |
| openstackgerrit | Merged openstack-infra/storyboard: Add filters to the /v1/tasks/search endpoint https://review.openstack.org/390983 | 18:57 |
| zara_the_lemur__ | so I'm generally interested in the use-cases to work out if it's people disagreeing about the same case, or if the usefulness varies from case to case/person to person | 19:01 |
| prometheanfire | that's ever the question, being too flexible makes being usable harder much of the time | 19:05 |
| zara_the_lemur__ | yyyyyyyep :D so I figure if at least we know who needs what why, we can tailor it to the users instead of trying to cover all bases | 19:10 |
| *** diablo_rojo has joined #storyboard | 19:27 | |
| *** diablo_rojo has quit IRC | 22:16 | |
| *** jeblair has joined #storyboard | 22:31 | |
| jeblair | Zara: what do you think of worklists including the story name when a card is for a task? | 22:31 |
| jeblair | Zara: (we have some tasks where they make more sense in the context of a story -- eg "write localrc" makes more sence if it is in context: "devstack-gate roles refactoring: write localrc") | 22:32 |
| SotK | the only issue I have with doing that is the potential for card titles to get really long | 22:43 |
| zara_the_lemur__ | yeah, and I think there's a task somewhere for making it clear that tasks are part of the same story, but we were never sure of the best way to represent it. so I like the idea of making context more findable, wondering what the best implementation would be (we might want to do it differently for worklists and lanes in boards) | 23:39 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!