@Jesse: Thanks for the quick reply and I'm hopeful that issues will be
public-public (accessible without login / indexable by Google) really soon.
It might have just been bad luck on my part that I was unable to access the
selected issues. I don't recall the exact URLs now, but if I see it in th
Hey Attila, that's certainly not how the issue tracker is supposed to be
set up; everything except the stuff in "GCP Private Issues," which
corresponds to the old tracker's "Production" issue type, should be
viewable by anybody logged into any Google account. Can you give me a
couple example issue
BTW, it seems to be worse than I expected!
I was catching up on all the discussions in the group and it seems that I
can't access any of the issues I didn't create! So even if I have a direct
link from the group saying "I created this issue", I can not look at it! So
any chance of collaboration
PS. Just some additional semi-related information for those interested:
Monorail is OSS and runs on App Engine.
https://chromium.googlesource.com/infra/infra/+/master/appengine/monorail
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To u
I don't understand why Google didn't just migrate to Monorail.
https://bugs.chromium.org/hosting/
I've noticed a few other minor problems, like the unchangeable default
setting being issues assigned to you, which obviously yields no results for
non-Googlers. Also you can filter by clicking on c