Skip to end of banner
Go to start of banner

Set up a Jira service account

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Overview

  • Service accounts help prevent potential issues when connecting to a specific employee account.

  • Jira Integration+ automatically respects user's Jira permissions.

  • Service accounts can be used to limit access to the main user via Jira configuration. The main user is the user who initially connected your bot in Slack to your Jira instance.

  • There are also settings you can use to limit access via configuration.

On this page:

Permission Requirements for Helpdesk +

  • Jira Permissions: The main authorized user needs the following permissions to create a connection to the APIs. Individual users do not need these permissions:

    • Jira Administrator Access

    • JSM Agent Role: Main authorized users must have the JSM Agent role for each selected service desk. Agent roles are not required for Jira software projects.

    • JSM License: A valid Jira Service Management (JSM) license is required for integration functionality.

Atlassian occasionally requires additional authentication from users when the main user is altered. This behavior is tied to the functioning of OAuth keys within the APIs and falls outside our sphere of control. Should your instance exhibit this behavior, users will be prompted to re-authenticate during their next action.

How to set up

  1. Create a Jira account.

  2. Make this user an admin in Jira.

  3. Check Permissions Schemes for the following:

    • Browse Project

    • Create Issue

    • Comment on Issue

    • Edit Issue

    • Transition Issue

    • Add Attachment

  4. Add the service account to the relevant Project Role in each project to ensure it has access to perform all actions.

  5. Go to https://account.nextup.ai.

  6. Scroll down to the main authorized user.

  7. Click Change.

  8. Authenticate as that user (make sure it is not logged in as you).

  • No labels