Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-73173

Atlassian Jira Software Cloud Plugin unable to save site configuration

      I am setting up a Jira configuration from my Jenkins server. After entering all necessary parameters (Site Name, Webhook URL, Secret), I successfully tested the configuration and received a message saying, "Successfully validated site credentials." However, when I clicked the 'Save' button, I encountered the following error:

      "Cannot invoke 'com.atlassian.jira.cloud.jenkins.config.JiraCloudPluginConfig.configure(org.kohsuke.stapler.StaplerRequest, net.sf.json.JSONObject)' because 'this.config' is null."

      An image is attached. Does anyone have any idea why this might have happened?

          [JENKINS-73173] Atlassian Jira Software Cloud Plugin unable to save site configuration

          Omer created issue -

          Omer added a comment -

          Is there any update regarding this issue? bgvozdev 

          Omer added a comment - Is there any update regarding this issue? bgvozdev  

          David Drum added a comment -

          I am also seeing this in 2.452.1/2.0.14 but was able to create an entry in 2.414.3/2.0.14

          David Drum added a comment - I am also seeing this in 2.452.1/2.0.14 but was able to create an entry in 2.414.3/2.0.14

          David Drum added a comment -

          In 2.414.3, I get “Error Saving Connection: JSONObject["sites"] is not a JSONArray.” but the new (and, possibly importantly, initial) entry is saved.

          David Drum added a comment - In 2.414.3, I get “Error Saving Connection: JSONObject ["sites"] is not a JSONArray.” but the new (and, possibly importantly, initial) entry is saved.

          David Drum added a comment -

          I've been able to add an entry in 2.452.1/2.0.14 but still with the “Error Saving Connection: JSONObject["sites"] is not a JSONArray.” message.

          David Drum added a comment - I've been able to add an entry in 2.452.1/2.0.14 but still with the “Error Saving Connection: JSONObject ["sites"] is not a JSONArray.” message.

          Hi sgdave .

          I've resolved the issue `Error Saving Connection: JSONObject["sites"] is not a JSONArray.` and it will be out by tomorrow.

          However for the other error mentioned in the screenshot, I couldn't replicate it. Can you please share the full logs from your Jenkins server? i.e. `http://JENKINS_SERVER/jenkins/manage/log/all`

          Kayub Maharjan added a comment - Hi sgdave . I've resolved the issue `Error Saving Connection: JSONObject ["sites"] is not a JSONArray.` and it will be out by tomorrow. However for the other error mentioned in the screenshot, I couldn't replicate it. Can you please share the full logs from your Jenkins server? i.e. ` http://JENKINS_SERVER/jenkins/manage/log/all `

          David Drum added a comment - - edited

          Now on another 2.414.3/2.0.14 Jenkins instance, nothing is saved, no errors are returned, but in the logs I get this:

          2024-07-03 12:59:39.734+0000 [id=31412121]    SEVERE    c.a.j.c.j.c.ConfigManagementLink#doSaveConfiguration: Failed to submit form, please try again.null

          This was resolved by restarting the Jenkins instance.

          David Drum added a comment - - edited Now on another 2.414.3/2.0.14 Jenkins instance, nothing is saved, no errors are returned, but in the logs I get this: 2024-07-03 12:59:39.734+0000 [id=31412121]    SEVERE    c.a.j.c.j.c.ConfigManagementLink#doSaveConfiguration: Failed to submit form, please try again.null This was resolved by restarting the Jenkins instance.

          sgdave 

          I was not able to replicate this error locally nor in our prod test server. Can you please share the full logs so that I can narrow it down? 

          Kayub Maharjan added a comment - sgdave   I was not able to replicate this error locally nor in our prod test server. Can you please share the full logs so that I can narrow it down? 

          The new version 2.0.15 has been published, please update to that and see if the error still exists.

          If it does please do provide the full logs from your Jenkins server.

          Kayub Maharjan added a comment - The new version 2.0.15 has been published, please update to that and see if the error still exists. If it does please do provide the full logs from your Jenkins server.

          David Drum added a comment -

          Version 2.0.15 worked on the 2.452.1 instance of Jenkins that was previously throwing an error. Thank you.

          David Drum added a comment - Version 2.0.15 worked on the 2.452.1 instance of Jenkins that was previously throwing an error. Thank you.

            kmaharjan4 Kayub Maharjan
            omerfeldman Omer
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: