Common FAQ

How does cloud app pricing work?

Cloud pricing is subscription based. You are eligible for support and automatic version updates as long as your subscription is active.

When your subscription renews each month, you are automatically billed for host products and apps based on the number of users in your instance.

If app pricing changes after your initial purchase, there’s a 60-day grandfathering period during which you can renew based on the old pricing.

How do I determine my cloud pricing?

Apps are billed based on the number of users in your host product. Jira Cloud apps are priced based on the maximum users of the Jira products on your instance. For example, if you have Jira Software (50 users) and Jira Service Management (10 agents) on the same instance, you pay the 50-user price for apps.

The pricing structure for cloud products and apps is as follows:

• Monthly subscriptions with up to 10 host product users are billed at a flat rate price.
• Monthly subscriptions with more than 10 users are billed per user, starting at the first user.
• Monthly subscriptions with more than 100 users are billed per user. The table above provides example pricing at various user levels.
• If per-user pricing is not yet available for this app, please contact the vendor for further information.

If you’ve opted for annual billing for your host product, apps are also billed annually at a discount (12 months for the price of 10).

Do you offer academic, community, or open-source licenses?

Academic, community and open source licenses are not available for cloud apps.

Can I extend my free trial?

For cloud apps, you cannot extend your free evaluation period. All cloud apps are immediately subscribed by a user, and we provide a free evaluation period. This is a minimum of 30 days and ends on the second billing cycle after you first subscribe to the app.

Does Azure AD Attributes Sync for Jira support Custom Domains?

Yes, Azure AD Attributes Sync for Jira supports Custom Domains. This feature lets the users choose unique domains for their Jira products. Click on the link to learn the details.

Why can’t I access the Azure AD Attributes Sync for Jira app in specific projects?

Atlassian implemented a regulation called App access rules. When these rules are applied to a specific project, access to certain data in that project is restricted.

Only the organization admin can change the App access rules. For more information, refer to the Atlassian documentation.
Below is a description of how App access rules impact the Azure AD Attributes Sync for Jira functioning.

In case of the Block app access to data:

If you configured the app and then blocked app access to data:

• The app panel won’t be displayed.
• Data that has already been mapped to custom fields will still be visible in the Issue View panel and available in the history; new mappings won’t be visible.
• You can still add a new directory and mapping. However, the data from Microsoft Azure won’t be displayed in the custom field.
  
• The app won’t be displayed in the project settings, so there won’t be an option to make changes in the configuration panel.
• You can configure the Azure AD Sync - Copy data from Azure AD and the Azure AD Sync - Update user’s attributes in Azure AD post functions. However, the data from Microsoft Azure won’t be updated upon workflow transitions, and the post functions won’t be included in the post functions list in the Workflow configuration screen.
• You’ll also see the blockade information in the custom fields on the Issue View panel.
  
  In case of the Allow app access to data
  
  

If you configured the app and then allowed app access to data:

• The mapped data will be displayed correctly.
• Creating a new issue in the project will be possible.
• The Azure AD Sync - Copy data from Azure AD and the Azure AD Sync - Update user’s attributes in Azure AD post functions will work correctly.
• If the organization admin turns off the Allow app access to data option and deletes the policies, the app works correctly.

In what format are the date and time displayed on a Jira issue?

The date displayed in the custom field on the Issue Panel is in the DD MM YYYY hh: mm (UTC) format, for example, 04 June 2021 11:52 AM (UTC).

The date displayed on the Issue Details View is in the DD MM YYYY hh: mm (UTC) format or according to the user’s time zone, for example, 04 June 2021 11:52 AM (UTC+02:00).

Is Atlassian Access necessary to use the Azure AD Attributes Sync for Jira app?

Atlassian Access isn’t required for the Azure AD Attributes Sync for Jira app to work correctly.
The app’s main logic is to match Azure AD attributes between existing Jira users and their directory data. The feature Atlassian Access offers is the ability to create new Jira users based on the records available in the Azure AD directory.
Note that Azure AD Attributes Sync for Jira can’t create new users by itself; hence, using Atlassian Access is an excellent way of streamlining your processes along with Azure AD Attributes Sync for Jira.

Does the app support team-managed projects?

In team-managed projects, the Azure AD Attributes Sync for Jira app supports displaying attributes in the Issue Details View panel. However, it doesn’t support post functions or Mapping Azure AD data to custom fields.

What are the differences between Azure AD Attributes Sync for Jira and Active Directory Attributes Sync?

Both apps improve the user information synchronization between Active Directories and Jira. The biggest differences between them are Jira hosting and directory type:

• Active Directory Attributes Sync is designed for the Data Center. It enables admins to display and manage Active Directory LDAP user attributes across Jira, including user’s profile page, user’s hover profile, custom fields, and the Customer Portal.
• Azure AD Attributes for Jira is designed for Jira Cloud. It populates user information from Azure Active Directory into Jira custom fields. It offers an alternative to native directory connections, only available through Atlassian Access.