Atlassian Developers
Apps, interfaces and automation for Jira and Confluence, built by the team behind the Cross Connectors.
An extension that breaks at the next upgrade is not a saving.
The challenge: the Marketplace stops before your case
The Marketplace covers the common case. What is left over are the places where your organisation works differently from the average.
So the awkward question comes before the building: does anything need building at all? Often an existing app handles ninety per cent of the case, and the remaining ten per cent is a habit that can change. When the gap is a system with no app at all, the Marketplace has nothing more to offer.
A system with no app for it
A process spanning three tools
An app that does 80 per cent
Manual work that returns every week
What we build
We develop the extension ourselves or integrate existing third-party functions. Our Cross Connectors link SAP Solution Manager with Jira Cloud and Jira Data Center; the same team builds your adaptation.
On Jira Cloud that means a Forge app, on Data Center a Java plugin. We know both routes from our own product, including the differences that only surface in operation. Your platform therefore decides how we build, not whether we can.
Apps
Extensions for Jira and Confluence, where the Marketplace leaves a gap, for Cloud and for Data Center.
Interfaces
Connections to the systems that stay: SAP, ServiceNow and whatever else is in the house, over the vendor's supported routes.
Automation
Take repeated steps off people's hands without anyone learning a new interface.
How it works: what goes into an extension
An example from our own shop. Between Jira and SAP transport management we put a panel on the issue, from which a transport gets created, released, imported, coupled or decoupled. Beside it sits a project-level view where the same actions run across many issues at once, filtered by JQL.
On top of that come workflow guards: an issue only moves on once all its transports are released, for instance. Rules like that are the difference between a display and a control. How CC5 came about is described in SAP Cross-Connector Jira / TMS is now on Atlassian Marketplace.
- Panels on the issue for the actions that belong there
- Project-level views for acting across many issues at once, filtered by JQL
- Workflow guards that tie a transition to conditions
- Connections to SAP over the provided services rather than table access
- Automations for the steps that repeat every week
- Readable dependencies for the next Atlassian upgrade
- Testing and acceptance against a catalogue rather than by word of mouth
- Handover to named people who maintain the extension afterwards
Where an interface attaches
Between Jira and SAP Solution Manager, the issue and the change document travel in both directions. Your extension attaches at the same point: the vendor's supported interface.
That sounds obvious and is not. Reach into the database instead, or drive a user interface from a script, and you get something that works today and belongs to nobody two upgrades later.
From issue to change document
The state syncs both ways without anyone retyping it.
Cross ALM as a development partner
Cross ALM is an IT and process consultancy based in Berlin, grown out of a team of former SAP employees and SAP specialists. We are an Atlassian Gold Solution Partner and were named Atlassian Partner of the Year Rising Star EMEA in 2023: Cross ALM Receives Atlassian Partner of the Year 2022 Award.
We run our own apps on the Marketplace over years and across platform changes. The care that demands goes into every extension we build for you.
Our own apps
Four product lines on the Atlassian Marketplace and in the ServiceNow Store, maintained over years and across Cloud and Data Center changes.
Both platforms
Forge for Jira Cloud, a Java plugin for Data Center. We know the differences from running them, not from the documentation.
Into the SAP world
Registered SAP Application Development Partner. The link to SAP transport management is our own product.
Starting in three steps
The first two steps cost little and establish whether the third is needed at all.
Record the case
What should the system do, which side leads, and does an existing app perhaps cover it already.
Design and boundaries
The supported interface, the data it touches and the dependencies, written down, before anyone builds.
Build and hand over
Development, testing, training and handover to named people in your organisation.
From customer projects
What we have built outside the Marketplace is written up in our project reports: Flexible Cross Connector Jira/SolMan interface solution with LAPP covers a link that did not exist as a product, Jira-Solman Integration with BSR a municipal operator, and SAP Transport Management System – Jira Integration at HUK-Coburg transports driven from inside Jira.
Customers who trust us
Before we build
- What should the system do that it cannot do today
- Which data flows where, and which side is the source of truth
- What happens at the next upgrade
- If a Cross Connector already covers it, we build nothing new