Closed (fixed)
Project:
Usability Testing Suite
Version:
6.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
17 Sep 2008 at 15:52 UTC
Updated:
9 Jun 2009 at 16:30 UTC
As its beta-2 already, we should be working towards a 1.0 version. I will put down a list of interface elements that need to be finished before we throw out a 1.0. Boombatower can you say what you need to do before a 1.0 code wise?
All of the other interfaces still need quite some work, but are not necessary in need of a lot of work to serve there goal.
Comments
Comment #1
boombatower commentedCodewise I think it is were I want it to be.
Comment #2
Bojhan commentedOne notion on the code which I do think is necessary, when you create a task you have to save, and then record. Is it possible to this at once, so as you create a task you somehow save it(AJAX?), so you don't have to click save, in order to record a task. Because its kind of a broken interaction, which I think should be solved - for me to push the create a study page.
Comment #3
boombatower commentedI have some time away from school and I will attempt to get everything that needs to be done for 1.0 and possible more if I have time. Can we patch up what you are looking to have done with issues so that I know what to complete.
#2: I'm not sure that creates a more consistent interface since that adds a number of edge-cases. For instance when you press record the task is "save"? or just kinda hanging there waiting for you to finish recording? If I were to decided I don't want to create the task and navigate away and then come back to create a task should it fill in the previous values? Not to mentions the extra/interesting code that would need to be written to accomplish something like that. I would vote for leaving it alone until we have a better idea, especially with #351460: Record ideal path in base environment if specified
Please confirm the issues and provide any corrections.
Comment #4
Bojhan commentedParticipant UI has upmost priority, after that Creating a Study UI #320222: Create a study/task workflow - not 307846. Both should have finished mockups in them (if you need the PSD's ping skilip on IRC)
Analyze Dashboard
Study Dashboard #307946: Study Dashboard
Task DashboardParticpant Analysis (Leave this one for later - you can display what we do now the form data, and paths)
#2 Well the thing is, no one will press Save before Record unless we implicitly tell them to - its a counter intuitive interaction. So saving the task when you click record - for the user looks like the same thing (they will complete the form anyway). For the edge case that they don't, I think its a trade off we have to make (for now atleast).
Comment #5
boombatower commentedAlright, I'll look into #2 a bit more.
So are these the issues to tackle?
#307518: dashboard with studies
#305806: Improve UI for Participating User
#352389: Update e-mail sent when new environment is created
#307946: Study Dashboard
#320222: Create a study/task workflow
#351735: Fix filtering issues with analysis by session
#351657: Change record ideal path workflow
#358634: Improve Link to Graphs on Study dashboard
#351500: Create howto screencast
Comment #6
Bojhan commentedSounds right, with the how-to I will only cover Creating a study and part of the participant ui. Not the Analyze UI.
Comment #7
webchickHow the heck was I not subscribed to this?! Subscribe. :)
Comment #8
boombatower commentedIf we decide to hold on #320222: Create a study/task workflow as I'm not sure we have a workable solution, and may take a bit to figure out how we want it to work then I can release a 1.0.
So Bojhan please respond on that issue and if we hold on it then go ahead with the screencast.
Comment #9
boombatower commentedI can role a all-in-one tar.gz to make it easier to get dependencies.
Although I think ideally we should try and get something like usability.drupal.org or uts.drupal.org with this setup so that global (Drupal) studies can be conducted in one place.
Comment #10
Bojhan commentedIf you can roll a all-in-one tar.gz it would be great, not sure how far we can get that second idea yet.
Comment #11
boombatower commentedI have rolled a release candidate 1.
I currently do not have the time to implement the kind of ajax interface requested for study/task management. The system works perfectly fine currently and since it will primarily be used by Bojhan and others who should be able to understand the much improved work flow I think we can make a release candidate.
@bojhan: If you are fine with calling this a 1.0 then go ahead and create the howto screencast to be included in 1.0 release.
Comment #12
Bojhan commentedI am currently deeply busy with planning and organising the usability sprint, but I think you can roll a 1.0 without the screencast. I simply don't have time to do one right now, and I dont think its worthwhile to make a screencast on an interface that is not ready yet.
Comment #13
boombatower commentedAs we discussed in previous IRC chats, the study UI will be included in UTS 1.1. This seems like the proper way since we have a fully functioning suite with a RC which should contain all features.
I have completed all other issues, per #5. We just need the #351500: Create howto screencast before I can release.
EDIT: I guess it could be an annoyance to have to create the screencast again, so I'll just hold off on 1.0 and we can break the RC protocol.