Hey Compass team!
Nice to meet you here on the Atlassian Developer Community.
I guess you’ve never actually released a real feature unless it has broken multiple Atlassian apps In this case, I’m talking specifically about the new components implementation of Jira Software projects, announced here: Compass Components in Jira Software are coming! - Atlassian Community
Probably the Jira team should have told you more about the Ecosystem, but given their complete lack of providing any context with regard to this change in the changelog, I guess we can’t really blame you. You’re in good company with regard to breaking apps.
For those not initiated yet into this new feature: newly created company managed Jira projects will now have “Compass Components” instead of the classic native Jira components. I expect this is also going to be enabled by default for previously created company managed Jira projects that have not yet used Components. But I haven’t played with it enough to know all the use cases of how this change will break apps.
Oh right, I should tell you why this actually breaks apps. This is because the Jira REST API will no longer accept any mutations to project components if the Jira project is using “Compass components”. Given that this is the default, this means that the native Jira project component REST API endpoints will not work by default. A customer will need to actively switch back to native Jira components first.
Obviously, I get you want to upsell your brand new product. But perhaps it would be good to consider how these type of changes might impact Marketplace Partners. I mean, it’s not like there isn’t a long-running jira issue open about working with Components.
Anyway, as always it’s a great pleasure to spent the festive season scrambling to fix completely avoidable issues that could have been prevented with proper communications!