Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
languagebash
jira site:config add

✔ Site URL? · http://localhost:8080jira.example.com
✔ Alias for the site? · localhostdc2022
Checking site...... doneDone
✔ Username? · admin
✔ Do you want to use token instead of password (recommended)? (Y/n) · false
✔ Password? · ********
✨  Done in 21.83s.

To use the CLI, user doesn’t need to be an administrator, they can use any command if they granted permission in the Jira. They can’t do anything which their permissions in Jira doesn’t allow. Although you can try to run any command with any user, only the operations your account has permission to execute will be completed successfully. If you don’t have permission for an action you will receive “Not Permitted” (401/403) response from Jira.

After adding a site, you can also make it the default site, so that you don’t need to specify it every time using --site=my-site when running commands:

Code Block
jira config set-default dc2022

Adding a Cloud Site

If you have a license for Forge version of the add-on for your cloud site, you can also use command line tool to access it.

You can’t use username/password combination for accessing Jira Cloud. You need to create a TOKEN for your account and use that TOKEN together with your email to authenticate. You can refer here to learn more about generating personal access tokens in Jira.

You also need to provide the webtrigger URL manually. To get the webtrigger URL, execute the following command within the embedded terminal (Apps->AtlasCLI Terminal):

Anchor
webtrigger
webtrigger

Code Block
~$ webtrigger
https://c4038762-112e-4ed3-b333-123323e31132e.hello.atlassian-dev.net/x1/_2EhEzFa_iu3n8zKRTY2dfe1x1aWR

User doesn’t need to be an administrator, they can use any command if they granted permission in the Jira. They can’t do anything which their permissions in Jira doesn’t allow.

...