New Issue Tracker - Bugs are public.

Wow, i've been asking for this for years, glad to see its finally made it.
Hopefully it will help everyone in terms of finding if an issue is a known bug or not and save time writing up bugs that have already been reported.

The addition for being able to vote for a bug is interesting, not sure quite why its there, afterall a bug is a bug and they all need fixing, but maybe it will allow some old legacy bugs to be given more attention now.

Somewhat disappointed that only bugs without private information will be made public. I can understand the need for keeping information private, but it suggests that some bugs may never be entered into this public resource which kind of defeats its purpose. Hopefully this is an issue that can be addressed in the future, such as allowing bug reporters to state if the bug report can be made public (default would be private) or that QA could create a public version of a private bug just to get the details of the bug into public awareness.

I'm also disapppointed that only confirmed bugs will be added too, again seems to defat the purpose a bit, especially now that you have a public face for the bug reporter, as unconfirmed but real bugs could gain support information from the wider Unity community. Again I would hope that this would also be addressed in the future.

However overal this is a huge step in the right direction and i'm thankful for Unity investing the time to get this done.


Edit: Sorry Aurore that I edited my post as you were replying.

 

Well, this is huge.

Astronomical, Colossal, Cosmic, Enormous, Galactic, Gargantuan, Giant, Gigantesque, Grand, Humongous, Immense, Massive, Mega, Mighty, Monumental, Prodigious, Super, Super-Dupe, Tremendous.

I think I've said it all.

Thank you Unity.

 

Awesome! Going to hunt some bugs now and vote them up.

Does the search exclude fixed bugs and include category pages on purpose?
Edit: It seems many results are suppressed/not shown if you search for a keyword like "collision". Maybe not cached yet?

 

you should've kept the extreme name. would help to reach the younger audience lol

 

Just saw the tweet.

All I can say is: \(ツ)/

 

Grats and Thanks!
Gigi

 

My question is why is there open bugs from 2012 ACTIVE still in there?

 

Should you get your votes back automatically once an issue has been fixed? Or is it once it's released?

Like: http://issuetracker.unity3d.com/issues/build-performance-drops-after-building-in-4-dot-3

I didn't get my votes back but it's no longer active.

Thanks.

 

I have just realized I can take my votes back by myself.
PS: and vote for the fixed bug again

 

