UI glitches

[ahmadia]

General Layout

• The add buttons are on the top, but the data layouts are in a lower pane. Should the "add" buttons be inline with the data sections (Add Crawl down under crawls, Add Dataset under datasets)
• Failed crawls show up on status panel (main page) as "NOT STARTED"
• View button on far right of crawls is same link as crawl name. Redundant?

Add Crawl

• Add crawl modal "create" button is unresponsive if trying to add a crawl with the same name as a crawl from another project (why?)
• The add crawl modal takes too much space. The description/URL fields should be smaller.
• Entering a seed list and uploading seeds will only result in seeds being uploaded
• Newly created crawls don't immediately appear
• The "visualize" icon goes to a generic Kibana dashboard, instead of something specific to the crawl
• The "rounds" selector uses too-small arrows
• It's not obvious how to control a crawl after creating one. A crawl can't be launched in its creation modal.

Running Crawls

• Failed crawls cannot be "reset"
• Exclamation mark triangle symbol next to rounds. What is it for?
• logio doesn't work on Vagrant
• Tooltips jumble if the user clicks on stop/start/restart
• Stop crawl action stays in FINISHING state, but never interrupts crawl

Adding Datasets

• Adding a new dataset is not modal (datasets don't appear after they're added, a refresh is required)
• Uploaded datasets provide no context
• Uploaded datasets can be reuploaded (this makes no sense)

Adding Crawl Models

• Uploaded crawl models provide no context

[brittainhard]

@ahmadia

Add crawl modal "create" button is unresponsive if trying to add a crawl with the same name as a crawl from another project (why?)

There should be an error that shows up under the field which says "this field must be unique". It's a bug if this is not happening.

Newly created crawls don't immediately appear.

This is also a bug. Newly created crawls need to show up in the crawl table immediately after they are created.

If you can try these out again and create issues with errors from the javascript console, that would be great. Also if you could give me an idea of what browser you were using and what system you were on when these happened, that would also be great.

These are the only two things here that I would classify as bugs.

[ahmadia]

Will do.

[ahmadia]

@brittainhard - Let's review this again when we're both in the office this week.