<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Max brings up some great questions and issues. This is a great discussion. I know for me, from a UX perspective I have no idea which approach is the most useful and appropriate one. This functionality is fairly deep in the product. It seems like walking through these ideas and how they will work out up against use cases and what they are intended for, would be a useful exercise. There are some great ideas here, and because they are so foundational to the product. it seems like it would be useful to understand the workflows, use cases and how these ideas map to them and if they hold up or break and earlier for something deep like this is better. Would anyone be interested in this exercise?</blockquote><div> </div><div>- Monica </div><div> </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> </blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> </blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Message: 2 Date: Fri, 23 Sep 2016 16:23:42 +0200 From: "Max Rydahl Andersen" <<a href="mailto:manderse@redhat.com">manderse@redhat.com</a>> To: "Michael Kleinhenz" <<a href="mailto:kleinhenz@redhat.com">kleinhenz@redhat.com</a>> Cc: ALMighty-public <<a href="mailto:almighty-public@redhat.com">almighty-public@redhat.com</a>> Subject: Re: [almighty] Idea: modelling iterations Message-ID: <<a href="mailto:4D7F9683-A240-4B45-8E45-C54EAC46060E@redhat.com">4D7F9683-A240-4B45-8E45-C54EAC46060E@redhat.com</a>> Content-Type: text/plain; charset=utf-8; format=flowed On 22 Sep 2016, at 18:52, Michael Kleinhenz wrote: > Another possible model would be to have Iterations itself as a WIT. > Although this would require much more work on manage iterations (like, > create iteration would mean actual creation of a WI instead of just > attaching a label value). On the other hand, querying for iteration > contents could be simpler (by using query ops already there for > queries on WIs). I think this would be going too far IMO. Iterations and labels feels to me like things that warrants first class citizen and not just something encoded inside the generic work item. That said - I agree that things like iterations and other data that are used for grouping/categorizing should be as nice and light to use. Nothing worse having to do several clicks to just put something in a specific bucket when it could be done by typing a label/version/iteration etc. and have it created on the fly. My preference for anything use for categorisation/grouping is to allow defining strictly hierarchical taxonomies via a path like structure. i.e. Alpina/#116 and Banxia/#119 as iterations allowing to "encode" release train+sprint and ten be able to put issues into Alpina/#116 or Alpina dependent on what granualarity that makes sense. Same for areas/components/labels could be useful as hierarchies that can be created on the fly or if a project chooses "locked" down. Now writing through these one could maybe just have a "Categorisation type" and "Categorisation" and say work items can have fields of type "Categorization". i.e. Areas, Components, Labels, Iterations, ... And these have name, (optional) description, (optional) time frame (start/stop). Initially I would probably limit users access to customize the category types, but it seems like it would be interesting to model these categorisation fields in a similar manner and then at the UI/UX layer visualise them what fits best for them. Hope that makes sense ;) WDYT ? /max > > On Thu, Sep 22, 2016 at 6:43 PM, Michael Kleinhenz > <<a href="mailto:kleinhenz@redhat.com">kleinhenz@redhat.com</a>> wrote: >> Hi, >> >> I don't know if core already has iterations in place with it's core >> model. If not, would it be a good idea to model the iterations with >> labels (or tags or keywords, whatever it can be called)? >> >> This would generalize the concept of wi-to-iteration mappings to a >> more generic approach and would possibly enable much more flexibility >> with different planning approaches (like, Scrum 4.0 in 2033 ;-). >> >> An iteration mapping would then just be a special case of label. >> >> See GMail as a very similar case: generalizing the concept of folders >> (mail-to-folder mapping) to labels, enabling lot's of interesting >> usecases. >> >> -- Michael >> >> -- >> Michael Kleinhenz >> Principal Software Engineer >> >> Red Hat Deutschland GmbH >> Werner-von-Siemens-Ring 14 >> 85630 Grasbrunn >> Germany >> >> RED HAT | TRIED. TESTED. TRUSTED. >> Red Hat GmbH, <a href="http://www.de.redhat.com" rel="noreferrer" target="_blank">www.de.redhat.com</a>, >> Registered seat: Grasbrunn, Commercial register: Amtsgericht >> M?nchen, >> HRB 153243, >> Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham, >> Michael O'Neill > > -- > Michael Kleinhenz > Principal Software Engineer > > Red Hat Deutschland GmbH > Werner-von-Siemens-Ring 14 > 85630 Grasbrunn > Germany > > RED HAT | TRIED. TESTED. TRUSTED. > Red Hat GmbH, <a href="http://www.de.redhat.com" rel="noreferrer" target="_blank">www.de.redhat.com</a>, > Registered seat: Grasbrunn, Commercial register: Amtsgericht M?nchen, > HRB 153243, > Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham, > Michael O'Neill > > _______________________________________________ > almighty-public mailing list > <a href="mailto:almighty-public@redhat.com">almighty-public@redhat.com</a> > <a href="https://www.redhat.com/mailman/listinfo/almighty-public" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/almighty-public</a> /max <a href="http://about.me/maxandersen" rel="noreferrer" target="_blank">http://about.me/maxandersen</a> ------------------------------ Message: 3 Date: Fri, 23 Sep 2016 11:06:32 -0400 From: Andrew Lee Rubinger <<a href="mailto:alr@redhat.com">alr@redhat.com</a>> To: Adam Jolicoeur <<a href="mailto:ajolicoe@redhat.com">ajolicoe@redhat.com</a>> Cc: ALMighty-public <<a href="mailto:almighty-public@redhat.com">almighty-public@redhat.com</a>> Subject: Re: [almighty] User Experience for Almighty Message-ID: <CABm567E1+5Nd5CatWKsZG8nwU=<a href="mailto:C64iv51JBSDUMEBFOtwzqKow@mail.gmail.com">C64iv51JBSDUMEBFOtwzqKow@mail.gmail.com</a>> Content-Type: text/plain; charset="utf-8" On Fri, Sep 23, 2016 at 9:44 AM, Adam Jolicoeur <<a href="mailto:ajolicoe@redhat.com">ajolicoe@redhat.com</a>> wrote: > Good Morning (or Afternoon or Evening), > > As a follow up to the F2F last week, the UXD Team (specifically Monica and > I) have created an almighty-ux repo on GitHub under almighty/almighty-ux. > We will be tracking issues there, as well as Sprint milestones and work > items that correspond to UI development efforts. If there are discussion > items that anyone would like to post (other than on this mailing list), you > can create an issue under this repo, with the label ?discussion?. We?ll > monitor what is posted and prioritize as necessary. > > Regarding wireframes/mockups and other documentation, a UX directory has > been added to the almighty-devdoc repo. Any information will also be > displayed on <a href="http://devdoc.almighty.io" rel="noreferrer" target="_blank">devdoc.almighty.io</a> under ?ux designs > <<a href="http://devdoc.almighty.io/ux/ux-overview.html" rel="noreferrer" target="_blank">http://devdoc.almighty.io/ux/ux-overview.html</a>>?. Feel free to visit this > area for design references and information. Many times, it will just be > links to our InVision prototypes, but we will also include (in the future) > persona information, research and notes. > My applause for this effort! > > Any questions? Let us know! > > Thanks! > Adam Jolicoeur > > ---------- > Adam J. Jolicoeur > Interaction Designer > Red Hat Inc. > Email: <a href="mailto:adam.jolicoeur@redhat.com">adam.jolicoeur@redhat.com</a> > > > _______________________________________________ > almighty-public mailing list > <a href="mailto:almighty-public@redhat.com">almighty-public@redhat.com</a> > <a href="https://www.redhat.com/mailman/listinfo/almighty-public" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/almighty-public</a> > > -- Red Hat Developer Programs Architecture @ALRubinger -------------- next part -------------- An HTML attachment was scrubbed... URL: <<a href="https://www.redhat.com/archives/almighty-public/attachments/20160923/f0cb6cd2/attachment.html" rel="noreferrer" target="_blank">https://www.redhat.com/archives/almighty-public/attachments/20160923/f0cb6cd2/attachment.html</a>> ------------------------------ _______________________________________________ almighty-public mailing list <a href="mailto:almighty-public@redhat.com">almighty-public@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/almighty-public" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/almighty-public</a> End of almighty-public Digest, Vol 5, Issue 41 ********************************************** </blockquote></div> </div></div>