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

[Tiago Comasseto · Accepted solution]

Hi Dario, the Domain Users group is an special group in AD, it's called primery group. By default all users in AD are members of this group, but its membership association is different than the other groups, this group doesn't have the attribute MemberOf.

Currently JIRA doesn't support primery groups, but there's already an improvement request to implement this ability: https://jira.atlassian.com/browse/JRA-29187

As a workaround, you may associate the user your want to see in JIRA with another LDAP group or set up the User Directory so that it uses the Default Group Membership functionality.

I hope it helps