RFC-82: Recurring work in Jira

It seems necessary to have a serious discussion with Atlassian about the direction in which it has taken in recent times. It is evident that commenting on these RFCs is of little use, as feedback does not escalate to higher levels.

On one hand, we must keep up with the platform’s continuous breaking changes. On the other hand, Atlassian itself continues to cannibalize the marketplace by adding native functions that increasingly overlap with existing apps. All this while vendor feedback is completely ignored, and bugs and feature requests on ECOHELP continue to stagnate for decades.

These RFCs are limited to individual aspects. However, let’s consider all the RFCs together and the new features Atlassian launched and/or planned. The impact on the marketplace becomes significant, affecting many vendors and posing a considerable business risk. And this will likely worsen with upcoming announcements.

As vendors, we must unite to make our voices heard at a higher level within Atlassian’s hierarchy, requesting an official statement, as already proposed here: Atlassian Statement Request. Unfortunately, we do not have the contacts or the experience to lead this effort, but if someone were willing to draft a shared letter, we would be more than happy to sign it.

5 Likes