- How do I install GitScrum Community Edition with Composer?
- Install it with Composer using gitscrum-community-edition/laravel-gitscrum in a Laravel application, then follow the README for publishing configuration and running migrations. Because the package includes controller-based routes, config publishing, seeders, and middleware, treat installation like a full application module rather than a tiny utility. Test the install in a branch before rolling it into an existing app.
- Does GitScrum Community Edition support Laravel 10 and Laravel 11?
- The provided release notes do not state the exact Laravel and PHP version constraints, so check composer.json for the declared illuminate/* and php requirements. The addition of Laravel Page Speed in 1.1.0 may narrow the compatible Laravel matrix because response-mutating middleware packages often lag new framework majors. Confirm compatibility against your target Laravel version before upgrading.
- Is GitScrum Community Edition a standalone app or a package I can embed in an existing Laravel project?
- GitScrum Community Edition is an open-source, self-hosted project management platform built on Laravel, but the package also acts as a domain-integration layer for issue-tracking workflows. It includes presentation-adjacent controller logic such as IssueController::index and AJAX issue creation, so embedding it in an existing app is possible but not purely headless. Review controller coupling and route bindings if you plan to consume it from APIs, queues, or CLI tools.
- How do I publish GitScrum configuration and migrations?
- Use Laravel's vendor:publish workflow to publish the package config into a scratch directory first, then diff it against your committed config before overwriting anything. Run migrations in a branch and verify whether 1.1.0 adds only additive schema changes. Also check whether package seeders are auto-discovered, since they can collide with app-level test fixtures.
- Does GitScrum Community Edition include Scrum and Kanban boards?
- Yes. GitScrum Community Edition combines Scrum and Kanban workflows with sprint and task management, visual boards, time tracking, issue tracking, and team collaboration features such as roles, comments, and notifications. It is designed for self-hosting and Laravel customization, so teams can adapt workflows inside their own PHP application.
- What changed in laravel-gitscrum version 1.1.0?
- Version 1.1.0 is a minor release with label filtering by user story, AJAX-based issue creation, an IssueController::index refactor, a sync-without-detach mode, a private-mode sprint visibility fix, dead-code removal, Laravel Page Speed adoption, and test/seeder configuration changes. No deprecations or removals are announced. Treat it as a routine minor upgrade with extra review around sync semantics and middleware side effects.
- Does GitScrum's sync without detach change the default sync behavior?
- The changelog introduces a sync-without-detach mode but does not state whether detach-on-sync remains the default. Confirm in the package config or documentation whether the new mode is opt-in; if the default flipped, audit external tracker data for duplication, stale links, or unintended detachments. This is the highest-risk item in 1.1.0 for anyone relying on existing sync semantics.
- Is Laravel Page Speed a required dependency in GitScrum 1.1.0?
- The release notes say Laravel Page Speed was added, but the excerpt does not clarify whether it is a hard, optional, or dev dependency. Inspect composer.json and the package config to see whether it can be disabled. Because Page Speed mutates HTTP responses globally, adding it to a library warrants dependency sign-off and testing alongside your existing middleware stack.
- Is the private-mode sprint visibility fix in GitScrum 1.1.0 security-relevant?
- The fix addresses private-mode sprint visibility, which is authorization-adjacent. If earlier versions exposed private sprints to users who should not see them, treat this as a security-relevant correction and prioritize upgrading installations on 1.0.x or earlier. After upgrading, manually verify sprint visibility with low-privilege accounts.
- How should I test and upgrade a Laravel app from GitScrum 1.0.x to 1.1.0?
- Upgrade in a dedicated branch and run your full host application test suite plus manual checks over issue list, issue create, and sprint views. Diff newly published config against your committed copy to catch new keys, and confirm whether package migrations and seeders changed in 1.1.0. Also validate the sync path and private sprint permissions before merging to production.