Moving to Forge – Space Properties Changes

Projectrak is currently being updated from Atlassian Connect to Forge as part of its evolution on Atlassian Cloud. By moving to Forge, Projectrak is adopting Atlassian’s latest and preferred development platform for Cloud apps in the Marketplace, helping ensure the app stays aligned with Atlassian’s current platform standards and future direction.

Why it is important to update the app

Keeping Projectrak up to date is important to ensure the app continues to evolve on Atlassian’s current Cloud app platform. Forge is Atlassian’s preferred platform for Cloud app development and provides the foundation for a more secure, reliable, and scalable app experience.

As part of this transition from Connect to Forge, the feature used to set up project fields as space properties now relies on a new implementation. Updating before 29 June ensures that the existing configuration for this feature can be migrated automatically and that the functionality continues to work correctly after the update.

What happens if you do not update

If you do not update the app, Projectrak will continue to work correctly in general. This change only affects the functionality used to set up project fields as space properties.

If you do not update before 29 June, that specific functionality will stop working in its current implementation and its configuration will not be included in the planned migration. If you update after that date, you will need to configure those space properties again manually — as well as any places where you are using them, such as JQLs or Jira expressions.

Changes and items to review after updating (post‑29 June migration)

After the update and the migration of your space properties, you may need to make some adjustments to how you use these space properties inside Jira. This is outside Projectrak’s control, so it is important to review your current configuration after the update.

Please review the following scenarios:

1. Space property names can only contain letters, numbers, - and _. From now on, project property names can only use letters, numbers, - and _. During the migration, any other character will be replaced with _, and you will need to do the same wherever you reference the property by name.
   Example: If you had a field called "Project Status" and you currently use something like "project.Projectrak Status" = value, you will need to change that configuration to "project.Projectrak_Status" = value.
   Action: Review all places where you use these properties by name, such as JQL filters, workflows, automation rules, or any other Jira configuration, and replace any unsupported character with _ where needed.

2. No changes are needed if you use the space property alias. If you are using space properties through their alias, you do not need to make any changes.
   Example: You can identify this case if your configuration uses syntax like project.properties["Project Status"].
   Action: In that case, no action is required.