Skip to main content
Version: Version 22

import SelfguideEmbed from '@site/src/components/selfguide/SelfguideEmbed';

Jira teams

Introduction​

What is Jira team configuration? After creating the Jira application link, the next step is to configure how Jira teams are used in Fortes Change Cloud. This involves two parts:

  1. Creating a team configuration: defines how FCC and Jira exchange information, including issue types and field mappings.
  2. Adding Jira teams: makes teams available in Fortes portfolios, programs, or projects so work items can be exchanged.

The level at which you configure teams (portfolio or program/project) determines the granularity of the data exchange.

Who uses it?

  • Administrators and integration specialists who configure the Jira integration.
  • Portfolio and program managers who use Jira teams in FCC to align planning and execution.

What value does it deliver?

  • Links Jira teams to the correct level in FCC (portfolio or program/project), enabling structured data exchange.
  • Keeps FCC planning and Jira execution in sync through field mappings and issue type configuration.
  • Provides flexibility to support both SAFe-style Epic-level and Feature-level integrations.

Create a new configuration for team setup​

Configurations determine the level at which Jira teams can be selected in Fortes:

  • Jira teams selectable in portfolios
    Choose this level if full initiatives (Epics in SAFe terminology) should be passed to Jira.

  • Jira teams selectable in programs/projects
    Choose this level if the connection should be based on items from programs or projects (Features in SAFe terminology).

Steps to create a configuration​

  1. Click the ⋮ menu above the list at the level where you want information exchange.

  2. Select Manage configurations.

  3. In the configuration list, click + Add Configuration.

  4. Enter a Name for the configuration.

  5. Under Jira application link, select the link created earlier.

  6. Choose the Issue type that Fortes Change Cloud should use when creating items in Jira.

  7. Set up Field mappings for both directions:

    • Jira → Fortes Change Cloud: select a Jira field on the left and map it to the corresponding Fortes field on the right.
    • Fortes Change Cloud → Jira: select a Fortes field on the left and map it to the corresponding Jira field on the right.

      You can include as many field mappings as needed.

  8. Click Create to save the configuration.

The new configuration will now appear in the list and can be used when adding teams.

Create Jira teams in Fortes Change Cloud​

Once a configuration is in place, you can add Jira teams. These teams become available in the Fortes team overview and can be used in functional apps.

Steps to add a Jira team​

  1. Click + Add Team above the team list.
  2. Enter the Name of the team.
    • Optionally, add a Short Name (3 letters).
  3. (Optional) If time registration is needed, add users in the Members for time registration field.
  4. In the Configuration field, select the configuration created in the previous step.
  5. Under Jira team board identification, choose the Jira Project.
    • The option Project fixed will be selected automatically; pick the relevant Jira project from the dropdown.
  6. (Optional) Add one or more additional fields under Jira team identification to send fixed values.
    • This is useful if Jira board filtering relies on specific field values.
  7. Click Createto add the team.

The team will now appear in the team overview list.

Jira teams for time registration​

Linked Jira team members can register time on Portfolio or program items via the Hours app. To enable this:

  1. Create a Jira team or edit an existing one.
  2. Add the members who should register time in the Members for time registration field.
  3. Push a Portfolio item or program item to Jira. At that moment a Jira team is linked to the item; only then can its members register time on it.

The members can then register time on the item via the Hours app.

Best practices​

  • Choose the level deliberately: use portfolio-level configuration for full initiatives (Epics) and program/project-level for individual items (Features). See Jira teams in programs and projects.
  • Reuse configurations: one configuration can serve multiple teams that share the same issue type and field mappings.
  • Map only the fields you need: every field mapping adds synchronization overhead. Keep it to what the teams actually use.
  • Add a short name to keep teams recognizable in the team overview and on items.

FAQ​

What is the difference between configuring teams in portfolios versus programs/projects? The level determines what is exchanged: portfolio-level passes full initiatives (Epics), program/project-level passes individual items (Features). See Jira teams in programs and projects.

How do Jira team members register time? Add them to Members for time registration and push an item to Jira; they can then book time on that item via the Hours app.

Is the data exchange one-way? No. Field mappings are configured for both directions, and synchronization is continuous in both directions.

Can I add a team without choosing a configuration? Depending on your version, teams can be added without selecting a configuration. In that case no field mapping or issue type exchange is set up for that team.

Need more support?​

For step-by-step instructions or troubleshooting, contact your Fortes Change Cloud administrator or consult in-app help.