Skip to main content

Atlassian Inform Integration

Integrate your Atlassian usage data with the nOps platform to gain detailed insights into your Atlassian service utilization.

What Do You Get with Atlassian Integration in Inform?​

With the Atlassian integration in Inform, you get:

  • User Activity Analysis: View comprehensive breakdowns of your Atlassian user activities, including active users, idle users, and usage patterns by product.
  • Resource Utilization Insights: Track and analyze your Atlassian service usage patterns to optimize resource allocation and efficiency.
  • Idle User Identification: Identify inactive or underutilized user accounts to optimize licensing and resource allocation.
  • Multi-Account Support: Monitor multiple Atlassian accounts from a single dashboard for better usage management across projects.
  • Automated Data Sync: Regular updates of your usage data ensure you always have the latest activity information.
  • Custom Reporting: Generate detailed reports on your Atlassian usage patterns for better resource planning.

FAQs​

Expand FAQs

1. How does the Atlassian integration with nOps work?​

The integration connects directly to your Atlassian account using API credentials. nOps fetches usage and user activity data using your API key, processes it, and displays the information within the Inform platform for detailed usage analysis and optimization recommendations.

2. What permissions does the API key require?​

The API key requires Organization Admin permissions and must be created without scopes to access comprehensive user activity and organizational data. Specifically, you need:

  • Organization Admin role - The highest level of administrative access in your Atlassian organization
  • Centralized User Management - Legacy user management models are not supported
  • API key without scopes - Required because the Admin API endpoints for organization, user directory, and activity data are not covered by Atlassian's current scoped API system
  • Full Admin API access - To access organization data, user directories, and activity across all Atlassian products
warning

You must create an API key without scopes. Scoped API keys will fail because, as documented in Atlassian's Cloud Admin Scopes documentation, "scopes are not available for all APIs." The organization and user management endpoints this integration requires are not covered by the available scopes.

3. Can I use an existing API key?​

You can use an existing API key only if it was created without scopes and with Organization Admin permissions. However, for security best practices, we recommend:

  • Generating a new API key without scopes specifically for the nOps integration
  • Ensuring the key is created by an account with Organization Admin role
  • Setting an appropriate expiration date for regular key rotation

4. How long does it take for data to appear in nOps after setup?​

It may take up to 24 hours for the initial data synchronization to complete. After this period, your Atlassian usage data should be visible in the Usage Analysis tool.

5. What should I do if my usage data doesn't appear after 24 hours?​

If the data is not visible after 24 hours, check the following:

  • Verify Organization Admin role - Ensure your account has Organization Admin permissions
  • Check API key validity - Confirm the API key is correct and has not expired
  • Confirm unscoped API key - Verify the API key was created without scopes for full Admin API access
  • Verify Centralized User Management - Ensure your organization uses centralized (not legacy) user management
  • Check email visibility settings - Ensure default email visibility is set appropriately for data access
  • Confirm actual user activity - Ensure there is actual user activity in your Atlassian account
  • Validate API key entry - Check that the API key name is correctly entered in the integration setup

If the issue persists, contact nOps support for assistance.

6. Can I monitor multiple Atlassian accounts?​

Yes, you can monitor multiple Atlassian accounts by setting up separate integrations for each account. Each integration requires its own API key with appropriate permissions. This allows you to track user activity across different projects, departments, or environments.

7. What Atlassian usage data is tracked in the integration?​

The integration tracks user activity and resource utilization data from your Atlassian account, including:

  • Jira Software user activity and idle users
  • Confluence user engagement and content creation patterns
  • Bitbucket repository usage and developer activity
  • Trello board activity and user engagement
  • Atlassian Marketplace app utilization
  • Any other usage metrics from Atlassian services

8. What happens if my API key expires?​

If your API key expires, the integration will no longer be able to fetch new usage data. You'll need to generate a new API key in Atlassian and update the integration in nOps with the new key. We recommend setting a reminder for key expiration if you've configured an expiration date.