This page is a collection of feature wishes and requirements that //SEIBERT/MEDIA has for Atlassian to improve the Atlassian Cloud.
//SEIBERT/MEDIA has invested significant efforts in the past years to establish a strong offering in the Atlassian Marketplace. Our investments in draw.io for Confluence Cloud and draw.io for Jira Cloud were early on and pretty "painful". We are setting out to implement our Linchpin intranet for Server in Cloud over the next several months (and years). We've already released a microblogging app that we call Linchpin Communities, and we've started with Linchpin Cloud that will shortly be available at the Atlassian Marketplace . From the pain we have experienced in implementing these apps for Confluence Cloud we've come up with the following requests for Atlassian.
Feature wishes & use cases (in the box)
The following requests come from our current experiences in implementing an app in Atlassian Cloud. This is derived from the current platform:
We need more flexibility regarding the possibility to override "routes" using the theming api. (https://developer.atlassian.com/cloud/confluence/create-a-confluence-theme/#override-the-space-home-page-optional) as just the "spaceview" is not enough. We'll need possibilities to override the dashboard and the global header (like header.vm in Confluence/Jira Server)
We need the possiblity to enhance the attributes a user has or should at least be able to extend the profile view under wiki/people/557058:??? in case we have to store additional information on our own. Alternatively we have to be able to override the user directory of jira/confluence.
As Linchpin Intranet Suite is a "confluence-based" Intranet, for an own cloud-based implementation we would need something like an offical supported "Login with Atlassian" feature (comparable to Facebook, Twitter, ... auth providers). There may be hacky ways to achieve this (like the JWT-token-based Login Refined used), but we don't want to base our user management on an undocumented behaviour.
Furthermore it is currently unclear to us how to secure an own REST endpoint in a manner that only Atlassian.net instance (sys)administrators can use it as the roles are not a part of the JWT token provided to the iframe. Currently we can just verifying if a user was allowed to see an (condition-restricted) admin page. (related: https://community.atlassian.com/t5/Answers-Developer-Questions/How-to-check-whether-a-user-is-an-administrator-in-Connect/qaq-p/521263).
We are not able to render Linchpin Cloud macros within the Confluence Cloud mobile app
We want to inform users about new content within Linchpin Cloud. So it would be great if we can show notifications inside the Confluence Cloud notification box when new content is available for the user.
App menu entries are currently clustered within a single “App” menu item. It would be great, if menu items are not clustered (or we can define if items should be clustered or not).
Thinking outside the box (headless apps / microservices)
//SEIBERT/MEDIA is a company with 150 employees. We have 35 full time developers working on Linchpin today. We'd welcome a higher degree of freedom and extensibility of the Atlassian Cloud that is currently not available in such a limiting development environment that Atlassian offers today for Atlassian Cloud. So we'd be love to see opportunities to use Atlassian Cloud as "headless applications" within our own environment or even as "microservices". This would be an inverted model, where Atlassian would only offer core features like a "rich text editor" (from Confluence) or "issue management" (from Jira) and we'd implement this in our own apps both in the web and on mobile use cases.
This area needs more work and thought from our side. We plan to offer an MVP approach and will include other wishes. Feel free to subscribe to this page to stay in the loop as changes occur.
Short link to this page: https://seibert.biz/cloudwishlist