Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
  • Community
  • Q&A
  • Jira
  • Questions
  • I was testing jira import functionality on a project B by taking export of certain issues of project A. Now problem is that both project issues are same and have become interrelated.

Upgrade problems (8.3.3 -> 8.13.2)

Contemi-EUR: Dariusz Nowak
February 25, 2021

Hey,

I'm trying to upgrade my old 8.3.3 Jira to 8.13.2 (I believe LTS), my process is preety simple:

* Stop Jira

* Run atlassian-jira-core-8.13.2-x64.bin & atlassian-jira-software-8.13.2-x64.bin selecting option to upgrade existing Jira

** Not sure should I run both of them but tried only 2nd one (assuming software already has core inside) and no differerence

 

Then when I try to start Jira with all plugins (it works with --disable-plugins) I'm getting:

{code}

2021-02-25 16:34:01,343+0000 JIRA-Bootstrap ERROR      [c.a.jira.upgrade.PluginSystemLauncher] A fatal error occured during initialisation. JIRA has been locked.
org.picocontainer.injectors.AbstractInjector$UnsatisfiableDependenciesException: com.atlassian.jira.issue.index.IndexingStatsEventPublisher has unsatisfied dependency 'class com.atlassian.jira.issue.fields.DefaultFieldManager' for constructor 'public com.atlassian.jira.issue.index.IndexingStatsEventPublisher(com.atlassian.event.api.EventPublisher,com.atlassian.jira.datetime.DateTimeFormatterFactory,com.atlassian.jira.issue.fields.DefaultFieldManager,com.atlassian.jira.security.JiraAuthenticationContext,com.atlassian.jira.cluster.ClusterManager)' from JIRAContainer_2021-02-25T16:32:42.710Z:1663<|
        at org.picocontainer.injectors.ConstructorInjector.getGreediestSatisfiableConstructor(ConstructorInjector.java:191)
        at org.picocontainer.injectors.ConstructorInjector.getGreediestSatisfiableConstructor(ConstructorInjector.java:110)
        at org.picocontainer.injectors.ConstructorInjector.access$100(ConstructorInjector.java:51)
        at org.picocontainer.injectors.ConstructorInjector$1.run(ConstructorInjector.java:331)
        at org.picocontainer.injectors.AbstractInjector$ThreadLocalCyclicDependencyGuard.observe(AbstractInjector.java:270)
        at org.picocontainer.injectors.ConstructorInjector.getComponentInstance(ConstructorInjector.java:364)
        at org.picocontainer.behaviors.AbstractBehavior.getComponentInstance(AbstractBehavior.java:64)
        at org.picocontainer.behaviors.Stored.getComponentInstance(Stored.java:91)
        at org.picocontainer.behaviors.AbstractBehavior.getComponentInstance(AbstractBehavior.java:64)
        at org.picocontainer.behaviors.Locked.getComponentInstance(Locked.java:40)
        at org.picocontainer.DefaultPicoContainer.getInstance(DefaultPicoContainer.java:698)
        at org.picocontainer.DefaultPicoContainer.getComponent(DefaultPicoContainer.java:646)
        at org.picocontainer.DefaultPicoContainer.getComponent(DefaultPicoContainer.java:631)
        at org.picocontainer.parameters.BasicComponentParameter$1.resolveInstance(BasicComponentParameter.java:118)
        at org.picocontainer.parameters.ComponentParameter$1.resolveInstance(ComponentParameter.java:136)
        at org.picocontainer.injectors.SingleMemberInjector.getParameter(SingleMemberInjector.java:78)
        at org.picocontainer.injectors.ConstructorInjector$CtorAndAdapters.getParameterArguments(ConstructorInjector.java:309)
        at org.picocontainer.injectors.ConstructorInjector$1.run(ConstructorInjector.java:335)
        at org.picocontainer.injectors.AbstractInjector$ThreadLocalCyclicDependencyGuard.observe(AbstractInjector.java:270)
        at org.picocontainer.injectors.ConstructorInjector.getComponentInstance(ConstructorInjector.java:364)
        at org.picocontainer.behaviors.AbstractBehavior.getComponentInstance(AbstractBehavior.java:64)
        at org.picocontainer.behaviors.Stored.getComponentInstance(Stored.java:91)
        at org.picocontainer.behaviors.AbstractBehavior.getComponentInstance(AbstractBehavior.java:64)
        at org.picocontainer.behaviors.Locked.getComponentInstance(Locked.java:40)
        at org.picocontainer.DefaultPicoContainer.getLocalInstance(DefaultPicoContainer.java:605)
        at org.picocontainer.DefaultPicoContainer.getComponents(DefaultPicoContainer.java:586)
        at org.picocontainer.DefaultPicoContainer.getComponents(DefaultPicoContainer.java:572)
        at com.atlassian.jira.component.pico.CachingMutablePicoContainer.getComponents(CachingMutablePicoContainer.java:153)
        at com.atlassian.jira.component.pico.ComponentContainer.instantiateComponents(ComponentContainer.java:483)
        at com.atlassian.jira.component.pico.ComponentManager.earlyStartPluginSystem(ComponentManager.java:249)
        at com.atlassian.jira.upgrade.PluginSystemLauncher.start(PluginSystemLauncher.java:45)
        at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$postDbLaunch$2(DefaultJiraLauncher.java:145)
        at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrEnqueue(DatabaseConfigurationManagerImpl.java:301)
        at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrWhenDatabaseActivated(DatabaseConfigurationManagerImpl.java:196)
        at com.atlassian.jira.startup.DefaultJiraLauncher.postDbLaunch(DefaultJiraLauncher.java:137)
        at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$start$0(DefaultJiraLauncher.java:104)
        at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:31)
        at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:102)
        at com.atlassian.jira.startup.LauncherContextListener.initSlowStuff(LauncherContextListener.java:154)
        at java.lang.Thread.run(Thread.java:748)
