Change Parent Due Date

[tracey.fudge]

I would like to adjust the parent due date based on a child issue due date being changed (for the future only).  Does this look right?  I am not sure how to test this so I created a campaign with my name to filter out just that campaign.  

[Flavio Beck · Accepted solution]

I have resolved using script runner:

import com.atlassian.jira.component.ComponentAccessor
import org.ofbiz.core.entity.ConnectionFactory
import org.ofbiz.core.entity.DelegatorInterface
import java.sql.Connection
import groovy.sql.Sql
import com.atlassian.jira.user.ApplicationUser
import com.atlassian.crowd.embedded.api.Group

log.warn ("--------START TO COPY GROUPS -----------")
def delegator = (DelegatorInterface) ComponentAccessor.getComponent(DelegatorInterface)
String helperName = delegator.getGroupHelperName("default")

// GET USERS AND GROUPS FROM OLD DIRECTORY (EVEN IT IS NOT THE ACTIVE DIRECTORY) 
Connection conn = ConnectionFactory.getConnection(helperName)
Sql sql = new Sql(conn)

def sqlUsers = """
 SELECT cu.lower_user_name, cg.lower_group_name
 FROM cwd_user cu
 JOIN cwd_membership cm
 ON cu.id=cm.child_id
 JOIN cwd_group cg
 ON cm.parent_id=cg.id
 WHERE cu.directory_id=10200 AND cg.directory_id=10200 //change to the source directory
 ORDER BY cu.lower_user_name
 """

def groupsByUser = [:]

try {
 def rows = sql.rows(sqlUsers)
 // MAP THE SQL RESULT TO A VARIABLE (TO CLOSE TO CONNECTION BEFORE TIMEOUT)
 groupsByUser = rows.collectEntries {
 [it.lower_user_name, it.lower_group_name]
 }

} finally {
sql.close()
}

// ADD GRUPS FOR EACH USER IN NEW DIRECTORY
groupsByUser.each{
 def user = it.key
 def group = it.value
 
 def userManager = ComponentAccessor.getUserManager()
 def appUser = userManager.getUserByKey(user)
 def groupManager = ComponentAccessor.getGroupManager()
 Group groupObj = groupManager.getGroup(group)
 ApplicationUser aUser = (ApplicationUser) appUser
 Long dir = aUser.getDirectoryId()

//check if user is really present in the destination directory
if (dir == 10304){ 
 log.warn ("Adding user: " +user + " -> to group: " +group)
 groupManager.addUserToGroup(aUser, groupObj)
 } else {
 log.warn ("user not in NEW AD: " +user)
 }
}

[Moses Thomas]

@Flavio BeckSo you need to  add  this new AD,  configure it  and change order in  user directory in  Jira, and you  will  still  have user's  in  Jira  internal  directory which  are not in  new AD.   Why  don't you  export users in  old AD  to  new  AD ?

[Flavio Beck]

Hello...  maybe my question was not celar...  I have updated that.

for users in my internal AD not present in new AD, there is no problem, its OK.

The problem is about users present in both Local AD and Corp AD.

When I disable local AD they will assume Corp AD groups (that does not are useful for me).

Off course I can set to manage goups locally, and add each Corp AD user to the proper group, like jira-users.

But note, How can I do that in a easy way ?

1500 users one by one?

[Moses Thomas]

@Flavio BeckWith a power shell  script will  perform this action  for  1500 users,

this i have no  script to  do this.

[Flavio Beck]

I have checked to use scriptrunner to do this, but Jira API does not have any method get or add users from an specific directory.

I am am testing to use scriptrunner with SQL instead of API calls

anyway thanks for help.