Switching back from Compass components broke regular component validity

[Inspire Digital]

Ever since turning on and then turning off Compass Components I get a Create Issue pop-up modal (whereas I never used to and don't want to) when creating from the +Create Issue action at the bottom of the backlog.

What seems to be happening is that its no longer identifying the Jira Component that gets automatically added based on which board i'm on correctly. Even though when the modal pops up with the error, it still has the same Component added already, it just seems to be identifying it as an invalid value. I've also checked and the Component field isn't set as mandatory, so its definitely not expecting a value regardless of what's entered. 

I've found a similar issue someone else has experienced here: 

Getting an error message for valid value for Compo... (atlassian.com)

BUT this one seems to end up with the solution being to remove a component with the same name from another project. I can't do that as i'm syncing the components between JSM and Jira by having components with the same name.

Please help. 

[Jack Brickey]

Hi @Inspire Digital , I would definitely suggest reaching out to Atlassian support  on this issue. On the surface it seems to be a bug.