OK I was wrong above. I just closed an issue directly on the tracker and this is also still being displayed
I do not understand how it can be, but confirmed. The same problem also for JTracker project :(
Labels |
Added:
bug
|
Well just updated the dependencies and have the same issue locally. Seems that again there is some filtering problem. Trying to fix.
thank you for looking into this
On 7 March 2015 at 17:20, Dmitry Rekun notifications@github.com wrote:
Well just updated the dependencies and have the same issue locally. Seems
that again there is some filtering problem. Trying to fix.—
Reply to this email directly or view it on GitHub
#629 (comment).
Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2015-03-07 18:48:24 |
Status | Closed | ⇒ | New |
Wow, I can close issues across organizations and repos
joomla-framework/registry@e15549e adds test cases which reproduces the failure we were htting here and joomla-framework/registry@5c2e607 has the fix for it.
Status | New | ⇒ | Closed |
Closed_Date | 2015-03-07 18:48:24 | ⇒ | 2015-03-07 18:52:58 |
Thanks looks fixed now!
This seems to happen only when an issue is closed at github. I closed a few that way today and this is the result
This comment was created with the J!Tracker Application at issues.joomla.org/jtracker/629.