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?

    CommentAdd your comment...

    2 answers

      Hi Srinivas, I agree with Nic that your projects are without any schemes now. I have never used getProjectsNoSchemes, but if i understand the documention correctly it returns a Project object without any scheme information i.e. notificationScheme is null in this object. When you update this object it might write back the null schemes to the project and cause that behaviour. Also not sure if you might see the null schemes only after restarting Jira. So have a closer look at the schemes ...
      1. srinivas patruni

        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.

      2. Dieter
        What might help is to get the project once again using getProjectByKey before you call updateProject. This might fix the problems with the schemes but would still leave the problem with default assignee. i'd prefer to write a short Groovy script that loops over all projects and updates them on the server. When you install the Groovy script runner plugin there is already a script skeleton displayed in the text box where you can enter the script. I think it s not possible right now with the existing Apis since i also haven't found a Rest api in 4.4. if for some reason you have to do that remotely you could also write your own webservice module or servlet module that just updates the name.
      3. Dieter
        Update: sorry it's too early for me. Jcli also does not seem to allowcupdating the project name. So i suggest to go the groovy way
      4. Dieter
        ok, i forgot the JClI command line tool that CAN do it remotely. not sure, but i think Bob posts the same data as when you edit the project in thevuser interface.
      5. srinivas patruni

        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?

      6. srinivas patruni

        If it is not a straight forward approach, that should be mentioned in the api.

      7. Dieter

        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.

      8. srinivas patruni

        Thanks for your explaination Dieter!

      CommentAdd your comment...

      Did you accidently removed the notification schemes from the project? It is diffcult to do that 'accidently' via code though!

      1. srinivas patruni

        No. I have not touched that. Also observed the Default Assignee field is found as Unassigned.

      2. Jobin Kuruvilla [Go2Group]

        You might want to check the email server and such.

      3. srinivas patruni

        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){
        				jiraSoapService.updateProject(authToken, project);
        		} catch (RemotePermissionException e) {

      4. Jobin Kuruvilla [Go2Group]

        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!

      5. srinivas patruni

        Hi Jobin,

        Any update on this please?


      6. srinivas patruni

        This is absolutely what i had executed and did nothing else. Any other reasons?

      CommentAdd your comment...