Tasks:

Discussion:

• the transition to the next step is a little weird. It should automatically start the user on Create New Survey (instead I had to click create new survey and there was nothing in the survey area.) In fact, I think it would probably be better without the menu on the side. It could just have 3 steps. Step 1 would be "Campaign Info", Step 2 would be "Add Surveys" and Step 3 would be "review campaign". For step 3 you could view the campaign using the menu on the left in the way that it is done now. For step 2 it would let you create multiple surveys and and prompts to each survey. I think that would guide the user through creation in a logical order. (Cameron)

• I think it might make more sense to choose the type of prompt you want to add when you click the "create new prompt button". Maybe instead of a button, we could have a "pool" of prompts on the left hand side of the screen that can be dragged on to the center of the page to add a prompt to a survey. Those prompts could then also be reordered via drag and drop. Although being able to reorder prompts this way might make managing conditions difficult. (Cameron)

• I think it would be better if "Prompt Details" and "Condtion" were not shown to the user the way they are now. Instead, I think the content that is shown in the lightbox when you edit that field should be inlined in the prompt creation form. (Cameron)

• I created a survey and was taken to the prompt list screen, but it was not clear at all that that is where I was. There is also some text "New Item" that, at this point, seems out of place. I see how it works once I start clicking things. This page just needs work. My suggestion would be the creation box not be two expandable boxes. Instead, they should be a lightbox. Also, everything else is a button, but the "Create a new message." and "Create a new prompt." links aren't buttons; it feels like they should be. And they should be at the bottom of the page. It should be kind of like the "Edit Existing Surveys" page. Maybe there should just be a "Surveys" page with an "Add New Survey" button where you add / edit surveys. (John)

• I don't like the "Create Campaign" button not actually creating the campaign. I feel like I should be creating / editing / selecting surveys before I press "Create Campaign". (John)

• I think the first screen where you enter the campaign info is nice I actually don't mind the "Create Campaign" button since the user has no idea that the campaign was not created on the server. To them, they did create the campaign and now they need to add surveys to it. (Cameron)

• Easy:

  • 1. "help" link
  • 1. campaign sugmission status---success and failure cases
  • 1. Remove warning if 1st time choosing the prompt type
  • 1. Make the server configurable
  • 1. after clicking create campaign info, the app should lead to a new survey page
  • 1. Warning message if users click edit survey items while editing any survey info.
  • 1. Warning message if users creating a new message/prompt and navigating away
  • 1. If click edit, the "view only" should collapse and vice versa
  • 1. The tooltip is cutoff because it won't leave its container. (John)
  • 1. the instructions for editing a condition are hard to read. (Cameron)---make a table instead of a list
  • 1. do not check for empty survey until the end
  • 1. Create a "Cancel" button for prompt type modal
  • 1. put symbol of message/prompt before the text "create new message"/"create new prompt"
  • 1. When creating a new prompt, there is a warning dialog box that has some formatting / grammatical issues. Also, it says. "will clear all the data in the current prompt type", which seems like the ID, label, text, etc. will also be cleared. (John)
  • x On the campaign creation page, the "* Required Fields" feels...misplaced? (John)
  • x On the campaign creation page, the "Authors" field can probably be hidden as it cannot be changed. (John)
  • x The "Create Campaign" button should be colored. (John)
  • 1. Should the "Description" be a multi-line text box? (John)---yes and it should be automatically scrollable if the text is larger than the area.
  • 1. The "View Cmapaign XML" lightbox feels unnecessarily small. (John)---make the lightbox bigger
  • 3. If we have time, should but a css style on page header, submit button, cancel button.
  • 1. change survey data to survey info consistently throughout the app
  • 1. move help to the right. put a vertical bar next to the login info, and underscore the help text
  • 3. Screen shot for help page
  • 2. a campaign creation flow diagram to the help text

• Moderate:

  • 1. Create error message on login page
  • 1. Submit campaign directly to the server from Js.
  • 2. If users click edit survey/prompt but have not input anything and navigate away from the page, the app should allow it. But if users did make few changes, a warning should appear (currently a warning appear in both cases).---keep a state of this page (e.g. whether it has been changed), and then check this variable to determine whether to give a warning.
  • 1. If I choose the "Skip Option" checkbox, the "Skip Label" becomes editable, which is great. I see the "Skip" is already in there, which feels like a default option. But, if I click "Add Prompt" it says a required field is missing. This field doesn't have a red asterisk, so I don't think to look at it. It turns out, I cannot just use the placeholder text. (John)
  • 3. For "Prompt Details" for a single-choice prompt, there isn't enough room to see more than 2 options, which just seems odd. (John)
  • 1. for conditions if I choose "specify value", I am only able to choose 0 as the value, but that prompt has two choices, 0 and 1. This is probably due to a different bug that I just noticed where the choices that I specified for that prompt were not saved.. I'm not sure why. Maybe I didn't click save? (Cameron)
  • 1. adding a new advanced condition shows the old condition text from a different prompt. (Cameron)
  • x Creating choice prompts is somewhat confusing. Each row should have a "X" button, but there should be a single "+" button to add a new option. (John)
  • x why does editing the condition generated by the simple option have to clear the value when you go to the advanced option? You should be able to keep what the simple option put there to edit if you want. Going from advanced to simple is more difficult so I can see why you could lose data in that direction. Although maybe it could attempt to translate the advanced condition back to the simple one? And if it fails, show the message that it will be cleared. (Cameron)
  • 2. translate the simple conditional setting to a proper conditional text when change from simple condition to advanced condition. Add a note to say that the current version doesn't support converting from advanced setup to simple setup.
  • 2. integrate login with ohmage login (redirection)... Should be able to copy the code from Jeroen (ohmage teacher git repo). DO a commit to github before performing this work.
  • 3. remove php. Do a commit before performing this task.

• Hard:

  • 4. It would be nice if you could drag and drop to reorder choices and conditions (that would remove the grid of buttons on the left side of the screen). (cameron)
  • 4. Read and edit campaign from the server. Need a conditional parser to support this.
  • x Save campaign and submit to server while editing.