2021-02-25 16:34:06,632+0000 JIRA-Bootstrap ERROR      [c.a.jira.startup.DefaultJiraLauncher] JIRA has failed to start because of the following errors: [(Event: Level = (EventLevel: fatal) , Key = (EventType: startup-unexpected) , Desc = We couldn't start JIRA , Exception = An error occurred while trying to start JIRA. We can't give you any more detail right now, we suggest checking the logs for more detail and contacting our support team.<br/>See our documentation for more information on contacting our support team and creating a support zip.), (Event: Level = (EventLevel: fatal) , Key = (EventType: database) , Desc = Could not execute health check, DatabaseConfigurationManager not available. , Exception = ]

{code}

Is this maybe related to a specific plugin as it's not clear from error message?

Thanks
Dariusz

2 answers

0 votes
Harvinder Singh
Contributor
February 10, 2017

I mean the project A export file was having field "projectname" which I changed from project A to project B. Now, I imported that file to project B. I guess since the import was carried out  with csv having Sprint field and release field as well. So, it created similar fields for project B also. Further, I guess since the release and sprint were having same sprint id and version id. Therefore, the issues are interlinked in both the projects. Thus, in case I delete a sprint X for Project B which got imported from project A. The sprint X of Project A also gets deleted.

I hope you understand my problem now.

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
February 10, 2017

I don't understand what you've done, why, or what you're trying to achieve by doing it.

Some things jumped out as clear though:

  • Changing the project name in an export file is likely to break things unless you change the associated things.
  • "issues are interlinked" explains nothing about what you mean - links?  Same issues?  What?
  • Yes, if you delete a sprint, you delete it.  Sprints do NOT belong to projects, they belong to boards

 

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
February 10, 2017

This does not sound like the way JIRA behaves at all.

Could you clarify something - when you say "project", do you actually mean "board"?

Harvinder Singh
Contributor
February 13, 2017

By Project I mean "Project" named "A" and "B" and the issues can be seen in both the project boards and on clicking left nav backlog  also. In that view issues are coming based on the Sprints listed in Project A.

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
February 21, 2017

Your boards are set to include issues from both projects.  You need to change those.

Suggest an answer

Log in or Sign up to answer