FCLI Foundational Components CLI
Helps spread the AwesomeSauce of the Foundational Components team a bit further.
Prerequisites
Python 3 is required. Python 2 is not supported.
Second, Python 3's bin directory needs to be in your PATH environment variable. For example, if you are using the
python.org install on macOS, you will need to add the following to your ~/.profile.
PATH="/Library/Frameworks/Python.framework/Versions/3.*/bin:${PATH}"
Installation
fcli is located on PyPI.
To install, run the following.
$ pip3 install fcli
sudo may be needed if your Python 3 installation is in a protected directory. This will put the command the bin
directory of your Python 3 installation.
To update fcli to the latest version, run the following.
$ pip3 install --upgrade fcli
Again, sudo may be required.
Specifying Credentials
fcli uses your EUA credentials to authenticate yourself to JIRA, etc. There are multiple ways to specify your
credentials.
File
Create an ini file at ~/.fcli. In there, add the [default] section, and under that section specify a username and
password. An example can be seen in fcli.ini.
Environment Variables
The environment variables FCLI_USER and FCLI_PASS can be utilized to specify the username and password.
CLI
Only the username can be specified via the CLI. Tack on the --username <username> option.
Keyboard
If the username or password is not specified in some other fashion, the CLI will prompt the user.
Usage
Story Administration
Story Creation
To create a story in the backlog use
$ fcli backlog create story '<story title>'
You will be prompted to enter a Description and Acceptance Criteria.
Task Administration
Task Creation
There are three types of tasks the fcli can add: triage, EL, and backlog tasks.
To add a triage task,
$ fcli triage create "<task title>" "<task description>" [--importance <High/Medium/Low>] [--effort <High/Medium/Low>] [--due <date in the future>] [--in-progress] [--assign]
A new task is created in the triage board with the specified title and description. Optionally, put the task into the
In Progress state with the --in-progress option, and optionally assign the task to yourself with
--assign. The importance, effort, and due date are required, and they will be prompted for if they are not
supplied on the command line.
To add an EL task,
$ fcli el create "<task title>" "<task description>" [--importance <High/Medium/Low>] [--effort <High/Medium/Low>] [--due <date in the future>] [--in-progress] [--assign]
A new task is created in the EL board with the specified title and description. EL tasks require the same options as triage tasks.
To add a backlog task,
$ fcli backlog create task "<task title>" "<task description>" <parent story>
A new task is created in the standard backlog with the specified title and description. The task is linked with the parent story. If the parent story is already in an active sprint, the task is also moved into the same sprint.
Other Task Functions
To move a task from one status to another...
$ fcli task move <task key> <target status>
To run the triage and EL task scoring process...
$ fcli task score
Other Backlog Functions
To add a calculated VFR value to a story in the backlog and move it to Refined status...
$ fcli backlog score <task key> <duration> <cost of delay>
Triage Task Administration
There are currently two different tasks for triage administration: search for all open triage tasks and update the score for all open triage tasks.
To search for all open triage tasks,
$ fcli triage search
A json representation of all of the open triage tasks will be printed to the terminal.
The scores of all open triage tasks will be updated. The terminal will show progress.
Development
I accept PRs! Check out the issues and assign yourself when you start working on one.
Metadata
Release files for fcli 4.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| fcli-4.0.0.tar.gz | 13.3 kB | Without provenance | Details for fcli-4.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| fcli-4.0.0-py3-none-any.whl | Python 3 | none | any | Details for fcli-4.0.0-py3-none-any.whl |
Total release size: 44.2 kB
Release files / fcli-4.0.0.tar.gz
| Download URL | fcli-4.0.0.tar.gz |
|---|---|
| Size | 13.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
94bdea19a58e2485541a69acc24f0aa91fb6307df5450e0466ce9320df7602f9
|
|
BLAKE2b-256 checksum How to use checksums |
21087fd8b080195a72028b64f3c475e6b4c201df8bd982ac42f060415cfe94f5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.19.1 setuptools/40.4.3 requests-toolbelt/0.8.0 tqdm/4.26.0 CPython/3.6.5
|
Release files / fcli-4.0.0-py3-none-any.whl
| Download URL | fcli-4.0.0-py3-none-any.whl |
|---|---|
| Size | 30.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8d079b2aa7295d150f9f40e95261b5c8a57e56a432981d40d6b8b43d019505b6
|
|
BLAKE2b-256 checksum How to use checksums |
877abc26d066b2d327fcd7861f27b5f6f604112868fdeea628ff3331c7637606
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.19.1 setuptools/40.4.3 requests-toolbelt/0.8.0 tqdm/4.26.0 CPython/3.6.5
|
Security for fcli 4.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.