Re: project.webplatform.org UX

So, it looks as if the forms were either configured by someone else in the
last two days or I/someone trimmed down the fields a long time ago and
forgot. However, turning visibility off isn't hiding them from the
front-end view. So I need to look into the template and see if there is
some logic that needs to be reworked to get them to not show.

The issue listings are turned back off for now. I will re-activate those
once a trigger is in place so they are collapsed by default with an option
to expand a panel to get the issue lists.


On Fri, Sep 27, 2013 at 7:58 PM, Jonathan Garbee
<jonathan.garbee@gmail.com>wrote:

> I'll take a look at the configuration in the next day or two. If I recall
> how the form system is setup it will mean either editing each project's
> forms individually or each report types. It Will really come down to asking
> only the fields we really require for things. i.e. Time spent isn't really
> a good field to have in most situations.
>
> However, there are things like Owned by and Assigned to which normally
> doesn't fit into a good use-case for general content issues. With the
> structure of getting a content milestone done though there is a good use
> for each of these. So we may need to create a new issue type just for
> milestone task tracking. I will start with cleaning up the default forms
> and we can discuss what exactly we want for specific content milestones
> once that is finished.
>
> One other thing I am going to do right now is turn off the issue listings
> on the homepage. It adds a lot of extra stuff in the way and makes getting
> to the project you want to a bit harder. I am going to look into writing a
> script to hide the issue listings and show/hide them on some button click.
> That way it is there, but tucked away.
>
> -Garbee
>
>
> On Fri, Sep 27, 2013 at 12:58 PM, Julee Burdekin <jburdeki@adobe.com>wrote:
>
>> Hi, Renoir:
>>
>> Again, thanks much for fixing that irritating time-out, sendmail bug!
>> That was really the only real crasher that I know of.
>>
>> I didn't mention in today's meeting, but wanted to call out, the UX is a
>> bit of a hurdle for folks. There are irrelevant, duplicate, and weird
>> workflows within project.webplatform.org. We had planned on
>> consolidating & culling the various fields for the various UI choices, but
>> never did. This would be great to do before we start using
>> project.webplatform.org to manage content projects, such as the
>> up-coming JS project.
>>
>> I filed a bug about this.[1]
>>
>> Regards.
>>
>> Julee
>> [1] http://project.webplatform.org/prmg/issues/PRMG-32
>> ----------------------------
>> julee@adobe.com
>> @adobejulee
>>
>
>