![Page cover image](https://docs.nimbusintelligence.io/~gitbook/image?url=https%3A%2F%2F1735469989-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FKSboB0jIw43eWLIQyF8S%252Fuploads%252FUr8yttQj2pAhWqImiBnO%252FAtlassian%2520Jira%2520banner.png%3Falt%3Dmedia%26token%3Df348a33c-3469-445c-8abf-2a96a78fdb23&width=1248&dpr=4&quality=100&sign=688f8db7&sv=1)
Atlassian Jira
Project Management & Issue Tracking Software, Built for Software Development Teams
About Atlassian Jira
Atlassian Jira is a versatile project management and issue tracking software developed by Atlassian. Primarily designed for software development teams, Jira enables users to plan, track, and manage tasks throughout the project lifecycle. It supports customizable workflows, agile methodologies, and provides robust reporting features, fostering collaboration and transparency.
Get the Nimbus Intelligence Connector in Snowflake
You can install the Nimbus Intelligence Atlassian Jira Connector from the Snowflake Marketplace with only a few clicks!
Obtain Credentials and Create a Connection
This connector is based on Client ID, Client Secret & Client Domain authentication. The instructions below indicate how to obtain your credentials from the Atlassian Jira page.
Generate an API Token for your Atlassian Account: https://id.atlassian.com/manage/api-tokens. The key you will be given will be you Client Secret and should be stored somewhere safely.
The domain you see on the search bar when you are logged in into Jira of the form
<account-name>.atlassian.net
will be your Base URL.Finally, the username/email that you use to log into Atlassian Jira is your Client ID.
Fill in the Add connection form in the Connections page in the application and click on the
Generate Ready-to-Run Script
button to obtain a pre-filled script with your information.Paste the script in a new worksheet and execute it fully to create a new connection.
Available Endpoints
Check the full Atlassian Jira API documentation.
Endpoint | Incremental Ingestion |
---|---|
Not supported by Atlassian Jira | |
Not supported by Atlassian Jira | |
Not supported by Atlassian Jira | |
Not supported by Atlassian Jira | |
Not supported by Atlassian Jira | |
Not supported by Atlassian Jira | |
Not supported by Atlassian Jira | |
Not supported by Atlassian Jira | |
Not supported by Atlassian Jira | |
Not supported by Atlassian Jira | |
Not supported by Atlassian Jira | |
Not supported by Atlassian Jira | |
Not supported by Atlassian Jira | |
Not supported by Atlassian Jira | |
Not supported by Atlassian Jira | |
Not supported by Atlassian Jira | |
Not supported by Atlassian Jira | |
Not supported by Atlassian Jira | |
Not supported by Atlassian Jira | |
Not supported by Atlassian Jira | |
Not supported by Atlassian Jira | |
Not supported by Atlassian Jira | |
Not supported by Atlassian Jira | |
Not supported by Atlassian Jira | |
Not supported by Atlassian Jira | |
Not supported by Atlassian Jira | |
Not supported by Atlassian Jira | |
Not supported by Atlassian Jira | |
Not supported by Atlassian Jira | |
Yes | |
Not supported by Atlassian Jira |
Need Help?
Don't forget to check the#faqs section in the Getting Started page.
Did we forget to implement an endpoint that you would like or did you find a bug? If you didn't find your answer in the FAQs, let us know!
If you have an issue, check the #known-limitations-and-issues section to see if we are already working on it!
Check the rest of the Available Connectors
Available ConnectorsLast updated