-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please lock sourceforge trackers against creating new tickets #11
Comments
On Tue, 15 Mar 2022 at 21:21, Olly Betts ***@***.***> wrote:
We've had a few tickets created in the SF trackers since switching to
github, which isn't a good experience for users as nobody is regularly
checking them (I've only noticed because I've been checking the old issues
to close duplicates and those fixed since, and to actually address the
low-hanging fruit.
In particular we've had two this week - I closed one as already fixed and
the other with instructions to report to github instead, but it's not a
good use of my time.
@wsfulton <https://github.com/wsfulton> Can you remove "User Permission"
to "create" from "Authenticated"? Or give me (I'm "olly" there) Admin
rights so I can?
Hi Olly
Makes sense. I added you as an administrator in SourceForge. Also changed
as requested, so now we have:
[image: image.png]
Authenticated and Anonymous users had 'create', it's gone now. Bit
confusing as the tooltip indicates that they don't have create permissions.
Feel free to tweak further.
Thanks
William
… Message ID: ***@***.***>
|
Thanks. I've similarly adjusted permissions for the patch and feature request trackers, and removed a more "global" create permission just in case that interacts unhelpfully. I also added messages redirecting people to github (not sure if people can actually get to a page when they're shown now though). |
Sounds good, thanks.
…On Thu, 17 Mar 2022, 00:28 Olly Betts, ***@***.***> wrote:
Thanks. I've similarly adjusted permissions for the patch and feature
request trackers, and removed a more "global" create permission just in
case that interacts unhelpfully. I also added messages redirecting people
to github (not sure if people can actually get to a page when they're shown
now though).
—
Reply to this email directly, view it on GitHub
<#11 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAV6YL3KTSSHQTKJFQY56JDVAJ4CPANCNFSM5QZ7OJBA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We've had a few tickets created in the SF trackers since switching to github, which isn't a good experience for users as nobody is regularly checking them (I've only noticed because I've been checking the old issues to close duplicates and those fixed since, and to actually address the low-hanging fruit.
In particular we've had two this week - I closed one as already fixed and the other with instructions to report to github instead, but it's not a good use of my time.
@wsfulton Can you remove "User Permission" to "create" from "Authenticated"? Or give me (I'm "olly" there) Admin rights so I can?
The text was updated successfully, but these errors were encountered: