740135 - Add info next to the "Log In" link indicating how to get a login

Status: RESOLVED WONTFIX

(Socorro :: Webapp, task)

Description

[Jeff Walden [:Waldo]]

If I wanted to view the URL for a crash, or other more-sensitive data than what is currently exposed, I'd need an account to view it.  There doesn't appear to be any indication in the crash-stats UI of how/where to file the bug to get such an account.  A link or something to an appropriately prefilled bug report would be helpful.

(To be clear: I don't have an account now, but I also don't need one, at least not right now.  I was simply triaging a question from someone else about how to get the URL associated with a crash.  I couldn't immediately find the right place to file the bug myself, and it occurred to me that that information needs to be better exposed in crash-stats itself.)

Comment 1

[Robert Kaiser]

I'm not sure if we have any such note on any other service we have - but then, in most, you create a login and then have no permissions, needing to magically (without good docs, quite often) request a permission bit somehow.

That said, if someone wants a list of URLs for a single bug, that person should add the needURLs keyword to the bug, and the CrashKill team will look into that.

Comment 2

[Laura Thomson :laura]

Modify the text that says "you're logged in but you don't have x privileges" - link to wiki page explaining how to get access.

Comment 3

[Peter Bengtsson [:peterbe]]

Another option would be a bugzilla link that has much of the stuff filled in.
I wonder where this should be. People don't read. If the link exists on the Profile page at least we can *say* "Go to your profile page and there's a link to Bugzilla there for getting elevated permissions"

What do you think Adrian || lonnen?

I deal with all these requests and I honestly don't know how people know to file bugs. I think it's done as word-of-mouth tips from within the platform org.

Comment 4

[[DEACTIVATED] Adrian Gaudebert]

I think we first want a wiki page either on wiki.m.o or on mdn with explanations about our permissions. Or that could even be a page in the website, alongside the Super Search API documentation for example, and then we can load the permissions directly from our database (makes maintenance easier). 

And then we can add links to that page from anywhere we want, like the Profile page, or the 403 page.

Comment 5

[Will Kahn-Greene [:willkg] ET needinfo? me]

We have this page, but it's focused on the auth system we're using, so I'm not sure it's relevant:

https://wiki.mozilla.org/Socorro/GoogleAuth

Plus I have no idea if anyone has seen that page or if anyone looking for this kind of information discovered this page in their search. But ... there it is.

A page on MDN seems prudent since that's where all the other docs geared towards the kind of users looking for logins and permissions exists.

Comment 6

[Lonnen :lonnen]

As recently as bug 1288310, Uptime members were updating MDN with documentation about using crash stats: https://developer.mozilla.org/en-US/docs/Mozilla/Projects/Crash_reporting/

There's a line in there saying "talk to Benjamin" which probably still works. A motivated individual may spruce up that page.


Alternatively we could surface permissions, maybe as a table in the profile page. It's a bit unusual to see something like that in a SaaS offering outside of an admin page. I would only pursue this if we decided to handle requests for permissions in the application instead of Bugzilla. This would let us ensure every user had agreed to the latest handlers agreements, but there are currently no plans to implement this.

I'd also be ok with a wontfix.

Comment 7

[Lonnen :lonnen]

guides for using crash-stats exist, tribal knowledge is good enough for now. Until we decide to handle permission requests inside the application I don't think we will go ahead with thinking through this workflow.