Last year we started working on a new add-on for Atlassian JIRA. After months of work we decided to drop everything and start over on a relatively new platform, JIRA Cloud. This was a radical decision that definitely kept us up at night. This short story is about this decision.
One of our newly released add-ons, Flag Content for Confluence, was built in a such a way that it integrates with the Likes plugin of Confluence, but it was not dependent on it.
When testing the add-on with theme add-ons like Brikit Theme Press, we found out that our solution messed up their styling.
When we started using JIRA we created workflows that reflected our working processes. These first workflows were simple but a bit constrictive. For example when you started work on an issue (status in Progress), you could not transition it back to Open, only to on-Hold. And generally speaking, that’s what we wanted, but what about when you make a mistake? We all press buttons too quickly once in a while!
The current approach of in-VM plugins incurs a very high cost in development, QA, and support time. This is due to tight coupling and increased security and stability risks.
The Atlassian Remote Apps project aims to bring the benefit of third-party extensibility to OnDemand by dramatically lowering the costs and risks related to third-party code.
We investigated the possibilities to setup a remote app for enabling Numbered Headings for OnDemand. Here are our findings…