*** udesale has joined #storyboard | 03:36 | |
*** ssbarnea has quit IRC | 04:29 | |
*** ssbarnea has joined #storyboard | 04:32 | |
*** jtomasek has quit IRC | 05:59 | |
*** jtomasek has joined #storyboard | 06:11 | |
*** jtomasek has quit IRC | 06:18 | |
*** jtomasek has joined #storyboard | 06:19 | |
*** florianf has joined #storyboard | 07:28 | |
*** tosky has joined #storyboard | 07:29 | |
*** ssbarnea_ has joined #storyboard | 07:29 | |
*** ssbarnea_ has quit IRC | 07:31 | |
*** ssbarnea_ has joined #storyboard | 07:45 | |
*** jpich has joined #storyboard | 07:55 | |
*** dtantsur|afk is now known as dtantsur | 10:50 | |
*** thrace has joined #storyboard | 11:06 | |
*** persia has joined #storyboard | 11:06 | |
*** persia_ has joined #storyboard | 11:06 | |
TheJulia | Is there any way to merge stories? | 13:19 |
---|---|---|
SotK | not at the moment, no | 13:20 |
SotK | its something that would probably be useful to implement somehow though, but will need thought to work nicely | 13:21 |
TheJulia | okay, we (ironic) were just doing some bug triaging on a call and found where someone duplicated something we imported from launchpad :( | 13:21 |
SotK | our workflow for duplicate stories against storyboard has been to mark the tasks invalid and tag the story as a duplicate, and link the original in the comments | 13:23 |
SotK | there was some discussion at the PTG involving aspiers and persia about more effective duplicates support, but I don't recall the specifics off the top of my head | 13:23 |
*** ssbarnea_ has quit IRC | 13:59 | |
TheJulia | It would be interesting to see, because we ran across a few cases where we had duplicates and it would have been useful because there was information both that made sense to preserve | 14:51 |
*** jamesmcarthur has joined #storyboard | 15:09 | |
*** ssbarnea_ has joined #storyboard | 15:43 | |
*** jamesmcarthur has quit IRC | 16:50 | |
*** jamesmcarthur has joined #storyboard | 16:54 | |
*** jamesmcarthur has quit IRC | 16:57 | |
*** dtantsur is now known as dtantsur|afk | 17:02 | |
*** jpich has quit IRC | 17:10 | |
*** ssbarnea_ has quit IRC | 17:14 | |
*** jamesmcarthur has joined #storyboard | 17:26 | |
*** jamesmcarthur has quit IRC | 17:34 | |
*** florianf has quit IRC | 17:41 | |
*** udesale has quit IRC | 17:50 | |
fungi | yeah, if we just wanted it to work like lp does (which granted is not great either) it could shade the text boxes slightly on the redundant stories with an admonition near the top (similar to what private stories display) mentioning the corresponding canonical story, have somewhere on the page to display a list of the stories which are duplicates of the one you're currently looking at, and possibly hide | 18:06 |
fungi | redundant stories from search results | 18:06 |
fungi | and maybe also switch the tasks on the story to invalid or some similar but not yet implemented task state | 18:07 |
mordred | so I've gotten myself sucked in to geneology things - and one of the sites for doing it is wikitree... | 18:08 |
mordred | they have a 'merge people' facility, because sometimes the same person gets added twice from different directions | 18:08 |
mordred | the ui for that pulls up a side-by-side comparison of each of the pieces of data - as well as the narrative description of the person | 18:09 |
mordred | and lets you select which thing should go into the final merged entry - as well as, for narrative description, allow you to merge both, pick one - or write your own new one | 18:10 |
fungi | yeah, three-way merge would be really cool... and probably a ton of development effort, but maybe that's not a problem if someone's really keen on writing the implementation | 18:10 |
mordred | yah | 18:10 |
fungi | however the thing you're talking about isn't really for chronological discussion text though, right? seems like merging discussions would get strange really fast | 18:10 |
mordred | it also does it as 'merge one person into another person' - so the one that got merged then turns in to a re-direct to the new person | 18:10 |
mordred | fungi: if you could do those in a sort of threaded manner perhaps ... | 18:11 |
fungi | step #0, add threading to storyboard comments ;) | 18:11 |
mordred | fungi: (yeah, merging the discussion text is likely the hardest part) | 18:11 |
mordred | fungi: step #0 could turn all current storyboard comments into a thread with the story itself being the 'root' of the thread. then for the merged case, you could add an entry for the second story as a message off the main story with the discussion thread intact below it | 18:12 |
mordred | OR - one could not do any of thise :) | 18:12 |
fungi | yeah, but would still imply adding threading to the data model and corresponding parameters to the relevant api methods and then extend the webclient to provide visualization of that as well as some sort of "reply" button allowing the user to branch the discussion at specific comments | 18:15 |
fungi | otherwise it quickly gets confusing as to which original story's discussion someone's following up to with new comments at that point | 18:16 |
*** jamesmcarthur has joined #storyboard | 18:26 | |
*** jamesmcarthur has quit IRC | 18:31 | |
*** jamesmcarthur has joined #storyboard | 18:57 | |
*** jamesmcarthur has quit IRC | 19:01 | |
*** jamesmcarthur has joined #storyboard | 19:24 | |
*** jamesmcarthur has quit IRC | 19:24 | |
*** jamesmcarthur has joined #storyboard | 19:24 | |
*** ssbarnea_ has joined #storyboard | 19:29 | |
*** jamesmcarthur has quit IRC | 19:38 | |
*** ssbarnea_ has quit IRC | 19:54 | |
*** ssbarnea_ has joined #storyboard | 19:55 | |
*** jtomasek has quit IRC | 21:30 | |
SotK | iirc the API already partially supports threaded comments | 21:37 |
corvus | do we have direct links to report bugs for projects yet? | 21:50 |
corvus | fungi: ^ | 21:50 |
fungi | corvus: not to my knowledge | 21:58 |
fungi | i think what's missing is a passthrough to specify the default project selection for the initial task which gets autopopulated | 21:59 |
corvus | fungi: thanks | 22:04 |
fungi | corvus: if we had that it could extend the current reporting url get parameters we already have for forcing private, setting a starting description text and so on | 22:05 |
fungi | it's definitely a feature i've wanted | 22:05 |
fungi | basically the analog of lp's "report a bug" link from its project pages | 22:06 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!