We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-26358

LifecycleAware onStart timing for plugin components is not consistent across different scenarios

      In my findings (https://developer.atlassian.com/display/JIRADEV/JIRA+Plugin+Lifecycle), the LifecycleAware onStart method seems to be called after PluginEnabledEvent occurs when starting up JIRA, but well before PluginModuleEnabledEvent when installing/enabling a plugin.

      This lack of consistency in timing makes it difficult for plugin developers to write useful code for the LifecycleAware onStart method.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Data Center'
            1. Jira Data Center
            2. JRASERVER-26358

            LifecycleAware onStart timing for plugin components is not consistent across different scenarios

                In my findings (https://developer.atlassian.com/display/JIRADEV/JIRA+Plugin+Lifecycle), the LifecycleAware onStart method seems to be called after PluginEnabledEvent occurs when starting up JIRA, but well before PluginModuleEnabledEvent when installing/enabling a plugin.

                This lack of consistency in timing makes it difficult for plugin developers to write useful code for the LifecycleAware onStart method.

                        Unassigned Unassigned
                        mtokar Michael Tokar
                        Votes:
                        12 Vote for this issue
                        Watchers:
                        17 Start watching this issue

                          Created:
                          Updated:

                            Unassigned Unassigned
                            mtokar Michael Tokar
                            Affected customers:
                            12 This affects my team
                            Watchers:
                            17 Start watching this issue

                              Created:
                              Updated: