Thursday, 2018-05-03

*** udesale has joined #storyboard03:36
*** ssbarnea has quit IRC04:29
*** ssbarnea has joined #storyboard04:32
*** jtomasek has quit IRC05:59
*** jtomasek has joined #storyboard06:11
*** jtomasek has quit IRC06:18
*** jtomasek has joined #storyboard06:19
*** florianf has joined #storyboard07:28
*** tosky has joined #storyboard07:29
*** ssbarnea_ has joined #storyboard07:29
*** ssbarnea_ has quit IRC07:31
*** ssbarnea_ has joined #storyboard07:45
*** jpich has joined #storyboard07:55
*** dtantsur|afk is now known as dtantsur10:50
*** thrace has joined #storyboard11:06
*** persia has joined #storyboard11:06
*** persia_ has joined #storyboard11:06
TheJuliaIs there any way to merge stories?13:19
SotKnot at the moment, no13:20
SotKits something that would probably be useful to implement somehow though, but will need thought to work nicely13:21
TheJuliaokay, we (ironic) were just doing some bug triaging on a call and found where someone duplicated something we imported from launchpad :(13:21
SotKour 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 comments13:23
SotKthere 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 head13:23
*** ssbarnea_ has quit IRC13:59
TheJuliaIt 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 preserve14:51
*** jamesmcarthur has joined #storyboard15:09
*** ssbarnea_ has joined #storyboard15:43
*** jamesmcarthur has quit IRC16:50
*** jamesmcarthur has joined #storyboard16:54
*** jamesmcarthur has quit IRC16:57
*** dtantsur is now known as dtantsur|afk17:02
*** jpich has quit IRC17:10
*** ssbarnea_ has quit IRC17:14
*** jamesmcarthur has joined #storyboard17:26
*** jamesmcarthur has quit IRC17:34
*** florianf has quit IRC17:41
*** udesale has quit IRC17:50
fungiyeah, 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 hide18:06
fungiredundant stories from search results18:06
fungiand maybe also switch the tasks on the story to invalid or some similar but not yet implemented task state18:07
mordredso I've gotten myself sucked in to geneology things - and one of the sites for doing it is wikitree...18:08
mordredthey have a 'merge people' facility, because sometimes the same person gets added twice from different directions18:08
mordredthe 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 person18:09
mordredand 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 one18:10
fungiyeah, 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 implementation18:10
mordredyah18:10
fungihowever the thing you're talking about isn't really for chronological discussion text though, right? seems like merging discussions would get strange really fast18:10
mordredit 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 person18:10
mordredfungi: if you could do those in a sort of threaded manner perhaps ...18:11
fungistep #0, add threading to storyboard comments ;)18:11
mordredfungi: (yeah, merging the discussion text is likely the hardest part)18:11
mordredfungi: 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 it18:12
mordredOR - one could not do any of thise :)18:12
fungiyeah, 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 comments18:15
fungiotherwise it quickly gets confusing as to which original story's discussion someone's following up to with new comments at that point18:16
*** jamesmcarthur has joined #storyboard18:26
*** jamesmcarthur has quit IRC18:31
*** jamesmcarthur has joined #storyboard18:57
*** jamesmcarthur has quit IRC19:01
*** jamesmcarthur has joined #storyboard19:24
*** jamesmcarthur has quit IRC19:24
*** jamesmcarthur has joined #storyboard19:24
*** ssbarnea_ has joined #storyboard19:29
*** jamesmcarthur has quit IRC19:38
*** ssbarnea_ has quit IRC19:54
*** ssbarnea_ has joined #storyboard19:55
*** jtomasek has quit IRC21:30
SotKiirc the API already partially supports threaded comments21:37
corvusdo we have direct links to report bugs for projects yet?21:50
corvusfungi: ^21:50
fungicorvus: not to my knowledge21:58
fungii think what's missing is a passthrough to specify the default project selection for the initial task which gets autopopulated21:59
corvusfungi: thanks22:04
fungicorvus: 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 on22:05
fungiit's definitely a feature i've wanted22:05
fungibasically the analog of lp's "report a bug" link from its project pages22:06

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!