Status Update
Comments
lu...@gmail.com <lu...@gmail.com> #2
There was a typo in your "steps to reproduce" the issue: I've fixed it in the description, tested locally, works as expected.
lu...@gmail.com <lu...@gmail.com> #3
Actually, I repeated the test and, depending on which project is provided, the change can be either found or not found.
lu...@gmail.com <lu...@gmail.com> #4
Found the culprit in ChangeArgumentParser
: even if the change-id format contained also the project name as project~changeNum
, the change resource was created without the project name.
By adding it as changeResource = changesCollection.parse(changeNotes.getChange().getProject(), cId, null);
the problem is fixed.
st...@gmail.com <st...@gmail.com> #5
Comment has been deleted.
Description
Step to reproduce
Expected result
The set-topic command allows one to specify a project.
Observed result
There is no
project
parameter, hence the command returns:warning: "1" matches multiple changes
. It is not possible to set a topic on an imported change.Background
A
project
parameter need to be added to make sure a unique change can be selected