Permissions vary based on your JIRA version. See the documentation below to ensure you have the right permissions before you start setting up JIRA in Velocity.
For Data Center and JIRA Server v8.13 or below:
Uses Basic Auth
Jira documentation on permissions: https://confluence.atlassian.com/jirasoftwareserver0813/permissions-overview-1027135602.html
If you have JIRA Server v8.14 and above:
Uses bearer tokens
Jira documentation on permissions: https://confluence.atlassian.com/jirasoftwareserver0814/permissions-overview-1043893013.html
If you have JIRA Cloud:
Uses Basic Auth
JIRA documentation on permissions: https://support.atlassian.com/jira-software-cloud/docs/how-do-jira-permissions-work/
401 Status Error:
When JIRA returns a 401 status error (Token Unauthorized), this indicates the token configured to fetch data from JIRA is either invalid or does not have permission to fetch the data about the projects you are attempting to sync.
To fix this, try one or both of the following solutions:
Expand the personal access token permissions to be able to have access to the projects you wish to sync
Regenerate the personal access token
Check that Project permissions are set to the "Browse Project" permission.
JIRA Documentation to manage Project permissions: https://confluence.atlassian.com/adminjiraserver073/managing-project-permissions-861253293.html
When connecting JIRA, it's important to check that Group permissions are set accordingly.
JIRA documentation to manage Group permissions: https://support.atlassian.com/user-management/docs/create-and-update-groups/
If these credentials do not include Jira Admin permission (`Administer Jira` global permission), Velocity won't be able to create the webhooks required to keep your Jira data up-to-date. You'll need to manually create a Jira webhook by following the instructions here.