Jira SAFe plugin

Connect supports several Jira plugins, such as the SAFe plugin, the Jira Elements Connect (nFeed) plugin, and the ScriptRunner plugin.

This topic describes how to use the Jira SAFe Epic to Feature Translator plugin to translate a Jira epic to a feature.

Overview of the SAFe plugin

The Jira SAFe plugin translates the epic (in English) and/or equivalent language specific equivalents for other locales. Connect expects a Jira epic to be named Epic, and when it encounters a name other than that, it may fail. The following sections describe how to use the plugin to avoid these failures.

The Jira SAFe Translator plugin uses the term "Feature" to describe the Jira "Epic". In order to accommodate this behavior, you must set a locale in which you reinstate the original term of "Epic" and configure the data source user to use that locale.

You should aim to choose a locale that is unused in your Jira data center. The recommended locales are English (UK) or English (USA).

Back to top

Configure as an administrator

Follow these steps to configure the Jira Administrator settings.

  1. Log in to Jira as an administrator.
  2. Click the Manage Apps tab.
  3. At the Atlassian Marketplace for Jira, select SAFe Translator plugin menu > Configuration. The SAFe EPIC to Feature Translator configuration page opens.

  4. Unlock the custom fields:

    1. Make sure the Unlock the fields radio button is black indicating that the fields are unlocked.

    2. From the Choose locale dropdown menu, select English (UK).

    3. From the Translate the 'Epic' labels to dropdown menu, select Epic.

    4. Click Next.

  5. Translate the custom fields:

    1. Go to Administration > Issues > Custom fields.

    2. Click Translate and enter new values in the Field Name box for each custom field : Epic Color, Epic Link, Epic Name, Epic Status.

    3. Click Next.

  6. Lock the custom fields:

    1. Make sure the Unlock the fields radio button is green indicating that the fields are locked.
    2. Clear the cache.
    3. Click Next.

Back to top

Configure as a unique user

Follow these steps to configure your unique data source user settings.

  1. Log in to Jira as a unique Connect data source user.
  2. In the profile section, under Preferences, click the pencil Edit button.
  3. In the Update User Preferences menu, select English (UK) from the Language dropdown, and click Update.

Back to top

Translate existing Jira data sources

If you have Connect Jira data sources that were created before performing these configurations, you may receive error messages informing you that those features are no longer present. To correct this, you can do one of the following:

  • Define a new Connect Jira data source after the changes are made.

  • Trim the Feature type from the existing data sources. This is done by using the trimJiraTypes<dataSourceName> argument in the Connect REST client command mfcFullRestClient.jar.

    For details, see SSL/TLS configuration.

    The operation updates the specified data source to include only the types used in connections that involve the data source. This also results in improved performance.

Back to top