Why did my Jira issues vanish?

[poma...@googlemail.com]

Hi there,

some weeks ago I created some issues for the maven-metadata-plugin in the Jenkins Jira. The issues are backing some pull request for the plugin. Now I noticed that two of the issues have vanished in the meantime:

• JENKINS-29432: Repository password should not be stored unencrypted
• JENKINS-29433: Information about currently used artifact

Can anybody tell me why these issues may have been disappeared?

Kind regards

Marc

[Christopher Orr]

On 11/08/15 13:22, poma...@googlemail.com wrote:
> Hi there,
>
> some weeks ago I created some issues for the maven-metadata-plugin in
> the Jenkins Jira

> <https://issues.jenkins-ci.org/issues/?jql=project%20%3D%20JENKINS%20AND%20component%20%3D%20maven-metadata-plugin>.

> The issues are backing some pull request for the plugin

> <https://github.com/jenkinsci/maven-metadata-plugin/pulls>. Now I

> noticed that two of the issues have vanished in the meantime:
>

> * JENKINS-29432: Repository password should not be stored unencrypted
> * JENKINS-29433: Information about currently used artifact

>
> Can anybody tell me why these issues may have been disappeared?

If you posted between the 15th and 17th of July, you may have been an
unlucky victim of the database outage at the end of the month:

http://jenkins-ci.org/content/wiki-and-issue-tracker-outage-over-weekend

http://osuosl.org/blog/mysql1-vip-post-mortem -- "though most data could
be restored, some data from between the 15th and the 17th was lost."

Regards,
Chris

[Daniel Beck]

On 12.08.2015, at 12:28, Christopher Orr <ch...@orr.me.uk> wrote:

> http://jenkins-ci.org/content/wiki-and-issue-tracker-outage-over-weekend
>
> http://osuosl.org/blog/mysql1-vip-post-mortem -- "though most data could
> be restored, some data from between the 15th and the 17th was lost."

Ouch. Looks like I was a bit too optimistic in the blog post. I'll try to find the affected issues and notify the creators.

[poma...@googlemail.com]

Hi Daniel,

hi Christopher,

many thanks for the information and for having a look!

FYI: I just checked some local records and I am almost sure that I created the tickets on July 22nd.

Kind regards

Marc

[Björn Pedersen]

Hi,

I just tested by manually changing the urls:

It looks like issues from  JENKINS-29432 up to  JENKINS-29468 are missing.

JENKINS-29431 created 15/Jul/15 12:09 PM is still accessible

JENKINS-29469 created 17/Jul/15 5:43 AM is accessible again.

[Daniel Beck]

I've come to the same conclusion in https://jenkins-ci.org/content/update-wiki-and-issue-tracker-outage

I'm currently writing an email to all affected users, asking them to re-post everything that's still relevant. Thanks to the jenkinsci-issues list, we know most of what was lost.

[poma...@googlemail.com]

OK, seems like my local records where misleading. My ticket must have been created in the period You mentioned. Bad luck :(

I think I'll recreate the issues some time the next days, but with just a very basic description ...