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; } } }

move issues between two "team managed" projects

Yaron Norani

Hi,

I hav e ateam tha works with a team namaged project.

They use set of custom fileds.

we would like to use additional similar TMP (team managed project) tha uses a similar set of custom fields.

We have created again the set of fields and values in the new project .

When we try to "move" issues between the projects the custom filed values were not detected and copied.

How can we solve it.

We would like to be able to move an issue between two TMP projects and as a result , all field values, including custom field values, will remain.

Accepted answers

Trudy P Claspill

Hello @Yaron Norani

Custom fields created within a Team Managed project are unique to that project. Creating a custom field in another TMP project with the same name is creating a new, separate custom field.

When you Moved the issue you should've seen a screen something like this:

Screen Shot 2023-07-24 at 12.34.26 PM.png

On this screen did you map your source custom fields to comparable custom fields in the destination project?

One way that TMP projects can "share" custom fields is for a Jira Administrator to create the custom field through Jira Settings > Issues > Custom Fields, give the custom fields Global Context, and then for each TMP project to search for and add that Global Context field to their project. This is the only way that TMP projects can truly share a single field. Then and only then will the TMP projects be adding data to the "same" custom field in the backend.

All comments

Trudy P Claspill

Hello @Yaron Norani

Custom fields created within a Team Managed project are unique to that project. Creating a custom field in another TMP project with the same name is creating a new, separate custom field.

When you Moved the issue you should've seen a screen something like this:

Screen Shot 2023-07-24 at 12.34.26 PM.png

On this screen did you map your source custom fields to comparable custom fields in the destination project?

Yaron Norani

@Trudy P Claspill , thanks for the reply.

Regarding your question:

On this screen did you map your source custom fields to comparable custom fields in the destination project?

Answer: I had to choose value and not field name. In that case , I will have to fill in all values.

Is there any mapping file , as exist when you import from CSV?

Is there are other "magical" option beside creating the custom fields again, as global?

Trudy P Claspill

There is no mapping file that can be used with the Move function.

You could attempt to update the already Moved issues by doing a CSV import to update the fields (rather than importing new copies of the issues).

There are no native methods to map the values of custom fields in one TMP project to separate custom fields in another TMP project via the Move operation.

Yaron Norani

Ok thanks @Trudy P Claspill

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud