Download the PHP package jeffersongoncalves/jira-cli without Composer
On this page you can find all versions of the php package jeffersongoncalves/jira-cli. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Table of contents
Download jeffersongoncalves/jira-cli
More information about jeffersongoncalves/jira-cli
Files in jeffersongoncalves/jira-cli
Download jeffersongoncalves/jira-cli
More information about jeffersongoncalves/jira-cli
Files in jeffersongoncalves/jira-cli
Vendor jeffersongoncalves
Package jira-cli
Short Description A Jira Cloud CLI built with Laravel Zero.
License MIT
Homepage https://github.com/jeffersongoncalves/jira-cli
Package jira-cli
Short Description A Jira Cloud CLI built with Laravel Zero.
License MIT
Homepage https://github.com/jeffersongoncalves/jira-cli
FAQ
After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.
Example:
Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories.
In this case some credentials are needed to access such packages.
Please use the auth.json textarea to insert credentials, if a package is coming from a private repository.
You can look here for more information.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?
Informations about the package jira-cli
Jira CLI
A modern Jira Cloud CLI built with Laravel Zero.
Features
- Issues - Create, list, view, edit, move, assign, delete, comment, worklog, link, clone, and watch issues
- Epics - List, create, and manage epic associations
- Sprints - List, add issues, and close sprints
- Boards - List boards with project filtering
- Projects - List accessible projects
- Releases - List project versions and releases
- Authentication - Secure credential storage with API tokens (Basic and Bearer)
- Browse - Open issues and projects in the browser from the terminal
Requirements
- PHP 8.2+
Installation
Or clone and build locally:
Getting Started
1. Create a Jira API Token
- Go to https://id.atlassian.com/manage-profile/security/api-tokens
- Click Create API token
- Give it a descriptive label (e.g.
jira-cli) - Click Create and copy it immediately - it will only be shown once
The API token inherits all permissions from your Atlassian account. For OAuth 2.0 / Forge apps, the following granular scopes are required:
Note: API tokens (Basic auth) inherit all permissions from the account - no scope configuration needed. Scopes below are only for OAuth 2.0 and Forge integrations.
Jira Platform Scopes:
| Scope | Permission | Required for |
|---|---|---|
read:issue:jira |
Read | List, view, and clone issues |
write:issue:jira |
Write | Create, edit, assign, and clone issues |
delete:issue:jira |
Delete | Delete issues |
read:issue.transition:jira |
Read | List available status transitions |
read:comment:jira |
Read | View issue comments |
write:comment:jira |
Write | Add comments to issues |
read:issue-worklog:jira |
Read | List worklogs |
write:issue-worklog:jira |
Write | Log time on issues |
read:issue-link:jira |
Read | View linked issues |
write:issue-link:jira |
Write | Link issues together |
delete:issue-link:jira |
Delete | Remove issue links |
read:issue-link-type:jira |
Read | List link types |
write:issue.watcher:jira |
Write | Watch issues |
read:project:jira |
Read | List projects |
read:project-version:jira |
Read | List releases/versions |
read:user:jira |
Read | User info and assignment |
Jira Software (Agile) Scopes:
| Scope | Permission | Required for |
|---|---|---|
read:board-scope:jira-software |
Read | List boards |
read:sprint:jira-software |
Read | List sprints |
write:sprint:jira-software |
Write | Add issues to sprint, close sprint |
read:epic:jira-software |
Read | List epics |
write:epic:jira-software |
Write | Add/remove issues from epics |
2. Save your credentials
You will be prompted for your Jira server URL, Atlassian account email, and API token.
3. Verify authentication
4. Start using commands
Commands
Authentication
| Command | Description |
|---|---|
auth:save |
Save Jira credentials (server, email, API token) |
auth:show |
Display saved credentials |
Issues
| Command | Description |
|---|---|
issue:list |
List/search issues with JQL filters (--project, --type, --status, --assignee) |
issue:view <key> |
View issue details (--comments to include comments) |
issue:create |
Create a new issue (interactive or via options) |
issue:edit <key> |
Edit issue fields (--summary, --priority, --assignee) |
issue:move <key> |
Transition issue status (--status or interactive) |
issue:assign <key> [user] |
Assign issue (me for yourself, empty to unassign) |
issue:delete <key> |
Delete an issue (--force to skip confirmation) |
issue:comment <key> |
Add a comment (--body or interactive) |
issue:worklog <key> |
Log time (--time=2h) or list worklogs (--list) |
issue:link <inward> <outward> |
Link two issues (--type or interactive) |
issue:unlink <linkId> |
Remove an issue link |
issue:clone <key> |
Duplicate an issue |
issue:watch <key> |
Watch an issue |
Epics
| Command | Description |
|---|---|
epic:list |
List epics (--project=KEY) |
epic:create |
Create a new epic (interactive or via options) |
epic:add <epic> <issues...> |
Add issues to an epic |
epic:remove <issues...> |
Remove issues from their epic |
Sprints
| Command | Description |
|---|---|
sprint:list |
List sprints (--board=ID, --state=active\|closed\|future) |
sprint:add <sprint> <issues...> |
Add issues to a sprint |
sprint:close <sprint> |
Close/complete a sprint (--force to skip confirmation) |
Boards, Projects & Releases
| Command | Description |
|---|---|
board:list |
List boards (--project to filter) |
project:list |
List accessible projects |
release:list |
List project versions (--project=KEY) |
Utilities
| Command | Description |
|---|---|
me |
Show current authenticated user |
open [key] |
Open issue or project in the browser |
serverinfo |
Show Jira server information |
Development
Changelog
Please see CHANGELOG for more information on what has changed recently.
License
Jira CLI is open-source software licensed under the MIT license.
All versions of jira-cli with dependencies
PHP Build Version
Package Version
Requires
php Version
^8.2
The package jeffersongoncalves/jira-cli contains the following files
Loading the files please wait ...