Yeah, it`s much friendlier to simply ignore the bug reporter instead. Letting him hope that there will be a fix for version 2.6 while he uses Version 4.3 now ...

*ironymode off*


Nobody will fix such old bugs. And nobody expects to get bug fixes for such old bugs. I would suggest to make a hard reset with the bugs. Close all bugs before version 4. They will not be fixed anyways. It makes really no sense to keep bugs from version 1.5 active.

Huh? Sounds to me as the perfect system to prevent further votings ...

 

@Aurore, you mention "search". Can't see a txt search field - just those drop downs. I probably wouldn't never check if somebody already submitted a bug i hit as it just takes to much time browsing the categories.

 

I sent a bug report, received a confirmation a week ago that it has been reproduced and still no track of it on the issue tracker even if it's set to public. Should I be worried?

 

I'd like an issue tracker tab in the Unity Editor so we remember to check status. It'd also be nice if bugs over 2 years old were closed as OCBE.

 

I've submitted a bunch of bugs to FogBugz and none of them are in the Issue Tracker. One of them is fixed, the rest are absolutely reproducible (except maybe the crash report):

• 722975 Editor Startup Errors Open 8/27/2015 1:58 PM
• 716908 CLS Compliance Open 8/3/2015 12:19 AM
• 716733 Vector3 ambiguity with magnitude and sqrMagnitude Open 8/1/2015 7:30 PM
• 715745 No horizontal scroll bar in Hierarchy Open 7/28/2015 8:49 PM
• 712521 [FIXED] Docs: Material.SetColor Open 7/15/2015 8:02 PM
• 710245 Crash Report Open 7/7/2015 3:29 PM
• 708896 Build Settings - Headless Mode Hidden for Windows Platform Open 7/1/2015 1:29 AM
• 673872 Please add support for the following Open 2/20/2015 12:19 AM
• 666573 user submitted bug Open 1/25/2015 10:18 AM

 

It's not rude...it's reasonable. There's even some back to 2009. Begone with them.

 

Begone with them, I agree with you....

If Unity did not fix them for Unity 4.6 before end of support, then why bother displaying them and making a big pile.
You had plenty time to fix them, again is this some kind of QA tactic being used.
Anything before Unity 5x series should be rechecked and closed.

And by the way you did a poor job of last Unity 4.6 patches which included hardly anything.
If you going to stop 4.6 support then do it with style.

 

My first bug reported doesn't exist in the bug tracker too.

 

I dont think they appear unless someone moves them there, or we have hundred/thousand bug reports..

 

A heads up: The mail I got back from submitting a bug had a '.' at the end of the link to the bug which carried over into the browser and resulted in a "Case not found. No case was associated with the ticket."

Remove the . at the end of the link in the address bar and you can see your bug. Should be fixed to avoid confusion.

 

I'm trying to follow the status of this Unity issue, it looks like it's been marked fixed but it's not clear which version of Unity the fix was included with or if/when it will be included in a future version. Is there a way surface that information?

https://issuetracker.unity3d.com/issues/embedded-binaries-function-in-xcode-manipulation-api

 

Why is there no way to file a bug report on the IssueTracker? There is an issue marked as resolved that is still occurring in 5.6.1f1 with the InputField caret not being visible, but it is marked as fixed and there is no way to re-open it or re-report it via the IssueTracker. What is the point of a public system if the public can't provide any input other than to vote on issues to affect the order in which they are fixed? I appreciate the gesture, but ultimately it is only that.

 

You can report a bug via the built-in Unity Bug Reporter: Help -> Report a Bug. If you believe that your bug has something to do with an existing fixed one, just mention it in the description.

People may submit bug reports with sensitive information that is not meant to be public, so the Issue Tracker is kind of a public wrapper around the internal bug tracker.

 

I reported tons of bugs already and they never appeared on Issue Tracker. I have some very urgent ones waiting for a fix (1108407).

What do I need to make a bug reported appear on Issue Tracker?

 

I know is an old thread but in case anyone asks.. (forgive the maybe bad english)

When I send bugs, I'm careful to write perfectly the way to reproduce the issue, maybe adding screenshots or videos.

To me they reply about after a month, and like I said before, writing well the way to reproduce the issue, lead to the quick recognization of the problem (because they don't need to reply requesting more informations (and also after given, they can reply you weeks later)).


They reply usually in two following ways:

1. Is not a bug but your mistake, and they explain you why you are getting the error and usually they give you at least the information to fix it.

2. They recognize it as a bug and they send you the link of the bug in the issue tracker.

PS. Be careful to the explainations in the first point. Sometimes it happened to me that they explain to me the error and the fix, also if it was a bug (so they explain me the workaround without recognize it as a bug). In this case, I reply with an email specifying that by the explanation it was a bug. Then they recognize it as a bug and send me the issue tracker link.


My experience is based on about twenty reports (of which at least half are recognized as bugs)

 

Completely agree with you. Had one question, for the bugs that were recognized? Did you find they got resolved? If so can you give man an idea how how long it took? I realize the timeframe will be wildly different for different bugs, but just want to get some idea, that all.

 

This article should talk about how Unity decides which bugs to fix first (the article is from 2016 I don't know if they updated the system) (https://blog.unity.com/technology/a-look-inside-tracking-bugs-by-user-pain)

However, I really don't think I can tell an average resolution time based on my reports. The only thing I noticed (I repeat, based on a few reports so it may not be totally correct), is that bugs like crashes were solved in a short time (a few weeks or a month from the recognition), while bugs like those of editor that do not affect the game, a report of mine is still planned and was recognized 6 months ago, some have been declared as "postponed" because they require a larger update, a couple more were first recognized as bugs, then they have said they were "By design" or that they would not be solved because a different solution was already available in a major version (like 2020 => 2021) and maybe the circumstances did not consider an update even on the minor version important (it happened to me only in a report), others are recognized but they do not give you an Issue Tracker link but they just tell you that they have tracked them internally and there you do not even know if or when they will solve it, etc..

As for the errors of individual packages, I think that writing on the relevant forum can be useful, because often the developers of the Unity package look at those forums and if you show them the bug (perhaps already recognized), if it is an important bug maybe sometimes they may be more likely to fix it sooner (at least that was my feeling).

These are my considerations

 

Wow. Thanks for the detailed reply. Much appreciated it. I'm hoping for a bug fix on a bug I reported, that's why I was asking. Very informative.