Automate Crucible
HumDay reads Crucible’s own published API description and derives 79 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What HumDay can do in Crucible
36 documented operations change something in Crucible.
- POSTAdd a general comment to the review.
/rest-service/reviews-v1/{id}/comments - POSTAdds a reply to the given comment.
/rest-service/reviews-v1/{id}/comments/{cId}/replies - POSTMark the given comment as read for the user used to make this POST.
/rest-service/reviews-v1/{id}/comments/{cId}/markAsRead - POSTUpdates the comment given by the perma id to the new comment posted.
/rest-service/reviews-v1/{id}/comments/{cId} - POSTPublishes all the draft comments of the current user.
/rest-service/reviews-v1/{id}/publish - POSTAdds the given list of reviewers to the review.
/rest-service/reviews-v1/{id}/reviewers - POSTAdd the changes between two files in a fisheye repository to the review.
/rest-service/reviews-v1/{id}/reviewitems - POSTGet the user authentication token.
/rest-service/auth-v1/login - POSTAdds the given list of revisions to the supplied review item, merging if required.
/rest-service/reviews-v1/{id}/reviewitems/{riId}/revisions - POSTThis method should no longer be used, as it uses a POST for a read-only retrieval operation and is provided for backward compatibility only.
/rest-service/reviews-v1/filter - POSTMarks the comment as leave unread to the current user - it will not automatically be marked as read by crucible.
/rest-service/reviews-v1/{id}/comments/{cId}/markAsLeaveUnread - POSTAdds the given review item to the review.
/rest-service/reviews-v1/{id}/reviewitems/details - POSTAdds a review item for each of the supplied crucibleRevisionData elements.
/rest-service/reviews-v1/{id}/reviewitems/revisions - POSTFor the effective user, mark all comments in a review as read (except those marked as leave unread).
/rest-service/reviews-v1/{id}/comments/markAllAsRead - DELETEDeletes the given comment.
/rest-service/reviews-v1/{id}/comments/{cId} - POSTThis method should no longer be used, as it uses a POST for a read-only retrieval operation and is provided for backward compatibility only.
/rest-service/reviews-v1/filter/details - POSTAdd the revisions in a patch to an existing review.
/rest-service/reviews-v1/{id}/patch - POSTImmediately send a reminder to incomplete reviewers about the given review.
/rest-service/reviews-v1/{id}/remind - POSTCompletes the review for the current user
/rest-service/reviews-v1/{id}/complete - POSTUncompletes the review for the current user.
/rest-service/reviews-v1/{id}/uncomplete - DELETEPermanently deletes the specified review.
/rest-service/reviews-v1/{id} - POSTpublishes the given draft comment.
/rest-service/reviews-v1/{id}/publish/{cId} - DELETERemoves an item from a review.
/rest-service/reviews-v1/{id}/reviewitems/{riId} - DELETEDeletes the reply.
/rest-service/reviews-v1/{id}/comments/{cId}/replies/{rId} - POSTUpdates a reply with the given newComment.
/rest-service/reviews-v1/{id}/comments/{cId}/replies/{rId} - POSTCloses the given review with the summary given.
/rest-service/reviews-v1/{id}/close - POSTOld, non-restful name.
/rest-service/reviews-v1/{id}/addPatch - POSTChange the state of a review by performing an action on it.
/rest-service/reviews-v1/{id}/transition - PUTSets the review item specified by itemId with the given reviewItem.
/rest-service/reviews-v1/{id}/reviewitems/{riId}/details - POSTThis call includes the repsonse header that contains the URL of the newly created entity.
/rest-service/reviews-v1/{id}/reviewitems/{riId}/comments - DELETERemoves the revisions given from the review item in the review specified by the id.
/rest-service/reviews-v1/{id}/reviewitems/{riId}/revisions - DELETERemoves the patch with the given id from the review.
/rest-service/reviews-v1/{id}/patch/{patchId} - DELETERemoves the reviewer from the review.
/rest-service/reviews-v1/{id}/reviewers/{username} - POSTUpdate reviews v1
/rest-service/reviews-v1 - POSTUpdate addFile
/rest-service/reviews-v1/{id}/addFile - POSTUpdate addChangeset
/rest-service/reviews-v1/{id}/addChangeset
What HumDay can read from Crucible
These are the operations a schedule or a trigger can watch.
- GETGet a list of all reviews that have been linked to the specified JIRA issue key.
/rest-service/search-v1/reviewsForIssue - GETGet a list of all the users.
/rest-service/users-v1 - GETGet the list of projects that the authenticated user is entitled to access.
/rest-service/projects-v1 - GETReturn a list of Reviews which include a particular file.
/rest-service/reviews-v1/search/{repository} - GETReturn a list of Reviews which include a particular file.
/rest-service/reviews-v1/search/{repository}/details - GETReturns the user's profile details.
/rest-service/users-v1/{username} - GETReturns a list of all repositories.
/rest-service/repositories-v1 - GETGet a list of the actions which the current user is allowed to perform on the review.
/rest-service/reviews-v1/{id}/actions - GETReturn all the comments visible to the requesting user for the review.
/rest-service/reviews-v1/{id}/comments - GETReturns a list of all the items in a review.
/rest-service/reviews-v1/{id}/reviewitems - GETGet a list of the actions which the current user can perform on this review, given its current state and the user's permissions.
/rest-service/reviews-v1/{id}/transitions - GETGet the user authentication token.
/rest-service/auth-v1/login - GETTo ignore a property, omit it from the query string.
/rest-service/reviews-v1/filter - GETSearch for reviews where the name, description, state or permaId contain the specified term.
/rest-service/search-v1/reviews - GETReturns the user details of the user mapped to a committer in a repository.
/rest-service/users-v1/{repository}/{username} - GETGets the given comment.
/rest-service/reviews-v1/{id}/comments/{cId} - GETTo ignore a property, omit it from the query string.
/rest-service/reviews-v1/filter/details - GETGet a list of patches and their details for the given review
/rest-service/reviews-v1/{id}/patch - GETGet a list of reviewers in the review given by the permaid id.
/rest-service/reviews-v1/{id}/reviewers - GETGet all the reviews which match the given filter, for the current user.
/rest-service/reviews-v1/filter/{filter} - GETGet comment metrics metadata for the specified metrics version.
/rest-service/reviews-v1/metrics/{version} - GETGets the replies to the given comment.
/rest-service/reviews-v1/{id}/comments/{cId}/replies - GETRetrieves all reviews that are in one of the the specified states.
/rest-service/reviews-v1/details - GETReturns Crucible version information.
/rest-service/reviews-v1/versionInfo - GETGets a list of all the reviews that match the specified filter criteria.
/rest-service/reviews-v1/filter/{filter}/details - GETGet a single review by its permId (e.g.
/rest-service/reviews-v1/{id} - GETGets a list of completed reviewers.
/rest-service/reviews-v1/{id}/reviewers/completed - GETReturns a project description.
/rest-service/projects-v1/{key} - GETGets a list of reviewers that have not completed the review.
/rest-service/reviews-v1/{id}/reviewers/uncompleted - GETReturns detailed information for a specific review item.
/rest-service/reviews-v1/{id}/reviewitems/{riId} - GETRepresents a sorted list of changesets, newest first.
/rest-service/repositories-v1/changes/{repository}/{path} - GETReturns the specified review.
/rest-service/reviews-v1/{id}/details - GETFor backward compatibility we provide this method, but repositories should be referred to just by their key.
/rest-service/repositories-v1/{repository}/svn - GETReturns the raw content of the specified file revision as a binary stream.
/rest-service/repositories-v1/content/{repository}/{revision}/{path} - GETLists the contents of the specified directory.
/rest-service/repositories-v1/browse/{repository}/{path} - GETRepresents a particular changeset.
/rest-service/repositories-v1/change/{repository}/{revision} - GETRepresents the history of a versioned entity.
/rest-service/repositories-v1/history/{repository}/{revision}/{path} - GETRead reviews v1
/rest-service/reviews-v1 - GETRead general
/rest-service/reviews-v1/{id}/comments/general - GETRead versioned
/rest-service/reviews-v1/{id}/comments/versioned - GETRead repository
/rest-service/repositories-v1/{repository} - GETRead comments
/rest-service/reviews-v1/{id}/reviewitems/{riId}/comments - GETRead path
/rest-service/repositories-v1/{repository}/{revision}/{path}
How automating Crucible works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live Crucible account.
- Grant access, then go live. You approve the specific Crucible operations it may use — and only those.
Automate Crucible with these
- OData for namespace microsoft.graph11412 operations
- GitHub811 operations
- Atlassian The Jira Cloud platform474 operations
- Gitlab358 operations
- JIRA 7.6.1324 operations
- Appcenter App Center Client323 operations
- Gitea .321 operations
- Bitbucket292 operations
- Keycloak Admin281 operations
- Apple App Store Connect251 operations
- Files.com222 operations
- Vmware vRealize Network Insight Reference161 operations
Categories
Questions about Crucible automation
- Can HumDay connect to Crucible?
- Yes. HumDay reads Crucible's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 79 operations are documented.
- Do I need to write code to automate Crucible?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Crucible account.
- What can HumDay do in Crucible?
- 36 of the 79 documented operations change something in Crucible, and 43 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Crucible account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Crucible is held behind that approval.
Where this came from
The operations above are read from a published API description for Crucible at docs.atlassian.com/fisheye-crucible/latest_backup/wadl/crucible.wadl. Descriptions are the provider’s own words, not ours. Last published 2018-11-21.