FAQ

Here are the answers to some of your most frequently asked questions. If you think we’re missing any critical tips, please let us know by contacting us through the Appfire Support Portal.

What is the price for the plugin? Can I pay only for users that use Enhancer Plugin for Jira Cloud?

You can check the price here.

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

Does the Enhancer Plugin support custom domains or site renames?

Yes. The Enhancer Plugin is fully compatible with Atlassian’s Cloud Site Rename feature. Renaming your site can help you strengthen your brand identity by using a domain that reflects your organization and simplify navigation by making it easier for teams to identify the right site.

You can safely rename your Atlassian Cloud site (for example, from companyname.atlassian.net to yourbrand.atlassian.net) without affecting the app functionality.

Your configurations and data will remain intact, and the app will continue to work seamlessly after the change.

For more details on how Cloud Site Rename works, see Atlassian’s official documentation.

I am trying to migrate my Enhancer Plugin instance from DC to Cloud, but I can’t upgrade the app because my Jira version is no longer supported. What can I do?

Enhancer Plugin cannot release new versions for Jira versions that Atlassian has marked as End of Support (EOS).

Cloud migration support in Enhancer Plugin is Forge-based, and Forge capabilities are only available on Jira versions that are still supported by Atlassian. As a result, the Enhancer Plugin version required for migration (v7.1.5 or later) is not compatible with Jira versions that have reached end of support. This limitation is based on Atlassian’s support policy, not on the migration process itself.

You can review Atlassian’s supported Jira versions here.

I’m getting the “Some apps are not registered to receive migration notifications” error during the JCMA migration process. Why?

This happens when Enhancer for Jira Data Center is running on a version earlier than 7.1.5. From version 7.1.5, Enhancer Plugin uses Forge-based migration support. Versions below this do not register with the Jira Cloud Migration Assistant (JCMA), so the app cannot receive migration notifications and does not appear as migratable.

How to fix this

Upgrade Enhancer Plugin to version 7.1.5 or later.
Restart the Jira Cloud Migration Assistant.

How can I check which JEP workflow enhancements are used in my Data Center instance?

Not all JEP workflow enhancements available in Data Center are supported on Cloud. If you’re preparing for a Cloud migration or comparing environments, some workflow behavior may change.

To understand what to expect, you can check which JEP workflow enhancements are currently used in your Data Center workflows. Each enhancement has a unique module key that you can identify directly (for example, by querying the database).

The lists below show all JEP workflow enhancement module keys, grouped by conditions, functions, and validators, so you can easily review which enhancements are applied in your environment.

Workflow conditions:

plugin.jepjep-wf-condition-previous-status
plugin.jepjep-wf-condition-not-reporter
plugin.jepjep-wf-condition-parent-issue-jql
plugin.jepjep-wf-condition-user--custom-field
plugin.jepjep-wf-condition-user-not-in-role
plugin.jepjep-wf-condition-user-has-any-role
plugin.jepjep-wf-condition-user-in-role
plugin.jepjep-wf-condition-user-in-group-role
plugin.jepjep-wf-condition-issue-in-status
plugin.jepjep-wf-condition-date-comparison

Workflow functions:

plugin.jepjep-wf-function-assign-to-user-in-role
plugin.jepjep-wf-function-notify-when-a-field-has-been-set
plugin.jepjep-wf-function-notify-overdue-transition
plugin.jepjep-wf-function-assign-issue-based-on-a-property
plugin.jepjep-wf-function-assign-issue-to-user-in-customfield
plugin.jepjep-wf-update-linked-issues-customfield
plugin.jepjep-wf-update-linked-issues-field
plugin.jepjep-wf-add-field-aswatcher-to-parent-issue
plugin.jepjep-wf-add-smart-select-assignee

Workflow validators:

plugin.jepjep-field-has-been-set-validator
plugin.jepjep-parent-issue-status-validator
plugin.jepjep-parent-issue-jql-validator
plugin.jepjep-subtasks-jql-validator
plugin.jepjep-user-in-project-role-validator
plugin.jepjep-wf-validator-date-comparison