Bulk Clone In Jira Cloud

[Rakesh_Jajper]

Hi team,

We are trying different options for cloning issues - Scriptrunner - clone issue, Deep clone etc and running into some issues to keep issue number same like original project.

After deep diving we found out that issue keys for cloned projects are not matching with original issue.

For example: in URS if issue number is URS-19734, somehow in cloned project its assigning different number: SRP-17711 instead SRP-19734

Anyone got similar issues? Any suggestions how we can fix this?

We have requirement to keep the same number in different project as there are many places they refer this numbers? Project key will vary but we want the number to be same

Thanks

Rakesh

[Ernesto Castro]

Nop, I'm not using SSL... the problem is that IIS requires the user to authenticate using integrated security but as the link between the application is done from tomcat, and it is running as Local System, it is rejected by IIS.

[Rodrigo Girardi Adami]

Hi Ernesto,

Are you using SSL? I could find another question which the problem was the certificate.

If the case, I recommend to test without SSL and recreate the app links using trusted applications.

If you are able to connect to each other application, then I recommend to check the SSL settings and check if the certificates are correctly placed on each truststore of each application server.

Cheers,

Rodrigo