avatar brianteeman
brianteeman
27 Nov 2013

Looks like sometime around issue 200 issues created here stop being created over at github.

In addition if you try and edit an issue here (that is not on github) you get an invalid issue error message

avatar brianteeman brianteeman - open - 27 Nov 2013
avatar mbabker
mbabker - comment - 27 Nov 2013

Where was this issue created from?

avatar b2z
b2z - comment - 27 Nov 2013

@brianteeman can you provide an examples of these issues please?

avatar brianteeman
brianteeman - comment - 27 Nov 2013

There was a filter set over at github that I didnt spot that prevented the issues being displayed (facepalm)

However when I tried to edit issues 230 I got an error
0 RuntimeException
Invalid Issue

If you look at the issue (on issues.joomla.org) you can see the changes recorded but they are not reflected in the issue itself

avatar b2z
b2z - comment - 27 Nov 2013

I got it now. Looks like it is connected with the #228. Some sync issues may be, hard to tell :( It's the beast of @mbabker and @elkuku :skull: Hope they will fix it :muscle:

avatar brianteeman
brianteeman - comment - 27 Nov 2013

OK I will close this issue then as it was a combination of my own PEBCAK and a known issue

avatar brianteeman brianteeman - change - 27 Nov 2013
Status New Closed
Closed_Date 0000-00-00 00:00:00 2013-11-27 13:57:49
avatar brianteeman brianteeman - close - 27 Nov 2013
avatar brianteeman brianteeman - close - 27 Nov 2013
avatar elkuku
elkuku - comment - 27 Nov 2013

On the PEBCAK - also happens in front of my keyboard on GitHub...

And it is starting here because always either the "open" or "closed" filter is active.
I think we really should start to group filters into an "area" that is visible only, and highlighted somehow, if any filter is active. - To avoid those PEBCAKs ;)

Add a Comment

Login with GitHub to post a comment