Search Issue Tracker

Won't Fix

Won't Fix in 6000.5.X

Votes

0

Found in

6000.0.65f1

6000.3.5f1

6000.4.0b5

6000.5.0a5

Issue ID

UUM-132648

Regression

No

Project Auditor Analysis is not marked dirty when the save file is deleted even after reopening the Project Auditor window

Project Auditor

-

Steps to reproduce:

  1. Create a new Unity project using the Universal 3D template
  2. Import the provided script "NewMonoBehaviourScript.cs"
  3. Open the Project Auditor window (Window > Analaysis > Project Auditor)
  4. Click the "Install Rules" button
  5. Click the "Start Analysis" button
  6. Click the save button and save the Analysis
  7. Delete the save file
  8. Observe the Project Auditor window

Actual results: The Analysis is not marked dirty/unsaved

Expected results: The Analysis is marked dirty/the Analysis title has an asterisk*

Reproducible with versions: 6000.3.5f1, 6000.4.0b5, 6000.5.0a5

Tested on (OS): MacOS Silicon Tahoe 26.2, Ubuntu 24.04

Notes:

  • The Analysis is not marked dirty (does not have an asterisk) even after reopening the Project Auditor window
  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.5.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.