A question raised - during implementation I have commented out the GitHub's new issue submit feature and made only local submissions. But these new issues did not show on the issues list of the project though they exists in the issues table as well as activities. Is it a bug? And what is the point to allow the submissions without the GitHub authorization (I mean this one)?

And what is the point to allow the submissions without the GitHub authorization (I mean this one)?

The idea here is to allow "projects" that are only managed in JTracker but not in GitHub (e.g. a security tracker)

But these new issues did not show on the issues list of the project though they exists in the issues table as well as activities. Is it a bug?

I remember that the issue_id for new issues is retrieved from GitHub while for "non GitHub projects" it must be generated (I believe this is still a @todo )

Thanks @elkuku, now it's clear.

So :) Good to merge? ;)

Code wise I don't see why not. Unfortunately I haven't pulled it down to test, but it reads well.

@elkuku what do you think? Good to merge?

On your demo server, David and I noted a small issue. On the closed filter, the Date Closed column is hidden, but visible on the open filter. Still checking out the rest, but looking sharp

Hehe, silly me. This code is the reverse problem:

if ($('#filter-status').val() == 10) {
        $('.date-closed').hide();
};

Should be:

if ($('#filter-status').val() == 1) {
        $('.date-closed').hide();
};

Thanks will fix it :)

Yeah We are moving forward I still hope to release v1.0 in December :)