Thanks all for the tips. bulk moving the issues to the TEST project and back fixed it.
/James On Monday, 6 July 2020 15:57:13 UTC+1, Mark Waite wrote: > > I saw the same problem with several issues that had been created when Jira > was having serious issues (disc space, etc.). My ugly workaround was to > use "Move" to change the issue from one project to another, then use "Move" > again to change it back. When it came back to the same project, it could > then have its state changed and it behaved like a normal Jira issue. > > If you want me to apply that technique to the specific issue, let me know. > > On Mon, Jul 6, 2020 at 8:43 AM Devin Nusbaum <[email protected] > <javascript:>> wrote: > >> In my experience, this happens when someone tries to file a new issue >> while Jira is having problems. Jira reports that the issue couldn’t be >> created, so users try to submit the form again, and once the problem with >> Jira is resolved all of the submissions show up as duplicate issues where >> the status is broken and can’t be modified. What I normally do is clone one >> of the duplicates to get a new issue that isn’t broken, and then file an >> INFRA ticket asking admins to delete all of the duplicates. See >> https://issues.jenkins-ci.org/browse/INFRA-2581 as an example. >> >> On Jul 6, 2020, at 10:26, James Nord <[email protected] <javascript:>> >> wrote: >> >> Hi all, >> >> for some reason I can not close some specific Jira issues (other issues >> are fine)? >> anything in the following query seems like it can not change state : >> https://issues.jenkins-ci.org/browse/JENKINS-61646?jql=summary%20~%20%22attempt%20reconnect%22%20and%20component%20%3D%20kubernetes-credentials-provider-plugin%20 >> >> <https://issues.jenkins-ci.org/browse/JENKINS-61646?jql=summary%20~%20%22attempt%20reconnect%22%20and%20component%20=%20kubernetes-credentials-provider-plugin> >> >> <https://issues.jenkins-ci.org/browse/JENKINS-61637> >> >> /James >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/e7bf1ce7-1f61-4728-8cbc-b7d02b8294e4o%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/e7bf1ce7-1f61-4728-8cbc-b7d02b8294e4o%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CA01FD8E-366F-4BC2-BE24-6D9AA7B7D701%40cloudbees.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/CA01FD8E-366F-4BC2-BE24-6D9AA7B7D701%40cloudbees.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3cc6f069-a419-4648-871f-166ad6d8b702o%40googlegroups.com.
