| *** jamesmcarthur has joined #storyboard | 00:15 | |
| *** jamesmcarthur has quit IRC | 00:20 | |
| *** lifeless has quit IRC | 00:38 | |
| *** lifeless has joined #storyboard | 00:45 | |
| *** fatema_ has joined #storyboard | 01:50 | |
| *** fatema_ has quit IRC | 02:02 | |
| *** noama has joined #storyboard | 03:06 | |
| *** udesale has joined #storyboard | 03:50 | |
| *** noama has quit IRC | 03:50 | |
| *** noama has joined #storyboard | 04:44 | |
| *** udesale has quit IRC | 06:54 | |
| *** udesale has joined #storyboard | 06:55 | |
| *** udesale has quit IRC | 06:59 | |
| *** udesale has joined #storyboard | 07:00 | |
| *** tosky has joined #storyboard | 07:40 | |
| *** noama has quit IRC | 07:53 | |
| *** jpich has joined #storyboard | 08:02 | |
| *** dtantsur|afk is now known as dtantsur | 08:22 | |
| *** jamesmcarthur has joined #storyboard | 08:55 | |
| *** jamesmcarthur has quit IRC | 09:00 | |
| *** udesale has quit IRC | 11:24 | |
| *** dtantsur is now known as dtantsur|brb | 12:06 | |
| *** ttx has quit IRC | 12:09 | |
| *** ttx has joined #storyboard | 12:23 | |
| *** dtantsur|brb is now known as dtantsur | 13:35 | |
| *** udesale has joined #storyboard | 14:04 | |
| *** jamesmcarthur has joined #storyboard | 14:24 | |
| *** jamesmcarthur has quit IRC | 14:27 | |
| *** jamesmcarthur has joined #storyboard | 14:27 | |
| *** edleafe has joined #storyboard | 14:29 | |
| *** cdent has joined #storyboard | 14:32 | |
| cdent | once a project is set up to use-storyboard and a review indicates a Story: (as in https://review.openstack.org/#/c/578369/ ) is there some expected change in the related story | 14:33 |
|---|---|---|
| cdent | what should we see (if anything) and how do we figure out what went wrong if something was supposed to show up? | 14:33 |
| tosky | cdent: you need to add both Story: <nnnn> and Task: <nnnn> if you want to see a change in a task | 14:35 |
| tosky | if just add Story: is like Related-Bug; Story+Task is Closes-Bug | 14:36 |
| tosky | but not a bug, but a task inside the story | 14:36 |
| cdent | ah, right on, thanks tosky | 14:36 |
| cdent | I think my confusion is rooted in the fact that a launchpad bug comes over as a story with what amounts to a null task | 14:37 |
| cdent | but now that I know, cool | 14:37 |
| *** jamesmcarthur has quit IRC | 16:08 | |
| *** tosky has quit IRC | 16:29 | |
| *** tosky has joined #storyboard | 16:29 | |
| *** jpich has quit IRC | 16:29 | |
| *** udesale has quit IRC | 16:33 | |
| *** cdent has quit IRC | 16:34 | |
| fungi | _technically_ a launchpad bug comes over as a story with an initial story task corresponding to the bugtask for the project which was imported | 16:37 |
| fungi | if we import multiple projects which all have bugtasks on the same bug in lp, the resulting story will have multiple story tasks corresponding to those | 16:37 |
| fungi | and you can always add more tasks to a story than the initial one, it just needs at least one task | 16:37 |
| fungi | (and unlike launchpad bugtasks, you can have multiple tasks for the same project in a single story) | 16:38 |
| tosky | and when you start using properly the stories with multiple tasks, you don't stop anymore | 16:39 |
| fungi | it takes some adjustment in mindset, since you can track/coordinate things in a single story which would have been multiple bug reports in launchpad purely to work around lp design limitations | 16:40 |
| fungi | here's an example where i tracked the gerrit contactstore removal spec implementation in one story: https://storyboard.openstack.org/#!/story/2001094 | 16:43 |
| fungi | the tasks there correspond to the initial tasks which were discussed and approved for the spec | 16:44 |
| tosky | yeah, it logically works; I have smaller examples: https://storyboard.openstack.org/#!/story/2001996 | 16:48 |
| tosky | now we just need epics :) | 16:48 |
| *** ssbarnea[m] has joined #storyboard | 16:51 | |
| *** ssbarnea has left #storyboard | 16:53 | |
| *** dtantsur is now known as dtantsur|afk | 17:04 | |
| ssbarnea[m] | being redirected to original page on login would be really useful on storyboard... | 17:24 |
| fungi | yeah, i haven't actually figured out what its landing logic on login is | 17:27 |
| *** jamesmcarthur has joined #storyboard | 17:37 | |
| *** jamesmcarthur has quit IRC | 17:47 | |
| SotK | anyone around and wanting a meeting this week? | 19:04 |
| SotK | its *supposed* to redirect to the last page that was viewed, but it doesn't work and has always been a fairly low priority bug | 19:05 |
| clarkb | that bug has caused me to write long comments on the wrong bug in the past :/ | 19:06 |
| fungi | i'm around but didn't have much exciting | 19:10 |
| fungi | vitrage migrated, dhellmann fixed our terrible tag query performance, i'm still stuck trying to figure out the project name url unescaping | 19:10 |
| SotK | I also don't have much exciting, lets leave it for this week? | 19:12 |
| clarkb | next week is a US holiday | 19:22 |
| fungi | sure, we can skip this week and possibly next if people want to celebrate a usa holiday | 19:25 |
| *** jamesmcarthur has joined #storyboard | 19:38 | |
| *** jamesmcarthur has quit IRC | 19:46 | |
| *** jamesmcarthur has joined #storyboard | 19:54 | |
| *** jamesmcarthur has quit IRC | 20:01 | |
| *** jamesmcarthur has joined #storyboard | 20:03 | |
| *** jamesmcarthur has quit IRC | 20:43 | |
| *** jamesmcarthur has joined #storyboard | 20:49 | |
| *** jamesmcarthur has quit IRC | 20:53 | |
| *** jtomasek has quit IRC | 21:03 | |
| *** fatema_ has joined #storyboard | 21:21 | |
| *** jtomasek has joined #storyboard | 21:36 | |
| *** fatema_ has quit IRC | 21:39 | |
| *** fatema_ has joined #storyboard | 21:52 | |
| *** fatema_ has quit IRC | 22:02 | |
| *** jamesmcarthur has joined #storyboard | 22:40 | |
| *** jamesmcarthur has quit IRC | 22:45 | |
| *** tosky has quit IRC | 23:35 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!