I updated proejct names via SOAP. After that i found that email notifications have disabled for all projects. Everything else is found working. Any idea about why this has happend?
Community moderators have prevented the ability to post new answers.
Hi Dieter, It is not mentioned in the api that getProjectsNoSchemes method will return array of projects by making the Schemes to null. I also observed that the Default Assignee field is found as Unassigned after updating the projects.
So please let me know if there is any better way to fetch all the projects in JIRA for renaming the projects.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Dieter, Thanks for your information. I have one question.. Regarding the updatiion of projects using soap, is it ia known issue from atlassian side or it is an issue with the api?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If it is not a straight forward approach, that should be mentioned in the api.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
IMHO the RPC plugin definitely has a bug since it does not even try to preserve the default assignee. Look at the source code here:
The code simply assumes the assignee is null (last argument) !
// result is used later to update project so there cannot be an assignee
com.atlassian.jira.bc.project.ProjectService.UpdateProjectValidationResult result = projectService.validateUpdateProject(user, rProject.getName(), rProject.getKey(), rProject.getDescription(), rProject.getLead(), rProject.getProjectUrl(), null);
Also the schemes are definitely set to null if the schemes in rProject are null as they are if you get them using getProjectsNoSchemes like you. There should be a corresponding method updateProjectNoSchemes which simply ignores the schemes and also preserves the default assignee of the project.
I could be wrong and might have looked at an outdated version of the RPC plugin but at least the code i have found explains why you lost the schemes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your explaination Dieter!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did you accidently removed the notification schemes from the project? It is diffcult to do that 'accidently' via code though!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No. I have not touched that. Also observed the Default Assignee field is found as Unassigned.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You might want to check the email server and such.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
They are also up and running. Please find the below code snippet used for updation.
try {RemoteProject[] remoteProjects = jiraSoapService.getProjectsNoSchemes(authToken);
for(RemoteProject project : remoteProjects){ project.setName(project.getKey()+"-"+project.getName()); jiraSoapService.updateProject(authToken, project); System.out.println(project.getName()); } } catch (RemotePermissionException e) { System.out.println(e.toString()); }
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The above code looks fine to me and I don't think that caused you any issues. It must be something else that you have done!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jobin,
Any update on this please?
-Srinivas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is absolutely what i had executed and did nothing else. Any other reasons?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.