Jira CLI project creation and configuration import in a Dockerized Jira 8.20 environment

Answer to the core questions

1. Workflow import during project creation? The Atlassian‑provided CLI (e.g., jira-cli) does not support embedding a workflow JSON in the project create call. You must create the project first, then call jira-cli workflow import or use the REST /rest/api/2/workflow endpoint to attach the workflow.
2. Side effects of jira-admin db reset in Docker? Running jira-admin db reset inside the container will drop the embedded database (H2 or the configured DB). It does **not** touch the /var/atlassian/application-data/jira home volume unless that volume contains the DB files. If you map a dedicated DB container (e.g., Postgres) and keep the home volume separate, the reset is safe and will not corrupt configuration files.
3. Verifying CLI plugin version against Jira 8.20? Use the CLI’s plugin list or query the REST endpoint /rest/api/2/serverInfo to fetch the Jira version, then compare the plugin’s jira-cli plugin.xml version field. A quick sanity check is:

   docker exec -it jira bash -c "jira-cli --version && curl -s -u admin:admin http://localhost:8080/rest/api/2/serverInfo | jq .version"
   

   If the CLI version string contains the same major/minor numbers as the server, you’re aligned.

Step‑by‑step recipe for this scenario

1. Spin up Jira in Docker (replace JIRA_DB_PASSWORD and other secrets with your own values):

   docker run -d \
     --name jira \
     -p 8080:8080 \
     -v jira_home:/var/atlassian/application-data/jira \
     -e JIRA_DB_HOST=postgres \
     -e JIRA_DB_PASSWORD=secret \
     atlassian/jira-software:8.20.0
   

   Ensure the container is healthy before proceeding.
2. Install the CLI wrapper inside the container (example using curl to fetch the binary):

   docker exec -it jira bash -c "curl -L https://github.com/atlassian/jira-cli/releases/download/8.20.0/jira-cli-8.20.0-linux-amd64.tar.gz | tar xz -C /usr/local/bin"
   

3. Create the project via REST (the CLI can forward to REST, but a raw curl is explicit):

   docker exec -it jira bash -c "curl -s -u admin:admin -X POST \
     -H 'Content-Type: application/json' \
     -d '{\"key\":\"PROJ\",\"name\":\"Demo Project\",\"projectTypeKey\":\"software\",\"leadAccountId\":\"admin\"}' \
     http://localhost:8080/rest/api/2/project"
   

   Verify a 201 response.
4. Import the workflow (assuming you have a workflow.json file in the host’s configs/ folder mapped to the container):

   docker cp configs/workflow.json jira:/tmp/workflow.json
   
   docker exec -it jira bash -c "jira-cli workflow import --projectKey PROJ --workflowFile /tmp/workflow.json"
   

   The CLI will POST to /rest/api/2/workflow under the hood.
5. Import automation rules (Project Configurator plugin or REST /rest/api/2/rule if available):

   docker cp configs/rules.json jira:/tmp/rules.json
   
   docker exec -it jira bash -c "jira-cli rule import --file /tmp/rules.json"
   

   If the plugin is not installed, you may need to install it via the Atlassian Marketplace API first.
6. Reset the database for a clean start (if needed):

   docker exec -it jira bash -c "jira-admin db reset"
   

   This will drop the DB; ensure you have a fresh home volume or a backup. It does not delete the home volume unless that volume contains the DB files.
7. Verify the setup:
   • Check the Jira UI: http://localhost:8080/projects should list PROJ.
   • Inspect the workflow: http://localhost:8080/secure/admin/WorkflowScheme.jspa?workflowSchemeId=….
   • Confirm automation rules: http://localhost:8080/rest/api/2/rule (or via UI).

Missing diagnostic detail

To fine‑tune the db reset recommendation, could you confirm whether your database is running in a separate container or inside the Jira container? This influences whether the reset will affect the home volume.