How can I avoid having 'Removed Fields' when switching from one issue type scheme to another?

[sudesh varma]

Hi, I am currently working to switch my project from one Issue Type Scheme to another.

Some of the issue types in the old scheme will not be used in the new scheme. However, to not lose the issues with these issue types in the new structure, I have created placeholder issue types in the new scheme.

Now, at the time of switching the project from old issue type scheme to the new one, I have mapped the issue types that will not be used from the old one to the placeholder issue types and for each of them, I saw a confirmation that the old values will be retained. When I get to the summary step where I review and confirm I see a set of fields that will be removed, how can I avoid these and ensure that all fields in the old issue type get retained in the new placeholder issue type?

[Geert Graat]

Hi,

If you have a Text custom field, you can choose to use the Wiki Renderer for that field in the Field configuration. This allows you to use wiki markup, including mentions [~username].

Regards,

Geert

[Sean Dadds]

Hi Geert, I am using wiki renderer for the text field but when using @Jonathan Ward, it just gives a link to the user's profile. It does not give a notification like using the @ markup. Thanks for the reply.

[John Bayne]

We're on 6.3.

Just tried this and it doesn't appear to work in custom fields. Not aware of any mechanism to enable it.