Community Announcements have moved! To stay up to date, please join the new Community Announcements group today. Learn more
×When I attempt to move an issue (task) from one TMP to another, it fails on step 1 of 2, saying that I have a problem, specifically with "Task issues may have different field settings than your source project". It is asking that I re-map or retain. Neither option allows me to migrate the task. I set both projects up the exact same and even created a test project, with no luck. I have custom fields for both projects, but they were created the same. I have the correct permissions as I am an admin on both projects. Any help would be much appreciated.
Welcome to the Atlassian Community!
Fields in TMPs are local to the project, they are not shared. Even if they have the same name and configuration, they are not the same field.
The contents of components and versions are the same, for both CMP and TMP types!
If you were to convert your custom fields to global custom fields (i.e. add a global field, and then script something to copy from the local custom field into them), they you will find the global fields transfer fine, without any need to map.
But I'm afraid moving TMP issues without that (and any issues with components and versions) is not going to work without copying or mapping.
Thanks Nic!
This pieces seems to discuss custom fields with global context (https://confluence.atlassian.com/adminjiraserver/custom-fields-with-global-contexts-956713282.html), but it appears to be for data center vs. cloud. Would the version make a difference in the ability create fields that would enable passing tasks between projects?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There appears to be a way to add global context.
To add global context:
Select > Issues > Fields > Custom fields.
Find the custom field you want to configure, select > Contexts and default value.
Select Edit context. Alternatively, you can add a new context.
Go to Choose applicable issue types and select Any issue type.
Go to Choose applicable context and select Global context.
Select Modify.
support.atlassian.com/jira-cloud-administration/docs/edit-a-custom-field-context/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, those are the global fields I mentioned.
They are not the TMP-local fields you have already got. You will need to move the data from the TMP-local fields into global ones.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.