- How do I install lesstif/php-jira-rest-client in a Laravel application?
- Install it with Composer using composer require lesstif/php-jira-rest-client. The package is framework-agnostic, so Laravel does not need a package-specific service provider just to use it. Create a config/jira.php file, bind a configured client in your own service provider or container binding, and read host and credential values from environment variables.
- Does lesstif/php-jira-rest-client support Laravel 10 and Laravel 11?
- The package is framework-agnostic and does not ship Laravel-specific version constraints, so compatibility depends mainly on PHP and Guzzle or PSR-7 constraints in your lock file. Check its composer.json against your Laravel dependency matrix and run composer update in a branch before upgrading. Because it bypasses Laravel's Http facade, version support is more about shared dependencies than Laravel APIs.
- How do I authenticate to Jira Cloud vs Jira Server with this package?
- Jira Cloud typically uses Basic Auth with your Atlassian account email and an API token, while Jira Server or Data Center commonly uses a personal access token. The package supports Basic Auth and configurable Jira API endpoints, so you provide the correct host and credential pair in configuration. Do not hard-code credentials; load them from environment variables or config/services.php.
- Does lesstif/php-jira-rest-client support OAuth 2.0 (3LO) for Jira Cloud?
- The package description only claims Basic Auth with configurable endpoints and does not claim OAuth 2.0 (3LO) support. That matters for distributed or multi-tenant Jira Cloud apps, where Atlassian increasingly requires OAuth 2.0. If you need 3LO, plan to handle the OAuth flow and token refresh yourself or use a client that supports it.
- How do I work with Jira custom fields using this PHP client?
- Custom fields are addressed by raw field IDs such as customfield_10010, and those IDs differ between Jira sites. Store the mapping in configuration, for example config/jira.php, and translate domain field names to Jira IDs in your gateway layer. This keeps field ID changes out of application code and call sites.
- Does the package handle JQL search pagination and field selection?
- The client exposes JQL search and common issue operations, but you should verify pagination handling with startAt and maxResults plus field selection in the version you install. In practice, pass startAt, maxResults, and fields explicitly and loop until the returned total is reached. Wrapping search in your own JiraGateway method avoids leaking pagination details into call sites.
- How does lesstif/php-jira-rest-client report errors and exceptions?
- The package is an object-oriented HTTP wrapper around Jira's REST API and typically surfaces failures through Guzzle or PSR-7 exceptions rather than Laravel's HTTP client exceptions. Confirm the exact behavior for your pinned version and map it to application-owned exceptions in your gateway. Because it does not use Laravel's Http facade, Http::fake and Laravel retry hooks do not apply.
- Is it safe to use this package in production given its license and provenance?
- The assessment flags the license as NOASSERTION and the repository provenance as unknown, which are hard stops until a human verifies the LICENSE file and confirms the Packagist package maps to the expected vendor and repository. Pin an exact version with a committed composer.lock and review the commit history before production use. Also account for single-maintainer bus-factor risk and monitor release cadence.
- Can I use Laravel's Http fake or retry features with this Jira client?
- No, not directly. The package uses its own HTTP layer, so Laravel's Http facade fakes, Http::retry, and request event hooks do not apply. Add retry, backoff, circuit-breaking, and tracing at your application layer, or isolate the client behind an interface you can fake in tests.
- What is a good way to integrate and later replace this Jira client in Laravel?
- Bind a configured client in a JiraServiceProvider, read JIRA_HOST, JIRA_AUTH_MODE, JIRA_USER, and JIRA_TOKEN from environment variables, and keep a config/jira.php map of custom field keys to IDs. Wrap the vendor client in an application-owned JiraGateway interface with domain methods such as openTicket, transitionTicket, and searchByJql. Register it as a singleton only if credentials are global; use a keyed factory for multi-tenant or per-environment credentials. That interface is the seam that lets you replace the package with Atlassian's SDK or direct HTTP later.