| *** jasondotstar has quit IRC | 01:35 | |
| *** jasondotstar has joined #storyboard | 01:37 | |
| *** openstackgerrit has quit IRC | 02:15 | |
| *** openstackgerrit has joined #storyboard | 02:24 | |
| *** kencjohnston has joined #storyboard | 02:32 | |
| *** kencjohnston has quit IRC | 03:01 | |
| *** kencjohnston has joined #storyboard | 03:03 | |
| *** kencjohnston has quit IRC | 04:07 | |
| *** jtomasek has joined #storyboard | 07:36 | |
| *** mrmartin has joined #storyboard | 07:36 | |
| *** faybrocklebank has joined #storyboard | 08:17 | |
| *** mrmartin has quit IRC | 08:43 | |
| *** openstackgerrit has quit IRC | 08:47 | |
| *** openstackgerrit_ has joined #storyboard | 08:47 | |
| *** openstackgerrit_ is now known as openstackgerrit | 08:48 | |
| *** jtomasek has quit IRC | 08:52 | |
| *** jtomasek has joined #storyboard | 08:57 | |
| *** mrmartin has joined #storyboard | 09:06 | |
| *** mrmartin has quit IRC | 09:18 | |
| *** mrmartin has joined #storyboard | 09:39 | |
| Zara | morning storyboard! | 10:23 |
|---|---|---|
| SotK | morning! | 10:23 |
| openstackgerrit | Zara proposed openstack-infra/storyboard-webclient: Make header 'quick navigate' and 'search' clearer https://review.openstack.org/278987 | 11:18 |
| *** jtomasek_ has joined #storyboard | 13:20 | |
| *** jtomasek_ has quit IRC | 13:37 | |
| Zara | ooi, how come the quick-navigation bar in the header wasn't deemed suitable for small screens? | 14:12 |
| *** krotscheck_dcm is now known as krotscheck | 14:15 | |
| * krotscheck doesn't remember | 14:15 | |
| *** mrmartin has quit IRC | 14:16 | |
| Zara | heh :) I don't actually *have* a smartphone so I'm the worst person for knowing this sort of thing... I want to free up space on the sidebar for a boards/worklists icon, and I don't want to increase the number of icons (slippery slope to a million buttons, imo). so on large screens, planning to move 'search' icon to text saying 'advanced search' under quick navigate bar in header. On small screens, may ju | 14:22 |
| Zara | st move icon to the header, if we shouldn't have the bar. | 14:22 |
| *** mrmartin has joined #storyboard | 14:36 | |
| *** mrmartin has quit IRC | 14:38 | |
| krotscheck | Well, thankfully chrome will simulate that for you. | 14:43 |
| Zara | oooh, neat | 14:47 |
| Zara | TIL | 14:47 |
| Zara | (I'd been zooming to 300% as a workaround) | 14:47 |
| Zara | thanks for the tip | 14:48 |
| * SotK tries to figure out how to make assigning a due date to a card in a board sane | 15:32 | |
| SotK | I'm not sure how to know what to do when the user changes the due date a card has, does this assert the new due date for the task and leave the old one, or unassert the old one and assert the new one | 15:37 |
| SotK | I'm also not entirely sure how we should be picking which date shows up on a card, other than "earliest one assigned to it that is visible in this board" | 15:38 |
| Zara | by 'assert'/'unassert', do you mean create/destory? | 15:40 |
| Zara | *destroy | 15:40 |
| Zara | or 'say this one is important' vs 'ignore this one'? | 15:40 |
| SotK | I mean say "I think this task should have this due date" | 15:41 |
| SotK | (so, assigning the due date to a task) | 15:41 |
| Zara | so is this changing which target a task is working toward (which might involve making a new target), or changing the date of a target? | 15:43 |
| SotK | the former | 15:44 |
| Zara | okay, I think unassert the old one and assert the new one, since I'm not sure when it'd be useful to display both (could be wrong on that though?) (also, I actually think it should display 'latest one assigned to it') | 15:51 |
| Zara | since I'm guessing within a board that'd be the most relevant. | 15:51 |
| SotK | but, latest one assigned to it by whom? | 15:53 |
| Zara | until we have filter-dates-by-creator, I'd default to 'all creators and users of the board' and see what happens. | 15:55 |
| Zara | I guess the alternative is archiving old targets when they're not relavant | 15:57 |
| Zara | or removing them from the board | 15:58 |
| Zara | I'd be wary of someone changing a date and it removing a target from a board by default, though. | 15:58 |
| Zara | (yeah no that really wouldn't work because they could be relevant to other tasks in the board, so nvm that last bit) | 15:59 |
| Zara | summary: it has to display the new one, otherwise you have no way of updating a task's due date in a visible way without getting rid of the associated target. | 16:00 |
| Zara | b/c either you're manually unasserting, so you definitely want the new one, or you're not, in which case, unless the target goes, you've just made an invisible due-date afaict | 16:02 |
| SotK | that makes sense, but what if the previous due date still needs to be asserted (ie, it was asserted by a PM and is now being replaced by a dev's personal target)? :/ | 16:03 |
| Zara | we can't do personal targets without filtering by user | 16:03 |
| Zara | hm, I'm trying to think if there's a way around that | 16:04 |
| SotK | even with that, what happens if a user is in the "owners" group for more than one date on a task? | 16:05 |
| Zara | so, this is multiple targets applied to a task, and we're actually saying 'which target is more important?' (sorry I don't want to use 'date' here because it confuses whether we're referring to the date or the object that includes a date) | 16:06 |
| Zara | So I think in the case where there are multiple targets, a user needs to be able to filter the view by target, without dissassociating those from the board for everyone | 16:08 |
| SotK | this is when someone creates a target/due date, assigns it to a task, then later on creates another target/due date (which is later than the other target) and for whatever reason also assigns that target to the task | 16:09 |
| Zara | right, so in that case, I think you'd end up with multiple dates on the card by default | 16:10 |
| * SotK thinks that will look really messy | 16:10 | |
| Zara | so we'd want the view to be able to filter by target | 16:10 |
| Zara | yep | 16:10 |
| SotK | my understanding of "filter by target" is "only show cards whose tasks or stories have this target", does that match yours? :) | 16:11 |
| Zara | ah, no, I was thinking 'only show dates on the cards that match this target' | 16:12 |
| Zara | that's ambiguous, sorry, 'only show dates that are part of this target on the cards' | 16:12 |
| Zara | because I don't see how storyboard can guess which target is the most important, but it can remember a user's preference for that. | 16:13 |
| SotK | this is all getting really complex again :( | 16:17 |
| Zara | so sb shows all the cards on the board, and if, eg, 'deliver demo' target is checked, it shows dates for that target on the cards (and other cards without dates). if 'deliver demo' and 'make a thing' are checked, sb shows both dates per card (a tricky thing is making it clear which date applies to which target) | 16:17 |
| Zara | so the best option to begin with is to just show the most recent date, and not do personal targets | 16:19 |
| Zara | because that will require filtering dates by user or target or both and that will be tricky. | 16:19 |
| SotK | I think that is the pest option permanently tbh, but we'll see if people really want to start putting personal targets on shared boards | 16:19 |
| SotK | s/pest/best/ | 16:20 |
| Zara | yeah, I thought doing it this way lets us be flexible enough to incorporate iff we need it | 16:20 |
| Zara | *incorporate it | 16:20 |
| * SotK decides the next problem is, "what if the user changing the due date doesn't have permission to unassert the previous date?" | 16:21 | |
| SotK | s/date/target/ | 16:21 |
| Zara | then they can't change the date, hahahaha | 16:21 |
| Zara | in seriousness, I think that's right. they'd have to get permission or get someone with permission to do it. | 16:22 |
| Zara | permissions just apply within a specific board, right? | 16:22 |
| SotK | nope, they are per-target for the purposes of asserting/unasserting targets | 16:23 |
| SotK | hmm, that has made me think about what happens when you add a user to a board | 16:28 |
| Zara | oh, I thought the date was asserted just in the context of the board? | 16:28 |
| SotK | nope, the date is asserted storyboard-wide | 16:28 |
| SotK | one date can be in use in many boards, and can be asserted on many tasks/stories | 16:29 |
| Zara | and tasks can have multiple dates? | 16:29 |
| SotK | yeah | 16:29 |
| Zara | I still don't understand 'assert' in this context then! xD | 16:30 |
| * SotK types up his understanding to paste it somewhere | 16:31 | |
| Zara | right, I thought a task had multiple targets. which target is relevant depends on the board (and there could be more within a board, but we're ignoring those for now). so asserting = saying which one is relevant, rather than adding a target to a task | 16:33 |
| Zara | that was what I thought was going on | 16:33 |
| Zara | s/which one/which target | 16:34 |
| SotK | aha, I was using "assert" = "assign a due date to a task" | 16:34 |
| Zara | hah, you've probably said that like 5 times and I've read it figuratively or something | 16:35 |
| Zara | right, so if I've follwed this time, assigning a date would remove the old due dates where that's what it means to 'assert'. | 16:35 |
| SotK | well, I don't really know what is the right thing to do | 16:36 |
| Zara | ah, right, I misunderstood before. I think we should keep all the dates | 16:36 |
| SotK | because you might assign a new date to replace an old date, or you might assign a new one because none of the old ones match your opinion | 16:36 |
| Zara | but we decide relevance at the board level. | 16:36 |
| SotK | relevancy is a whole different kettle of fish, which I think *should* be per-board, editable by people who can move cards in that board, and one-date-per-card | 16:37 |
| * SotK hopes you agree :P | 16:37 | |
| Zara | I think where someone assigns a new one to replace an old date | 16:37 |
| Zara | it's up to them to remove the old one from affected boards | 16:37 |
| * SotK is fine with that | 16:38 | |
| Zara | ~o~ | 16:38 |
| *** wendar_ has joined #storyboard | 16:38 | |
| SotK | ok, we can also use the per-card "relevant due date" to get the count of cards per-due-date in the board | 16:38 |
| Zara | and yep totally (we may differ on potential number of dates per card but that's a long way off so :)) | 16:39 |
| *** betherly has quit IRC | 16:39 | |
| *** jmccrory has quit IRC | 16:39 | |
| *** wendar has quit IRC | 16:39 | |
| *** mrmartin has joined #storyboard | 16:39 | |
| SotK | I think people's personal dates belong in their own personal boards xD | 16:40 |
| SotK | but I might be wrong :) | 16:40 |
| Zara | btw, I definitely got confused by 'date' as 'date' and 'date' as 'target, including a name and a date'; so if we can change the terminology now +6 to changing 'due_date' to 'target' | 16:40 |
| Zara | alternatively, we need to stipulate people use due_date to refer to the due_date, and not the due_date_date. | 16:41 |
| *** betherly has joined #storyboard | 16:41 | |
| Zara | haha, I wrote that wrong | 16:42 |
| Zara | what a day | 16:42 |
| SotK | :D | 16:42 |
| Zara | alternatively, we need to stipulate people use due_date to refer to the due_date, and not use 'date' to refer to the due_date | 16:42 |
| Zara | ^ was what I meant to type | 16:42 |
| SotK | that makes more sense, and is what I kept doing in my laziness | 16:42 |
| * SotK apologises for piling on the confusion | 16:42 | |
| Zara | hahaha | 16:42 |
| Zara | right, I'll never ever refer to filters again, and you'll never refer to dates, and life will be amazing | 16:43 |
| *** jmccrory has joined #storyboard | 16:44 | |
| *** mrmartin has quit IRC | 16:47 | |
| *** mrmartin has joined #storyboard | 16:56 | |
| *** mrmartin has quit IRC | 17:08 | |
| *** mrmartin has joined #storyboard | 17:12 | |
| openstackgerrit | Zara proposed openstack-infra/storyboard-webclient: WIP Search Changes https://review.openstack.org/279204 | 17:32 |
| openstackgerrit | Zara proposed openstack-infra/storyboard-webclient: WIP Task Links https://review.openstack.org/277882 | 17:36 |
| *** mrmartin has quit IRC | 17:40 | |
| *** mrmartin has joined #storyboard | 17:49 | |
| *** mrmartin has quit IRC | 17:54 | |
| Zara | hm, I haven't got much done today. where did the time go?! | 18:00 |
| * Zara hopes to be more useful tomorrow, 'night! :) | 18:07 | |
| *** mrmartin has joined #storyboard | 18:14 | |
| *** mrmartin has quit IRC | 18:15 | |
| *** faybrocklebank has quit IRC | 18:19 | |
| *** kencjohnston has joined #storyboard | 18:32 | |
| *** mrmartin has joined #storyboard | 18:40 | |
| *** mrmartin has quit IRC | 18:53 | |
| *** mrmartin has joined #storyboard | 18:54 | |
| *** mrmartin has quit IRC | 18:58 | |
| *** jtomasek has quit IRC | 20:31 | |
| *** kencjohnston has quit IRC | 22:11 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!