canonical: https://jentic.com/apis/fecru.local/fecru

# Fecru Fisheye Crucible

Atlassian Fisheye and Crucible expose an HTTP REST surface for browsing source repositories, running code reviews, and administering project-level access. This OpenAPI spec covers 113 endpoints across the rest-service-fecru namespace, including admin groups, permission schemes, user accounts, repositories, reviews, comments, and changesets. Teams running self-hosted Fisheye or Crucible can drive review workflows, group management, and repository inspection programmatically rather than through the web UI.

## For AI agents

Drive Fisheye and Crucible code reviews, repository browsing, and admin operations across self-hosted Atlassian source-management instances.

## Scope

Does not handle issue tracking, build pipelines, or deployment management - use for Fisheye repository browsing, Crucible reviews, and access administration only.

## Capabilities

- Manage admin groups and the users assigned to them
- Configure permission schemes that control repository access
- Browse repositories, changesets, and revisions through the rest-service-fecru namespace
- Open and update Crucible code reviews and reviewer assignments
- Inspect commit history and changeset metadata for audit reporting

## Use cases

### Review Workflow Automation on Self-Hosted Atlassian

Engineering teams running self-hosted Fisheye and Crucible automate the creation and routing of code reviews. The rest-service-fecru endpoints let a CI hook open a Crucible review when a feature branch is pushed, attach reviewers from the right admin groups, and update the review state as approvals come in - without manual steps inside the Crucible UI.

Example prompt: When CI completes on a feature branch, call the Crucible review create endpoint with the changeset IDs and the reviewer list pulled from GET `/rest-service-fecru/admin/groups/{name}/users.`

### Permission Scheme Auditing

Security teams audit which permission schemes exist on a Fisheye Crucible instance and which users belong to admin groups that have elevated access. GET `/rest-service-fecru/admin/permission-schemes` lists the schemes and GET `/rest-service-fecru/admin/groups/{name}/users` enumerates membership, feeding a quarterly access review into a compliance dashboard.

Example prompt: List every permission scheme via GET `/rest-service-fecru/admin/permission-schemes` and enumerate user membership for each admin group.

### Group Membership Provisioning

When new engineers join, they need to be added to the correct admin and reviewer groups. PUT `/rest-service-fecru/admin/groups/{name}/users` assigns members and DELETE removes them, so an HRIS-driven script can keep Crucible group membership aligned with current employment without manual sysadmin work.

Example prompt: On HR onboarding event, call PUT `/rest-service-fecru/admin/groups/{name}/users` to add the new engineer to the engineering reviewer group.

### Agent-Driven Review Setup

An AI engineering assistant can use Jentic to discover Fisheye Crucible's review and group endpoints, open a review for a pull request, attach reviewers from the right admin group, and update permissions for a sensitive repository - all through scoped Jentic credentials rather than direct REST calls.

Example prompt: Use Jentic to search 'list fisheye admin groups' and execute GET `/rest-service-fecru/admin/groups`/ to enumerate the candidate reviewer groups.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/rest-service-fecru/admin/groups/` | List admin groups |
| POST | `/rest-service-fecru/admin/groups/` | Create an admin group |
| GET | `/rest-service-fecru/admin/groups/{name}/users` | List users in a group |
| PUT | `/rest-service-fecru/admin/groups/{name}/users` | Add users to a group |
| GET | `/rest-service-fecru/admin/permission-schemes` | List permission schemes |
| POST | `/rest-service-fecru/admin/permission-schemes` | Create a permission scheme |

## Key resources

- **Admin Groups** — Create, list, and update administrative groups and their members
- **Permission Schemes** — Configure permission schemes that govern repository and review access
- **Repositories** — Browse repositories, changesets, and revisions tracked by Fisheye
- **Reviews** — Open and manage Crucible code reviews and reviewer membership

## Why Jentic

- **Setup:** Wiring Fisheye Crucible by hand means managing its session-based Authorization header and navigating a 113-endpoint rest-service-fecru surface of repository, review, and admin operations yourself. Through Jentic you install once, import Fisheye Crucible from the API Directory, store the session credentials once, and your agent calls it.
- **Permission scoping:** Fisheye Crucible puts the group name in the URL path (`/admin/groups/{name}/users`), so a rule can pin your agent to one group. You choose the operations it may call, so an admin write like adding a group or updating its users is included only when you add it, while group and permission-scheme reads can stay read-only.
- **Credential handling:** Your Fisheye Crucible session credentials are stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list Fisheye admin groups', and Jentic returns the matching rest-service-fecru endpoint with its input schema, narrowing 113 paths to the right call.

## Related APIs

- **Jira** — Issue tracker that pairs with Crucible reviews on the same Atlassian stack
- **GitHub** — Cloud-hosted source control and pull-request review platform
- **GitLab** — Self-hostable source control with built-in merge request reviews

## FAQ

### What authentication does the Fisheye Crucible API use?

This OpenAPI definition does not declare a security scheme; production Fisheye Crucible instances typically require basic auth or a session cookie configured by the server administrator. Through Jentic the credentials are stored in the vault and injected per request.

### Can I manage admin groups with the Fisheye Crucible API?

Yes. GET, POST, PUT, and DELETE on `/rest-service-fecru/admin/groups`/ and `/rest-service-fecru/admin/groups/{name}` cover full lifecycle management of admin groups and their members.

### What are the rate limits for the Fisheye Crucible API?

Self-hosted Fisheye Crucible does not enforce a documented public rate limit; throughput is bounded by the server's hardware and tomcat thread pool. Stagger bulk operations and monitor server response times when running large jobs.

### How do I list permission schemes through Jentic?

Run pip install jentic, search 'list fisheye permission schemes', load GET `/rest-service-fecru/admin/permission-schemes`, and execute it against your Fisheye Crucible base URL to receive the configured schemes.

### Can I add a user to an admin group via this API?

Yes. PUT `/rest-service-fecru/admin/groups/{name}/users` adds a user to the named admin group and DELETE on the same path removes them.

### Does this API support browsing changesets?

The rest-service-fecru namespace exposes repository and changeset endpoints alongside the admin operations covered here, so an integrating service can both browse code history and manage access from the same base URL.

### Can I limit what my agent is allowed to do with the Fisheye Crucible API?

Yes. Because you run Jentic One yourself, your own rules decide which of the rest-service-fecru operations your agent may call. Since Fisheye Crucible puts the group name in the URL path, such as `/rest-service-fecru/admin/groups/{name}/users`, a rule can pin the agent to a single group. You can keep group and permission-scheme reads like GET `/rest-service-fecru/admin/permission-schemes` read-only and add an admin write, such as PUT `/rest-service-fecru/admin/groups/{name}/users`, only when you choose to.