nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can you display jira tickets from one project to another?

Knirke Jensen

We have projects from two different teams that have interdependencies. However, the two teams do not work with the same status categories. Is there a way to map them across so one can be displayed in the other, but the original project "rules" the status?

Accepted answers

Mikel Garcia Bartolome

Hey @Knirke Jensen you can manage interdependencies between teams with different workflows and status categories by mapping statuses between projects while maintaining the original project’s status as the "source of truth."

Approaches to Mapping Statuses Across Teams

1. Automation Rules

Use Jira Automation to mirror or translate statuses between projects.

Steps:
1. Go to Project Settings > Automation in both projects.
2. Create a rule in the dependent project:
  - Trigger: "Issue updated" (watch for status changes in the original project).
  - Condition: Filter issues with JQL from the other project (e.g., project = "Team A" AND status CHANGED).
  - Action: Update the status in the dependent project to the corresponding status in its own workflow.
3. Define the mapping logic within the rule:
  - Example:
    - Original Project: In Progress → Dependent Project: Ongoing.
    - Original Project: Done → Dependent Project: Completed.

2. Custom Fields

Use a custom field (e.g., "Linked Status") to display the status from the original project in the dependent project.

Steps:
1. Create a custom field (e.g., Linked Status) and add it to the dependent project's screens.
2. Use Jira Automation or a scripting tool (e.g., ScriptRunner) to copy the status from the original project into this field whenever it changes.
3. Team members in the dependent project can see the "source of truth" status without needing direct synchronization.

3. Advanced Roadmaps (Jira Premium)

Use Advanced Roadmaps to create a consolidated view of statuses across projects.

Steps:
1. Configure the plan to include issues from both projects.
2. Use custom issue filters and views to create a status mapping or overlay.
3. Display both teams' statuses in the roadmap while aligning them logically.

4. Unified Status Mapping with a Shared Workflow

If the statuses differ only in naming, you can use a shared workflow with custom mappings for display.

Steps:
1. Create a unified workflow with all potential statuses.
2. Map each team's statuses to the unified workflow:
  - Example: Map Team A's "In Progress" to Team B's "Ongoing".
3. Use the board configuration in each team’s project to display only the relevant statuses:
  - Go to Board Settings > Columns and drag statuses into columns accordingly.

All comments

Marc -Devoteam-

Hi @Knirke Jensen

No this can't be done.

You can create a new board on both projects and map multiple statuses to the same column on the board.

Otherwise if this is not a solution in your case, the teams should work with an identical workflow.

I would recommend if the projects are not of the type company managed, to also start using this type instead of team managed, you can't create cross project boards and types can adjust the workflow to their liking

Mikel Garcia Bartolome

Approaches to Mapping Statuses Across Teams

1. Automation Rules

Use Jira Automation to mirror or translate statuses between projects.

Steps:
1. Go to Project Settings > Automation in both projects.
2. Create a rule in the dependent project:
  - Trigger: "Issue updated" (watch for status changes in the original project).
  - Condition: Filter issues with JQL from the other project (e.g., project = "Team A" AND status CHANGED).
  - Action: Update the status in the dependent project to the corresponding status in its own workflow.
3. Define the mapping logic within the rule:
  - Example:
    - Original Project: In Progress → Dependent Project: Ongoing.
    - Original Project: Done → Dependent Project: Completed.

2. Custom Fields

Use a custom field (e.g., "Linked Status") to display the status from the original project in the dependent project.

Steps:
1. Create a custom field (e.g., Linked Status) and add it to the dependent project's screens.
2. Use Jira Automation or a scripting tool (e.g., ScriptRunner) to copy the status from the original project into this field whenever it changes.
3. Team members in the dependent project can see the "source of truth" status without needing direct synchronization.

3. Advanced Roadmaps (Jira Premium)

Use Advanced Roadmaps to create a consolidated view of statuses across projects.

Steps:
1. Configure the plan to include issues from both projects.
2. Use custom issue filters and views to create a status mapping or overlay.
3. Display both teams' statuses in the roadmap while aligning them logically.

4. Unified Status Mapping with a Shared Workflow

If the statuses differ only in naming, you can use a shared workflow with custom mappings for display.

Steps:
1. Create a unified workflow with all potential statuses.
2. Map each team's statuses to the unified workflow:
  - Example: Map Team A's "In Progress" to Team B's "Ongoing".
3. Use the board configuration in each team’s project to display only the relevant statuses:
  - Go to Board Settings > Columns and drag statuses into columns accordingly.

Nic Brough -Adaptavist-

This does not display issues in one project in another one.

It's an AI answer that does not understand that. It is answering a question more like "How do I make two project work the same way?"

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud