Can you have a task which is just a view on to a task in another space (project)?

[Jim Walsh]

Assume I have 2 separate spaces (Project A and Project B)

A piece of work exists which both spaces need to track for different reasons.  Is it possible to create a real task (Task A1) in Project A where the work is being done but create a task in Project B (Task B1) which is just a "view" into the Task A1 and always reflects the current state of Task A1?

This would eliminate the need to double track the progress of the work in 2 separate spaces and both spaces would know when the work is marked as DONE.

[Trudy Claspill]

Hello @Jim Walsh 

Welcome to the Atlassian community.

Can you provide more information about why you think you need a copy of the Task A1 created in Project B?

Is it not sufficient to simply let the team using Project B directly view Task A1 in Project A?

How do you want the users of Project B to view the issue; in their agile board, through search results, ...?

If you must have a copy of A1 in Project B, some things that need to be considered:

1. What is the space type of each space; Software, Service, or Business, and Team or Company Managed?
2. How are the spaces configured? Do they use the same workflows, screens, custom fields, etc?
3. If there is a copy of the issue in Project B, then the people who have access to modify issues in Project B will be able to modify that copy. Jira does not natively provide a method to make a single issue in a space non-editable in all statuses by the space users while leaving all other issues of the same type and statuses editable

[Jim Walsh]

Hi @Trudy Claspill,

Firstly thanks for the reply. As I am new to JIRA I'm probably not explaining this well.

I have an epic in my department space which is to track the implementation of a piece of software for our department,  There are lots of tasks in that epic for the department and our 3rd Party supplier. However there is also a task to produce a report from another system to feed into the software.

The team that will write the report track all of their work in a separate Reporting space because they need to keep all of their work in one place.  So they will create a task in their Reporting space for this piece of work,

So this means if I want to have a full record of the work done for the software implementation in my epic I have to create a task for the report creation.  I will link this to the task in the Reporting system and add myself as a Watcher on it. Then all I will need to do is mark the task as DONE in my space when it's marked as DONE in the Reporting space.

None of this is particular awkward but I was just wondering if there was a type of task that was literally just an internal pointer to the main task in the Reporting system so that I didn't even need to do anything on my task once I had created it.

Hope that's a bit clearer.

Jim

[Trudy Claspill]

Hello Jim,

Thanks for that additional information.

Are the teams using Kanban or Scrum boards to plan and organize their work?

What is the space type for each of these spaces? Get that by clicking on the ... next to the space name in the panel on the left.

There is not a native feature that keeps two work items synchronized. That would require writing Automation Rules.

There are a couple of ways to handle this, depending on the types of spaces being used.

If the Reporting team has permission to update the items in Project A, they could simply do that rather than creating a copy of the work item in their own space.

If the Reporting team uses a Scrum or Kanban board to manage their work, it might be possible (depending on space types) for the Reporting team to pull the original task into their own board to include with their work from the Reporting space, rather than making a copy of the item. There are a variety of ways that the original issue could be "flagged" so that the Reporting team could find it and add it into their board.

If the Reporting team is using a Team Managed space, adding the original issue to their board requires set up of a different board, which is a bit more complicated.