Collaborate == faster bug report ?

Hey,
I posted a thread about list of bugs I have with unity 5.6b. It was closed because I posted all the bugs in one thread.
I’m happy to help and report bugs, but really, I’m not going to post same/many projects as different bug reports because it takes more than 20 minutes each.

I’m just wondering, with the collaborate service - can you access the project files even if we won’t upload them when bugs occurs?

That would be awesome!

Best,
Or

1 Like

There’s a bug report system designed specifically for capturing bug data. If you want the QA people to get the bug data then please just give it via their preferred channel.

I know it sounds pedantic to tell people to only use the appropriate form, but it’s just not practical to have everyone and their dog submitting bugs in different ways. Do you really expect them to check all new forum threads each day in case someone posted some bugs, then manually copy them over to their bug tracking system?

Sit on the other side of a support desk once and you’ll quickly realise that it’s important for people to do things in an orderly fashion, because that job is difficult enough even in that case.

1 Like

The best way to report a bug is via the built-in Bug Report system that is in Unity directly: Help → Report a Bug… (Well, thats the route via a Mac, I can’t remember if its the same on Windows… its likely very similar!)

Thanks guys for the responses.
I just want to clarify - I have 7~ different bugs, if I want to report them separately from the “Bug Report” menu it will take me around 3 hours just to upload my project(it is the same one!), and even more just to explain and doc my steps(and I can’t use unity while it uploading)

I was asking about the collaborate service - since Unity already has my project files in S3, can we save the uploading time?

I’m sure that handling the bugs is a hard work, I did post a report # in my thread. Just trying to make easier because more than 3 hours for bug reporting make people stop reporting)

Can you not isolate the bug into a separate project/example that is much smaller?

I’ve never had any luck uploading a multi-gigabyte project with Unity’s Bug-Reporter tool and I believe it’s a known issue that it does not handle that.

I recommend to ask Unity QA to provide a secure location where you can then upload your project. That’s how I did several times it in the past and it works much more reliable than using the bug-reporter.

My approach was to submit a bug-report via the Unity Bug-Reporter tool, describing the problem, provide steps to reproduce the issue, etc and asking for a secure location where I can upload a x GB project. QA then replied with an owncloud link where I uploaded the project. Once completed, I updated the bug-report that the project is online now.

Ohhh, I see! In that case I think I’d upload it with the first bug report, and include a note with the others to that effect. “See project files uploaded with bug #xxxxxx”. I know that’s not ideal for anyone, but at least it’s within the standardised system and at least it doesn’t involve uploading the same large thing 7 times.

I’m well acquainted with the pains of large uploads on small connections.