- Can I use stingus/jira-bundle in a Laravel app?
- Not as a normal Composer dependency. It is a Symfony bundle that relies on Symfony's DI container, Configuration tree, event dispatcher, and bundle bootstrapping, none of which exist in Laravel. You would need to vendor or fork the Jira client and OAuth 1.0a signing logic and re-wrap it in a Laravel service provider and facade. Treat it as a reference implementation, not an installable package.
- Does stingus/jira-bundle support Jira Cloud?
- No, not on the supported path. The bundle is built around OAuth 1.0a (3LO), which Atlassian has deprecated for Jira Cloud in favor of OAuth 2.0 (3LO) with scoped access and rotating refresh tokens. It is only defensible for Jira Server or Data Center application links. If Jira Cloud is in scope, reject this package and implement OAuth 2.0 instead.
- Is stingus/jira-bundle still maintained?
- The last release was 2019-11-14, with no activity signal since. The repository has five stars and zero dependents, so there is effectively no community to absorb bugs or answer questions. Expect to own any fixes yourself if you adopt the code.
- What PHP and Laravel versions work with stingus/jira-bundle?
- Unknown without running composer why-not, but a 2019 Symfony bundle is likely to have constraints incompatible with PHP 8.2+ and Laravel 10 or 11. Expect dependency conflicts on composer install and possible deprecation fatals even after forking. Verify the constraint set against your target stack before committing.
- How do I connect Laravel to the Jira REST API without a Symfony bundle?
- Use a maintained OAuth 1.0a implementation, such as a Guzzle OAuth subscriber or a dedicated OAuth 1.0a client library, and write a thin JiraClient service around it. That gives you Laravel-idiomatic configuration, HTTP client reuse, retry middleware, and logging. For Jira Cloud, skip OAuth 1.0a entirely and use OAuth 2.0 3LO with Socialite or a dedicated Atlassian driver.
- What OAuth version does stingus/jira-bundle use?
- It implements OAuth 1.0a request signing for Jira REST API calls, which fits Jira Server and Data Center application links. Atlassian has deprecated OAuth 1.0a for Jira Cloud, so the signing logic is mainly useful as a reference if you are porting it. Keep signing behind an interface such as JiraAuthSigner so you can swap to OAuth 2.0 later.
- How do I configure multiple Jira instances in Laravel?
- The bundle's Symfony Configuration tree does not carry over, so plan a config/jira.php file with named connections instead. Bind each connection to a distinct JiraClient instance in a service provider, and resolve them by name from the container. Keep credentials and base URLs per connection so token expiry, revocation, or base URL changes are isolated.
- What are the alternatives to stingus/jira-bundle for Laravel?
- For Jira Server or Data Center, pair a maintained OAuth 1.0a signing library with a small Laravel JiraClient service. For Jira Cloud, use OAuth 2.0 3LO via Socialite or a dedicated Atlassian OAuth 2.0 driver. Both paths avoid Symfony's container and give you Laravel-native configuration, HTTP middleware, and logging.
- Should I fork stingus/jira-bundle or use an OAuth 1.0a signing library?
- Fork only if you specifically need its Jira endpoint wiring as a starting point and accept becoming the maintainer. Otherwise, a maintained OAuth 1.0a signing library plus your own thin client is lower risk and easier to keep current. The bundle's reusable core is limited to request signing and REST client logic, which are straightforward to reimplement.
- How do I test a Jira integration in Laravel safely?
- Keep the Jira HTTP client behind an interface and fake it in unit tests so CI does not depend on a live Jira instance. Use a sandbox Jira Server or Data Center application link for integration tests, and cover token expiry, revocation, and base URL changes explicitly. If you ported code from the bundle, add tests for the signing layer since the original has no community test coverage to lean on.