Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-4446

After restarting Jira nearly 2 dozen previously enabled projects were no longer Greenhopper enabled

      We restarted the Jira process this morning and discovered nearly 2 dozen previously Greenhopper enabled projects were no longer enabled. We have re-enabled all of the ones we were certain had used Greenhopper previously, but won't know for sure if all projects have been re-enabled until our user base finishes reporting. We rely heavily on Agile development and this particular situation has caused a bit of a panic.

            [JSWSERVER-4446] After restarting Jira nearly 2 dozen previously enabled projects were no longer Greenhopper enabled

            Hi gbeckmann,

            If this has happened to you please log an issue at http://support.atlassian.com. This has not been a confirmed bug as of yet, but if we are able to reproduce this and find out the root cause with you then we will definitely have the cause and fix published in a public space for all of our customers.

            Cheers,

            Michael

            Michael Andreacchio added a comment - Hi gbeckmann , If this has happened to you please log an issue at http://support.atlassian.com . This has not been a confirmed bug as of yet, but if we are able to reproduce this and find out the root cause with you then we will definitely have the cause and fix published in a public space for all of our customers. Cheers, Michael

            It would be good to know for other users what is causing this issue, since we have exact the same problem. Do I have to create another ticket at http://support.atlassian.com? Thanks for the help.

            Vincent Pehrs added a comment - It would be good to know for other users what is causing this issue, since we have exact the same problem. Do I have to create another ticket at http://support.atlassian.com ? Thanks for the help.

            Hi Paul,

            Thanks for contacting Atlassian.

            This seems to be a support related issue and I'd like to help you in our support system http://support.atlassian.com please log the issue there and we will get onto your case ASAP.

            In future can you please raise support requests such as this by creating an issue in our support system, https://support.atlassian.com, not in http://jira.atlassian.com. As our support engineers respond to cases in https://support.atlassian.com, it will ensure that your problem gets addressed as quickly as possible. Also, https://support.atlassian.com is configured so that only Atlassian and you have access to the case, therefore it is a more appropriate location for us to gather any required system data and configuration from

            Cheers,

            Michael
            Atlassian Support

            Michael Andreacchio added a comment - Hi Paul, Thanks for contacting Atlassian. This seems to be a support related issue and I'd like to help you in our support system http://support.atlassian.com please log the issue there and we will get onto your case ASAP. In future can you please raise support requests such as this by creating an issue in our support system, https://support.atlassian.com , not in http://jira.atlassian.com . As our support engineers respond to cases in https://support.atlassian.com , it will ensure that your problem gets addressed as quickly as possible. Also, https://support.atlassian.com is configured so that only Atlassian and you have access to the case, therefore it is a more appropriate location for us to gather any required system data and configuration from Cheers, Michael Atlassian Support

            Moved to support

            Peter Obara added a comment - Moved to support

              mandreacchio Michael Andreacchio
              7152cdb8e92a Paul Jarman
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: