If you’re new to Unstructured, read this note first.

Before you can create a source connector, you must first sign up for Unstructured. After you sign up, the Unstructured user interface (UI) appears, which you use to create the source connector.

After you create the source connector, add it along with a destination connector to a workflow. Then run the worklow as a job. To learn how, try out the hands-on UI quickstart or watch the 4-minute video tutorial.

You can also create source connectors with the Unstructured API. Learn how.

If you need help, reach out to the community on Slack, or contact us directly.

You are now ready to start creating a source connector! Keep reading to learn how.

Ingest your files into Unstructured from Jira.

The requirements are as follows.

  • A Jira Cloud account or Jira Data Center installation.

  • The site URL for your Jira Data Center installation or Jira Cloud account. For Jira Cloud, open Jira in your web browser and copy the address from the browser’s address bar. If you’re unsure, check the dashboard URL, or if viewing an issue, project or board, the site URL is typically everything that comes before and including /jira, such as https://<organization>.atlassian.net/jira.

  • To process Jira projects, provide the IDs for the target projects. To get a project’s ID, sign in to your Jira Cloud account or Jira Data Center installation, and then go to the following URL: https://<organization>.atlassian.net/rest/api/latest/project/<project-key>, replacing <organization> with yours, and replacing <project-key> with the target project’s key. In the response, look for the URL https://<organization>.atlassian.net/rest/api/3/project/<project-id>, where <project-id> is the target project’s ID.

  • To process Jira boards, the IDs for the target boards. To get a board’s ID, sign in to your Jira Cloud account or Jira Data Center installation, and then go to the following URL: https://<organization>.atlassian.net/rest/agile/1.0/board?projectKeyOrId=<project-key-or-id>, replacing <organization> with yours, and <project-key-or-id> with the associated project’s key or ID. In the response, look for the URL https://<organization>.atlassian.net/rest/agile/1.0/board/<board-id>, where <board-id> is the board’s ID.

  • To process Jira issues, the IDs for the target issues. To get an issue’s ID, sign in to your Jia Cloud account or Jira Data Center installation, open the issue, and then look at the URL in your browser’s address bar. The issue ID is the string of characters after the final slash in the URL.

  • A user in your Jira Cloud account or Jira Data Center installation.

  • The user must have the correct permissions in your Jira Cloud account or Jira Data Center installation to access the target projects, boards, and issues.

  • One of the following:

To create the source connector:

  1. On the sidebar, click Connectors.
  2. Click Sources.
  3. Cick New or Create Connector.
  4. Give the connector some unique Name.
  5. In the Provider area, click Jira.
  6. Click Continue.
  7. Follow the on-screen instructions to fill in the fields as described later on this page.
  8. Click Save and Test.

Fill in the following fields:

  • Name (required): A unique name for this connector.
  • URL (required): The URL of the Jira instance.
  • Username (required for password or API token authentication, or personal access token authentication): The username of the Jira user.
  • Password (required for password authentication): The password of the Jira user.
  • API Token (required for API token authentication): The API token of the Jira user.
  • Personal Access Token (required for personal access token authentication): The personal access token of the Jira user.
  • Projects: A comma-separated list of IDs of the target projects in Jira to access.
  • Boards: A comma-separated list of IDs of the target boards in Jira to access.
  • Issues: A comma-separated list of IDs of the target issues in Jira to access.

The Cloud check box is reserved for future use. This box must always remain unchecked. Checking this box could lead to unexpected results or failures.

Was this page helpful?

Suggest edits