Search Issue Tracker

Won't Fix

Won't Fix in 6000.6.X

Votes

0

Found in

6000.0.75f1

6000.3.15f1

6000.4.6f1

6000.5.0b7

6000.6.0a5

Issue ID

UUM-142154

Regression

No

Search Default option for Column Format does not reset the column's format

Search

-

Steps to reproduce:

  1. Create a new project
  2. Open a search window
  3. Enter any query that returns results (p: dir="Assets")
  4. Switch to Table view
  5. Observe that Description entries are listed as expected
  6. Right-click on the Description column name
  7. From the Column Format menu, select any unsupported format (For instance - Material Property)
  8. Descriptions disappear as expected due to an invalid format being set
  9. Right-click on the Description column name again
  10. Select the Default option

Actual results: Description column format remains invalid

Expected results: Description column format is reset to the default value

Reproducible with versions: 6000.0.75f1, 6000.3.15f1, 6000.4.6f1, 6000.5.0b7, 6000.6.0a5

Tested on (OS): macOS 26.4.1, Ubuntu 22

Notes:

  • The issue can be worked around by manually selecting a supported format
  1. Resolution Note:

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

  2. Resolution Note (6000.6.X):

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.