Search Issue Tracker

Won't Fix

Votes

0

Found in [Package]

2019.4

2020.3

2020.3.24f1

2021.2

2022.1

2022.2

Issue ID

1395956

Regression

No

ChangeSets are not detected when created via Editor Scripts

Package: Version Control

-

Reproduction steps:
1. Create a Perforce server
2. In P4V create a Workspace for the attached "P4NewChangeset.zip" project
3. Open the project and connect to the created Perforce server (Project Settings > Version Control)
4. Create a new ChangeSet via Script (Changeset > Generate)
5. Observe the Outgoing tab in the Version Control window (Window > Asset Management > Version Control)

Expected result: The created ChangeSet can be seen
Actual result: The created ChangeSet is missing

Reproducible with: 2019.4.34f1, 2020.3.26f1, 2021.2.8f1, 2022.1.0b4, 2022.2.0a2

Note: ChangeSets are created properly when created from the context menus of already existing ones

  1. Response avatar

    Resolution Note:

    While certainly not "by design" this seems to have been the behavior of the Unity Perforce integration for a long time, likely since creation.
    A fix would be significant and potentially risky for an issue with a clear workaround (creating the changeset in P4V) versus other P4 integration fixes that seem to impact broader use cases.

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.