I ran through a quick test in a Jive Cloud instance and was able to remove a share via the "remove" link available through the breadcrumb:
As such, if you are seeing this option not working in your instance I would suggest submitting a support case in your customer group here in the Jive Community so that additional investigation can be conducted in your instance by the next available support engineer.
That being said, if you are wanting to instead use the API services, I would suggest checking out the Finding the Content ID and Place ID using Jive v3 API document in our Jive Knowledge Base space as this might be helpful.
Additionally, if you have API related questions I would recommend reaching out to the Jive Developers community as there you can collaborate with other developers on potential customizations utilizing the API endpoints.
I have already submitted a case, and a bug has been logged since you cannot access the breadcrumbs in 2015.2 - JIVE-59700
I understand how to get the content id with the API, but I have been unable to access the share information for the content item so that it can be removed.
This discussion was originally posted in the Jive Developers community, but after a week with no response I clicked the "Create a case" link on the side.
cc: Erin Cleary
Thanks for the update. Looking at the bug notes for JIVE-59700, there are no current workarounds listed. However, I ran through a few tests to see if this could be accomplished through the current API endpoints. While I found a couple of ways to get the "shareID"
1. Navigate to the user who shared the content's inbox, for example:
2. Or you can perform the same via the /inbox rest service (Jive REST API v3.12 → Inbox service - /api/core/v3/inbox?objectType=share).
Unfortunately, it looks like running a "DELETE" call against the share API endpoint only removes the inbox entry since shares to places are not currently available through the V3 API endpoints.
Thanks Jesse for looking into this further. I am trying to clear up a group from where users have shared random content, and there just isn't a way to do that. It's a bit frustrating. Hopefully they can get a fix soon.
Erin Cleary - This is another issue that I'd like to see fixed in the next release.