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?

[crochaju]

Have you looked at https://confluence.atlassian.com/kb/changing-port-that-your-atlassian-application-listens-on-834000041.html ?

try to change the port looking at:

Locate the Connectors

Find the following lines in server.xml:

1

<Server port="8006" shutdown="SHUTDOWN">

2

...

3

<Connector port="7990" protocol="HTTP/1.1"

4

                 connectionTimeout="20000"

5

                 useBodyEncodingForURI="true"

6

                 redirectPort="8443"

7

                 compression="on"

8

                 compressableMimeType="text/html,text/xml,text/plain,text/css,application/json"/>

Cheers

Carlos Rocha