1. Dashboard Migration
  2. Skip Unsupported Automation Rules
  3. Skip App Outdated Check
  4. Skip Invalid Workflow Rules
  5. Skip Users
  6. Project Configuration Only
  7. Enable Archived Issues as Unarchived
  8. Export All Filters
  9. Export Multiple Projects’ Boards

Beyond the familiar functionalities, Jira offers a set of hidden features known as “Dark Features” that provide additional capabilities, customization, and flexibility for users. In this blog post, we’ll shed light on some of these dark features, explaining their purpose and how you can leverage them to enhance your Jira experience.

Accessing Jira’s dark features is a straightforward process that allows you to enable additional functionalities and customization options within the platform. Here’s a step-by-step guide on how to access and activate dark features in Jira:

  1. Navigate to the Dark Features Page: To access the dark features in Jira, you need to go to a specific URL within your Jira instance. Open your web browser and enter the following URL, replacing <Jira_URL> with the actual URL of your Jira instance:javascriptCopy code<Jira_URL>/secure/admin/SiteDarkFeatures!default.jspa This URL will take you to the Dark Features management page.
  2. Input the Dark Feature Key: Once you’re on the Dark Features management page, you’ll see an option to input the dark feature key you want to enable. In your example, the dark feature key is com.atlassian.jira.migration.dashboard-migration.feature.
  3. Click Add: After entering the dark feature key, click the “Add” button. This action will activate the dark feature, making it available for use within your Jira instance.

Dashboard Migration

Key: com.atlassian.jira.migration.dashboard-migration.feature)

  • Why use it: Dashboard migrations are not supported by default in Jira Cloud Migration Assistant (JCMA). Enabling this dark feature allows you to migrate dashboards to the cloud.
  • How to use it: Dashboards are global entities and may not fit neatly into JCMA’s Project-By-Project (PBP) migration approach. It’s recommended to migrate dashboards as the last step using a dummy project. Enabling this feature flag is crucial for a successful migration, as JCMA may not handle all dependencies automatically.
  • Risks and Caveats: Some gadgets might not be migrated due to missing dependencies. Admins won’t be able to migrate system dashboards, and certain gadgets like Crucible Charts and Fisheye Recent ChangeSets are not supported.

Skip Unsupported Automation Rules

Key: com.atlassian.jira.migration.skip.unsupported.automation.rule

  • Why use it: Jira Service Management (JSM) projects may contain automation rules from third-party plugins not supported by JCMA. Enabling this feature excludes such automation rules from migration.
  • How to use it: This feature helps unblock project migration by excluding unsupported automation rules. If you encounter issues with these rules, consider skipping them or addressing them manually.

Skip App Outdated Check

Key: com.atlassian.jira.migration.skip.app.outdated.check

  • Why use it: This feature allows you to skip pre/post migration reports, which can lead to migration delays in some cases.
  • How to use it: Admins can review migration information before enabling this feature. It’s advisable to run the check at least once before disabling it.
  • Risks and Caveats: Skipping this check may limit your visibility into migration-related issues. It’s recommended for experienced users who are confident in their migration setup.

Skip Invalid Workflow Rules

Key: com.atlassian.jira.migration.skip.invalid.workflow.rule

  • Why use it: This dark feature enables you to skip invalid structured workflow rules during migration.
  • How to use it: The default export process includes all rules, but some might be incompatible. You can choose to skip these rules using this feature or fix them manually.

Skip Users

Key: com.atlassian.jira.migration.skip.users

  • Why use it: This feature skips users and groups in subsequent migrations, allowing you to define who you want to migrate.
  • How to use it: After migrating all users to Atlassian Cloud initially, you can enable this feature to exclude users and groups from future migrations.
  • Risks and Caveats: Be cautious when using this feature, as it limits the migration of users. It’s recommended as a last resort when dealing with specific migration scenarios.

Project Configuration Only

Key: com.atlassian.jira.migration.project.configuration.only

  • Why use it: This dark feature enables you to migrate projects with their required configuration but without the associated issues.
  • How to use it: It’s useful if you want to start fresh without migrating issue history or if you need to narrow down migration issues related to configuration.

Enable Archived Issues as Unarchived

Key: com.atlassian.jira.migration.enable.archived-issues-as-unarchived

  • Why use it: Use this dark feature to migrate archived issues as normal, unarchived issues.

Export All Filters

Key: com.atlassian.jira.migration.export.all.filters

  • Why use it: This dark feature allows you to export all filters during a migration.
  • How to use it: By enabling this feature, you ensure that all filters from your Jira instance are included in the migration process. This can be beneficial if you have a large number of filters and want to maintain consistency in your cloud environment.
  • Risks and Caveats: Be mindful of the volume of filters you have, as including all of them might increase the overall migration time and complexity.

Export Multiple Projects’ Boards

Key: com.atlassian.jira.migration.export.multiprojects.boards

  • Why use it: This dark feature facilitates the export of boards from multiple projects in a single migration.
  • How to use it: By enabling this feature, you can streamline your migration process by exporting boards from multiple projects simultaneously.

📢 👉 You may also want to read this post: Migrating Boards, Dashboards, and Filters to Jira Cloud