Note
We've packed up and moved from Confluence to Discourse to bring you a better, more interactive space. Out of courtesy we didn't migrate your user account so - you will have to signup again
The Exalate team will be on holiday for the coming days - returning Jan 4
Enjoy & stay safe
On the Github side of the connection I have the following :
issue.summary = replica.key + " " + replica.summary issue.description = replica.description //issue.reporter = nodeHelper.getUserByEmail(replica.reporter?.email) issue.labels = replica.labels issue.comments = commentHelper.mergeComments(issue, replica) if(replica.fixVersions) { issue.labels += nodeHelper.getLabel(replica.fixVersions.name) } if(replica.status.name == "Done"){ issue.status = nodeHelper.getStatus("closed") }else{ issue.status = nodeHelper.getStatus("open") } issue.labels += nodeHelper.getLabel(replica.status.name) issue.fixVersions = replica.fixVersions.collect { v -> nodeHelper.createVersion(issue, v.name, v.description) } issue.milestone = issue.fixVersions.nameI have a couple of problems I'd like to solve. 1. How can I make the status of the github issue be correct. They are always imported as open. 2. I'd like the reporter to match the github user - not the exalate bot. If I uncomment the reporter line it crashes. Otherwise it looks great. Thanks
1. How can I make the status of the github issue be correct. They are always imported as open.
Are you sure the JIra issue status name is Done?
2. I'd like the reporter to match the github user - not the exalate bot. If I uncomment the reporter line it crashes
Do the email of the users match between the two systems?
Thanks for the quick reply Juan.
Yeah, the status is definitely Done. I apply it as a label as well and I could probably just select all the issues with this label in Github and then close them but there's a lot so I'd really prefer if I could automate it. What are the correct status names for github? I assume "open" and "closed" or is there a boolean closed=true or something else?
The users should match on email. My only doubt here was if it had enough priveleges (I used a Personal Access Token) - I allowed all the repo permissions and read:user and user:email. I didn't see any permission errors anyway.
Here's what I see if I uncomment the getUserByEmail