Suggestion: "Allow Read-Only Access to Unity QA Team" option

As the title says, it would be handy to add an "Allow Read-Only Access to Unity QA Team" to the Support section of Collaborate, so as to ease the workflow of reporting issues, where needed.

Currently, we have to use the Repro Project Wizard, which takes time and not always useful for errors that appear on released bits, specially when there is no clue of the scene or scenes that are causing them. Say, native errors from Objective-C that were not present during Debug with XCode.

Imho, such option could simplify things when access to the project is needed.

 

New suggestion added: https://feedback.unity3d.com/sugges...access-to-unity-qa-team-option-to-collaborate

 

Have you looked at the public issue tracker? Among the reasons QA can't be exposed most certainly includes the fact they deal with NDA sensitive reports and projects people consider private.

Maybe I didn't understand.

 

Yes, you didn't. The idea is not to expose what QA is dealing with, but to expose the project you need to send to QA in Collaborate.

Today, when you send an issue, sometimes they need you to send a repro project which ends up to be a stripped version of the game it-self.

So, instead of sending that stripped version of the project to Unity QA, you allow them to access your project in Collaborate with a read-only permission.

 

I have added this comment to the suggestion:

 

I think they already can do that although its on a separate server, you have to talk to them though. Typically for repro without uploading a project (multi gig large projects) you give them an ip address or ftp, or they give you an ftp, and go from there.

The collab idea was suggested before I think, and the reply was it was on a different server.

 

I talked to them and they sent me the link to post the suggestion

EDIT: picture it as adding members to the project in Collaborate with read-only access -until the fix is found- that do not count as employees of your organization. But instead of sending invites, you just click an option, since those temporary members are part of Unity QA.

 

Good to know.

Side note: I had expressed my permission in the wording of the ticket itself and yet was asked to submit a project with the repro project wizard.

 

No, I submitted a bug with the editor, and in the wording I expressed my permission. Then I was requested to send a repro project. So I did. An I'm waiting to know whether they could build it successfully (given that it is a stripped down version of the whole game).