Steps to reproduce:

1. Open an existing issue
2. Quit ShipHub
3. Relaunch ShipHub

Results:
An untitled issue window is visible for each previously opened issue

Expected:
The previously opened issue windows should restore as they were

Hello World

/cc @kogir

Then I'm going to delete my account and see what happens.

There's emojify.js, but that turns them into images. I want to turn them into actual unicode characters and just let the system render them.

• Locked issues should not be editable
• Should be able to view locked state on an issue
• Should be able to lock an issue
• Should be able to unlock an issue

We can't quite do as well as Ship did, but we can use the created_at and closed_at dates along with the current state of the issue to produce useful charts nonetheless.

Right now you can only drag and drop a file (or use the attach button), but not paste one.

The "Close Issue" button in the add comment field could be interpreted to mean "Close this window", not "Add Comment and close the issue in one shot" (which is what it actually means).

Maybe make it red or change the wording?

This sort order could also affect the sort order in the repo completer when filing a new issue (see #20).

Cmd-opt-c: https://github.com/owner/repo/issues/#
Cmd-ctrl-c: owner/repo#
Cmd-shift-c: owner/repo# title

There should be a labels column visible in the IssueTableController. When it is expanded wide enough, it should show all applicable labels. When it is narrower, it should do finder style color labeling (with hover to see names).

• Auto-fill last used repo
• Auto-fill repo from overview context

Saving from within the app

Similar to Ship's:

Most recently used repos should sort to the top of the list.

See also #16 Auto-fill repo field

See also realartists/shiphub-server#26

Steps to reproduce:

1. Open an existing issue
2. Edit the title, but don't leave the title field
3. Press cmd-s

Results:
Default NSDocument save panel appears

Expected:
Document should just save with no panel

Not sure if this is even possible, but it seems like one of those web <=> native uncanny valley things we should shore up.

Steps to reproduce:

1. Create new issue
2. Fill out title
3. Fill out repo

Results:
All input fields lose focus

Expected:
Milestone field receives next focus

Steps to reproduce:

1. Create new issue
2. Fill out title, repo
3. Add a comment
4. Press cmd-s to save

Results:
Add comment text disappears, then after a short delay, the issue body appears.

Expected:
The issue body should appear much more quickly