Atlassian Updates and How We Can Help

Atlassian has recently announced several updates within the Cloud space, including key changes that may impact essential processes within your teams.

API Token Expiry

To enhance administrative control over token management and improve security, all existing API tokens created without expiry dates will now be assigned an expiry date. No token will expire sooner than 12 months from the official date set by Atlassian (13 March 2025) - Atlassian announcement.

What is the Effect of This Change?

This change may affect any integrations, automations, and other services that utilise API tokens generated within your Atlassian Cloud products (Jira Cloud (Jira Software, Jira Service Management), Confluence Cloud). We recommend reviewing all items that may be impacted by the newly established expiry dates for existing API tokens.

How Can We Assist?

We understand that reviewing this can be a cumbersome process. To facilitate this, we are offering to provide API token notification automations at no charge. This notification will serve as an automated early reminder to API token owners and administrators to renew API tokens, ensuring that no integrations or automations fail as a result of API tokens expiring.

If you would like us to assist in setting up this API token notification automation, please schedule a time with one of our Atlassian specialist Support Engineers.

Incoming Webhook Triggers

Atlassian are making changes that will affect automation rules utilising the Incoming webhook Trigger that were created before 28 January 2025. These rules will begin to be routed through a more secure endpoint. Atlassian announcement.

What is the effect of this change?

For affected rules to continue working after 30 May 2025, you'll need to make the changes in the applications to migrate to the new endpoint. The legacy endpoint will no longer be available to trigger your rules as of 30 May 2025.

To identify impacted automation rules, shortlist the affected rules by filtering the rules which have Incoming webhook as the Trigger.

Once this filter is applied, all impacted rules will display - update the rules to use the new endpoint as outlined in Atlassian’s support documentation.

If you would like any assistance with reviewing and updating impacted rules, our Managed Services team can also assist - please schedule a time with one of our Atlassian specialist Support Engineers.

Jira Service Management Assets – Limit of 2 Unique Constraints per Object Type

Finally, Atlassian has also announced changes coming into effect in Assets for Jira Service Management - Atlassian announcement.

The following limits have been gradually been rolled out effective February 2025:

• A maximum of 120 attributes per object type.
• A maximum of 2 unique constraints on attributes within an object type.
• For URL, Email, and Select attributes:
  • A maximum cardinality of 50 for attributes with multiple values.
  • A total of no more than 2700 characters across all values within an attribute.

Please refer to this article from Atlassian for a comprehensive list of limits in Assets for Jira Service Management, Cloud.

What is the Effect of This Change?

Atlassian have advised that a downloadable report (outlining exactly where changes need to be made in your sites Assets data) is expected to be available mid-April 2025.

Additionally, they have also reassured that for sites that continue to exceed these limits, the rollout of Assets changes will be delayed to provide users with time to adjust their data.