Project issue json needs comment index number included in data structure

Using {project_issue_comments}.comment_number is a better way of getting at that.

I'm not so sure. That table's going away in D7, so it seems short-sighted to depend on that. The dust is still settling on #1632492: Figure out and port project_issue comment numbering functionality to D7, but it seems like in any case, we're still going to use the comment subject field to hold the "#N" comment identifier. If anything, I'd just say we should call it "commentSubject" or "commentTitle" or something, and just let it be what it is.

I like dww's idea to use commentSubject since that will keep working for a long time

Seemed silly to make you re-roll this. I just took your patch from #1 and modified it to rename the key from 'commentIndex' to 'subject'.

At first, I committed/pushed it as 'commentSubject' but then I realized this is all inside a 'comments' subarray, and none of the other properties use a 'comment' prefix on the keys (e.g. the status is just called 'status', not 'commentStatus'), so I changed it to 'subject' for consistency. Sorry that means you'll have to re-roll at #1078108: Drush issue queue commands but that seemed like a better patch to have you re-roll, anyway. ;)

So, committed, pushed, and deployed live. Behold:

https://drupal.org/node/1730728/project-issue/json

Cheers,
-Derek