I have written a tool that plugs into P4V that allows the user to selected a shelved CL and trigger a Jenkins job.

I trigger the jobs remotely adding the following 2 parameters (to all the other parameters)
review=shelved CL number from P4V
status=shelved

From the example below, i can see the job does a sync and then does the unshelve

SCM Task: syncing files at change: 73544
... sync c:\jenkins2\workspace__sdmos_sdmos-int_3/...@73544
... force update false
... bypass have false
SCM Task: unshelve review: 73478
... sync c:\jenkins2\workspace__sdmos_sdmos-int_3/...
... unshelve -f -s 73478 c:\jenkins2\workspace__sdmos_sdmos-int_3/...
... revert -k c:\jenkins2\workspace__sdmos_sdmos-int_3/...
listing changes: //__sdmos_sdmos-int_3_jenkins_p4_mlb-gb-mlb-dt-007/...@73478,73544

so far so good.

But when i look at the changes pages the unshelved changes are missing.

I do get a
"No connection to Perforce." entry in the changes.

Looking at the code:
in the P4ChangeSet\index.jelly

I can see:
<j:forEach var="entry" items="${it.history}" varStatus="loop">

<j:choose>
<j:when test="${entry.id == null}">
No connection to Perforce.
</j:when>

Please note that i am not using the "Review" action.

So:
1) Either there is a bug
2) Me triggering the job remotely using review+status=shelved is incorrect