<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
</head>
<body>
<div name="messageBodySection" style="font-size: 14px; font-family: -apple-system, BlinkMacSystemFont, sans-serif;">Hi Everyone,
<div><br /></div>
<div>As part of this conversation, I thought it would make sense to share the Areas diagram that UX has created, through discussions with Todd and Michael V. Additional information can be found on GitHub: <a href="https://github.com/fabric8io/fabric8-ux/issues/101">https://github.com/fabric8io/fabric8-ux/issues/101</a>. </div>
<div><br /></div>
<div>-Adam</div>
</div>
<div name="messageReplySection" style="font-size: 14px; font-family: -apple-system, BlinkMacSystemFont, sans-serif;"><br />
On Jan 23, 2017, 4:06 PM -0500, Michael Virgil <mvirgil@redhat.com>, wrote:<br />
<blockquote type="cite" style="margin: 5px 5px; padding-left: 10px; border-left: thin solid #1abc9c;">
<div dir="ltr">The intent is as Konrad describes.
<div><br /></div>
<div>Based on the current behavior, there are some issues that can be addressed in the design/implementation to make this clearer. Would also need to ensure that the context and providing what can be created within that context from the backend. UX team is currently working on refining the UX/interaction to clarify this user experience - in this area.
<div><br /></div>
<div>In general; the process template selected when creating the Space defines the process hierarchy (planning work Item relationships, among other things).</div>
<div><br /></div>
<div>
<div>The intent:</div>
<ul>
<li>The quick create, should be just that, quickly create goal based work items at a level that I've determined by my setting my context <br /></li>
<li>The context; where I am working within the hierarchy; Theme, Initiative, Epic, Story, Task... Vision, Scenario, Value Prop, Experience, Feature, Task... or whatever</li>
<li>User Experience needs to be clean, clear and obvious to the user</li>
</ul>
</div>
<div>I should be able to set my context and then...</div>
<div>
<ul>
<li>Create a bunch of tasks for a story...</li>
<li>Create a bunch of stories to refine the goal of an Epic... </li>
<li>Create a bunch of stories in the backlog... </li>
<li>Create a bunch of initiatives while brainstorming... </li>
<li>etc.</li>
</ul>
<div>It would be easy to envision a common set of filters/views/tree structures that would be applied to all these hierarchies. The look and feel would be the same and comfortable for parent/child relationships - defined in the process template. Should not need any custom code in the backend or FE to accommodate these process templates. If we focus on Agile/Scrum for the first implantation using the templates, I would assume adding Waterfall, Red Hat or other process would not be a major feat...<br /></div>
</div>
<div><br /></div>
<div>I would also anticipate that the process template would allow a team over time, not out of the gate, to define the policies, rules and/or constraints of the process. This could include the rules/policies for work items (parent/children) relationships, iterations (milestones), policies for permissions, or even the fields to present on views. I think there is a lot we could configure and potentially allow to be defined within the template.</div>
<div><br /></div>
<div>Just some things we need to think about.</div>
<div><br /></div>
<div>For now, lets just get a simple end-2-end use case for the parent/child hierarchy working using a process template and we can extend it over time.</div>
<div><br /></div>
<div>Michael</div>
</div>
</div>
<div class="gmail_extra"><br />
<div class="gmail_quote">On Mon, Jan 23, 2017 at 8:36 AM, Aslak Knutsen <span dir="ltr"><<a href="mailto:aslak@redhat.com" target="_blank">aslak@redhat.com</a>></span> wrote:<br />
<blockquote class="gmail_quote" style="margin: 5px 5px; padding-left: 10px; border-left: thin solid #e67e22;">
<div dir="ltr">If that's the same QuickAdd bar, then I think it should visually be moved inside the Open WI draw to show the context things are being added and the 'type selector' be filtered same as 'allowed links'.
<div><span class="HOEnZb"><font color="#888888"><br /></font></span></div>
<div><span class="HOEnZb"><font color="#888888">-aslak-</font></span></div>
</div>
<div class="HOEnZb">
<div class="h5">
<div class="gmail_extra"><br />
<div class="gmail_quote">On Mon, Jan 23, 2017 at 2:23 PM, Konrad Kleine <span dir="ltr"><<a href="mailto:kkleine@redhat.com" target="_blank">kkleine@redhat.com</a>></span> wrote:<br />
<blockquote class="gmail_quote" style="margin: 5px 5px; padding-left: 10px; border-left: thin solid #3498db;">
<div dir="ltr">Aslak,
<div><br /></div>
<div>yes we need something superior, but if the quick add bar simply performs two actions rather than one, we're safe:</div>
<div><br /></div>
<div>1. Add work item (userstory)</div>
<div>2. Link to currently "open" work item (epic)</div>
<div><br /></div>
<div>That implies three things (at least)</div>
<div><br /></div>
<div>1. we can have some form of navigation that makes allows for filtering user stories based on a concrete link type (e.g. child of)</div>
<div>2. the quick add bar knows about which link type can be used (maybe the one which was used to filter in the first place?)</div>
<div>3. the quick add bar adds the new work item (userstory)</div>
<div>4. the quick add bar creates the link between the epic (currently filtered on) and the newly created user story</div>
<div><br /></div>
<div><br /></div>
</div>
<div class="m_1479773159329925911HOEnZb">
<div class="m_1479773159329925911h5">
<div class="gmail_extra"><br />
<div class="gmail_quote">On Mon, Jan 23, 2017 at 2:08 PM, Aslak Knutsen <span dir="ltr"><<a href="mailto:aslak@redhat.com" target="_blank">aslak@redhat.com</a>></span> wrote:<br />
<blockquote class="gmail_quote" style="margin: 5px 5px; padding-left: 10px; border-left: thin solid #d35400;">
<div dir="ltr">That workflow is unrelated to 'Epics'.
<div><br /></div>
<div>It's what we do in every planning sessions on some level. </div>
<div><br /></div>
<div>Create/Read a userstory, add 10 tasks.</div>
<div><br /></div>
<div>It's a feature for, I create/have a parent, now create n children.</div>
<div><br /></div>
<div>We need a better approach than;</div>
<div><br /></div>
<div>* Create parent</div>
<div>* Create child 1</div>
<div>* Create child 2<br /></div>
<div>* Create child n<br /></div>
<div>...</div>
<div>* Open parent</div>
<div>* Search and Link child 1</div>
<div>* Search and Link child 2<br /></div>
<div>* Search and Link child n<br /></div>
<div>...</div>
<div><span class="m_1479773159329925911m_7788017760563137094HOEnZb"><font color="#888888"><br /></font></span></div>
<div><span class="m_1479773159329925911m_7788017760563137094HOEnZb"><font color="#888888"><br /></font></span></div>
<div><span class="m_1479773159329925911m_7788017760563137094HOEnZb"><font color="#888888">-aslak-</font></span></div>
</div>
<div class="m_1479773159329925911m_7788017760563137094HOEnZb">
<div class="m_1479773159329925911m_7788017760563137094h5">
<div class="gmail_extra"><br />
<div class="gmail_quote">On Mon, Jan 23, 2017 at 1:58 PM, Konrad Kleine <span dir="ltr"><<a href="mailto:kkleine@redhat.com" target="_blank">kkleine@redhat.com</a>></span> wrote:<br />
<blockquote class="gmail_quote" style="margin: 5px 5px; padding-left: 10px; border-left: thin solid #34495e;">
<div dir="ltr">If I were a user of the system I'd probably go in and
<div><br /></div>
<div>
<ol>
<li>create an epic from the work item type dialog.<br /></li>
<li>go to the quick add and add 10 features</li>
</ol>
<div>IMHO we shouldn't first build for custom tailored UI solutions that fit a work flow specific to epics. I'm not saying we shouldn't do this at all but if we have the tools in place to do operate generically, then this is good start, no?</div>
</div>
</div>
<div class="m_1479773159329925911m_7788017760563137094m_-9193339247053115346HOEnZb">
<div class="m_1479773159329925911m_7788017760563137094m_-9193339247053115346h5">
<div class="gmail_extra"><br />
<div class="gmail_quote">On Mon, Jan 23, 2017 at 1:51 PM, Todd Mancini <span dir="ltr"><<a href="mailto:tmancini@redhat.com" target="_blank">tmancini@redhat.com</a>></span> wrote:<br />
<blockquote class="gmail_quote" style="margin: 5px 5px; padding-left: 10px; border-left: thin solid #2ecc71;">
<div dir="ltr">Can someone describe to me the experience of this common usage pattern: a user wants to create a new Epic and ten related Features. What's that workflow for that? </div>
<div class="m_1479773159329925911m_7788017760563137094m_-9193339247053115346m_-2194227522843130956HOEnZb">
<div class="m_1479773159329925911m_7788017760563137094m_-9193339247053115346m_-2194227522843130956h5">
<div class="gmail_extra"><br />
<div class="gmail_quote">On Mon, Jan 23, 2017 at 7:39 AM, Konrad Kleine <span dir="ltr"><<a href="mailto:kkleine@redhat.com" target="_blank">kkleine@redhat.com</a>></span> wrote:<br />
<blockquote class="gmail_quote" style="margin: 5px 5px; padding-left: 10px; border-left: thin solid #9b59b6;">
<div dir="ltr">We currently have the a little icon next to the left most field once you've clicked the quick add button. I suggest to make this a toggle just like we used to have it for the work item symbol in the top left corner of the details page: <a href="https://cloud.githubusercontent.com/assets/193408/21686784/d717829e-d366-11e6-9641-b61cece54c99.png" target="_blank">https://cloud.githubuserconten<wbr />t.com/assets/193408/21686784/d<wbr />717829e-d366-11e6-9641-b61cece<wbr />54c99.png</a>. Currently this is just a symbol and no longer a menu.</div>
<div class="m_1479773159329925911m_7788017760563137094m_-9193339247053115346m_-2194227522843130956m_-3602276906330631949HOEnZb">
<div class="m_1479773159329925911m_7788017760563137094m_-9193339247053115346m_-2194227522843130956m_-3602276906330631949h5">
<div class="gmail_extra"><br />
<div class="gmail_quote">On Mon, Jan 23, 2017 at 1:26 PM, Aslak Knutsen <span dir="ltr"><<a href="mailto:aslak@redhat.com" target="_blank">aslak@redhat.com</a>></span> wrote:<br />
<blockquote class="gmail_quote" style="margin: 5px 5px; padding-left: 10px; border-left: thin solid #e74c3c;">
<div dir="ltr">Then what happens to QuickAdd when there are multiple types shown in a list?</div>
<div class="m_1479773159329925911m_7788017760563137094m_-9193339247053115346m_-2194227522843130956m_-3602276906330631949m_8158092590246300950HOEnZb">
<div class="m_1479773159329925911m_7788017760563137094m_-9193339247053115346m_-2194227522843130956m_-3602276906330631949m_8158092590246300950h5">
<div class="gmail_extra"><br />
<div class="gmail_quote">On Mon, Jan 23, 2017 at 1:21 PM, Konrad Kleine <span dir="ltr"><<a href="mailto:kkleine@redhat.com" target="_blank">kkleine@redhat.com</a>></span> wrote:<br />
<blockquote class="gmail_quote" style="margin: 5px 5px; padding-left: 10px; border-left: thin solid #1abc9c;">
<div dir="ltr">
<div style="font-size:12.8px">Hey Aslak,</div>
<div><span><br /></span></div>
<span>> <span style="font-size:12.8px">The QuickAdd feature is currently hard coded to add items of type 'UserStory'. With no fixed types and no option to change the type this looks wrong.</span></span>
<div>
<div style="font-size:12.8px">> Should the Process Definition have some option to define a 'default' Type that should be used here?</div>
<div style="font-size:12.8px">> Should the Quick Add have an option to select which type it should quick add? Optionally, should the Quick Add remember the users previously used type? Or </div>
<div style="font-size:12.8px">> possible types based on some form of role, e.g. PM's would most likely create Experiences, SM UserStories and Devs Tasks?</div>
</div>
<div style="font-size:12.8px"><br /></div>
<div style="font-size:12.8px"><span>As far as I understood UI and UX, they want to make the quick add bar context sensitive. So when you're viewing a list of user stories, the quick add will just add user stories. But if you're viewing a list of epics, the quick add shall add epics. I have no clue about the technical realization yet but that's at least what I heard from talking to different people. It seems the most convenient to me instead of having some process defining what you can quick add.</span></div>
<div style="font-size:12.8px"><span>The only problem I see is how to get the "context", e.g. how to know that the list of work items is currently just showing features, epics or user types. Shall this be done with filters or maybe implicit filters?</span></div>
<div style="font-size:12.8px"><span><br /></span></div>
<div style="font-size:12.8px"><span>- Konrad</span></div>
</div>
<div class="gmail_extra"><br />
<div class="gmail_quote"><span>On Mon, Jan 23, 2017 at 12:08 PM, Aslak Knutsen <span dir="ltr"><<a href="mailto:aslak@redhat.com" target="_blank">aslak@redhat.com</a>></span> wrote:<br /></span>
<blockquote class="gmail_quote" style="margin: 5px 5px; padding-left: 10px; border-left: thin solid #e67e22;">
<div>
<div class="m_1479773159329925911m_7788017760563137094m_-9193339247053115346m_-2194227522843130956m_-3602276906330631949m_8158092590246300950m_-4169577252385756317h5">
<div dir="ltr">A few points to clear up around the generic type system.
<div><br /></div>
<div>'Epic'</div>
<div><br /></div>
<div>In the UX designs, Epic is special, e.g. it shows up as summary points in the same draw as Iterations and can be created directly from the 'right-click' menu: <a href="https://redhat.invisionapp.com/share/QU9U8D8GF#/screens/212141138" target="_blank">https://redhat.invisiona<wbr />pp.com/share/QU9U8D8GF#/screen<wbr />s/212141138</a></div>
<div><br /></div>
<div>What is the generic term/feature for this? Is the intent to be able to define as part of the Process Template which Type should be the 'special/top' type? What is the equivalent type in the PDD style, Vision/Experience?</div>
<div><br /></div>
<div>Part of <a href="https://github.com/fabric8io/fabric8-planner/issues/657" target="_blank">https://github.com/fabric8i<wbr />o/fabric8-planner/issues/657</a></div>
<div><br /></div>
<div><br /></div>
<div>
<div>'WorkItem Links hierarchy'</div>
<div><br /></div>
<div>Same as a Feature can be a Child of an Experience, a UserStory is a Child of an Epic. What are the Link Forward and Reverse names for this relationship?</div>
<div><br /></div>
<div>Relates to? Belongs to? Child of? Part of?</div>
</div>
<div><br /></div>
<div><br /></div>
<div>'Quick Add'</div>
<div><br /></div>
<div>The QuickAdd feature is currently hard coded to add items of type 'UserStory'. With no fixed types and no option to change the type this looks wrong.</div>
<div><br /></div>
<div>Should the Process Definition have some option to define a 'default' Type that should be used here?</div>
<div>Should the Quick Add have an option to select which type it should quick add? Optionally, should the Quick Add remember the users previously used type? Or possible types based on some form of role, e.g. PM's would most likely create Experiences, SM UserStories and Devs Tasks?</div>
<div><br /></div>
<div><br /></div>
<div><br /></div>
<div>PM's input appreciated. </div>
<div><span class="m_1479773159329925911m_7788017760563137094m_-9193339247053115346m_-2194227522843130956m_-3602276906330631949m_8158092590246300950m_-4169577252385756317m_-3154826624615217480HOEnZb"><font color="#888888"><br /></font></span></div>
<div><span class="m_1479773159329925911m_7788017760563137094m_-9193339247053115346m_-2194227522843130956m_-3602276906330631949m_8158092590246300950m_-4169577252385756317m_-3154826624615217480HOEnZb"><font color="#888888"><br /></font></span></div>
<div><span class="m_1479773159329925911m_7788017760563137094m_-9193339247053115346m_-2194227522843130956m_-3602276906330631949m_8158092590246300950m_-4169577252385756317m_-3154826624615217480HOEnZb"><font color="#888888">-aslak-</font></span></div>
<div><span class="m_1479773159329925911m_7788017760563137094m_-9193339247053115346m_-2194227522843130956m_-3602276906330631949m_8158092590246300950m_-4169577252385756317m_-3154826624615217480HOEnZb"><font color="#888888"><br /></font></span></div>
</div>
<br /></div>
</div>
<span>______________________________<wbr />_________________<br />
almighty-public mailing list<br />
<a href="mailto:almighty-public@redhat.com" target="_blank">almighty-public@redhat.com</a><br />
<a href="https://www.redhat.com/mailman/listinfo/almighty-public" rel="noreferrer" target="_blank">https://www.redhat.com/mailman<wbr />/listinfo/almighty-public</a><br />
<br /></span></blockquote>
</div>
<br /></div>
</blockquote>
</div>
<br /></div>
</div>
</div>
</blockquote>
</div>
<br /></div>
</div>
</div>
</blockquote>
</div>
<br /></div>
</div>
</div>
</blockquote>
</div>
<br /></div>
</div>
</div>
</blockquote>
</div>
<br /></div>
</div>
</div>
</blockquote>
</div>
<br /></div>
</div>
</div>
</blockquote>
</div>
<br /></div>
</div>
</div>
</blockquote>
</div>
<br /></div>
_______________________________________________<br />
almighty-public mailing list<br />
almighty-public@redhat.com<br />
https://www.redhat.com/mailman/listinfo/almighty-public<br /></blockquote>
</div>
</body>
</html>