Oneteem At ONETEEM, we drive the shift to the Connected Enterprise - fast, focused, and future-ready.

🚀 We’re on a mission to move every business workflow to the Atlassian Cloud, powered by custom private Forge apps. At ONETEEM, we design and build 🔒 secure, 🤖 intelligent, and ✅ compliant Forge solutions that extend the power of Atlassian for enterprise customers.

⚙️ As a Forge development powerhouse, we specialize in creating custom Atlassian Cloud apps that automate business workflows, strength

en data security, and deliver measurable business impact. We help organizations build a Connected Enterprise where strategy, teams, and tools work seamlessly together in the Atlassian Cloud.

👥 Our certified Atlassian experts combine Forge development, AI, and workflow automation to tailor solutions around your people, processes, and goals. We empower
🔹 Leadership Teams to drive alignment and visibility
🔹 Product Teams to deliver what matters with integrated, automated workflows
🔹 Delivery Teams to accelerate software delivery through modern cloud practices
🔹 Service Teams to optimize IT and enterprise service management with Forge

💡 With deep expertise in Forge-based Atlassian app development, a strong focus on AI, data privacy, and cloud security, and a passion for transforming business workflows rather than just implementing tools, ONETEEM turns your Atlassian stack into an intelligent operating system for teamwork that delivers measurable, end-to-end business results.

If you run a Forge app across a large install base, this quiet change matters more than it sounds.Atlassian removed the ...
31/08/2026

If you run a Forge app across a large install base, this quiet change matters more than it sounds.

Atlassian removed the site limit on the Export app logs API on 26 August 2026. It used to return logs for a maximum of 3,500 sites. That cap is gone.

1️⃣ You can now export logs across every site where your app is installed and log sharing is enabled, no more blind spots past 3,500.
2️⃣ Nothing to do. If the old threshold was cutting you off, you now get logs for all eligible sites automatically.
3️⃣ The API still returns logs in the OTLP log data model, so your existing Splunk, Datadog, Dynatrace or New Relic pipeline just sees more of the picture.

Most apps never came close to 3,500 sites. The signal is the direction. Atlassian keeps taking scaling limits out of Forge observability, one at a time, so the platform holds up for the apps that do get there.

Which scaling limit would you want to see come off next?

Your Rovo agent can now go to the Marketplace.The Rovo Agent Connector moved from EAP to Preview. Apps using this module...
26/08/2026

Your Rovo agent can now go to the Marketplace.

The Rovo Agent Connector moved from EAP to Preview. Apps using this module can now deploy to staging and production, which means Marketplace listing is on the table. One hard requirement comes with it.

1️⃣ A2A v1.0 is now required, v0.3 is no longer supported and apps still on v0.3 are rejected at deployment
2️⃣ Add version "1.0" to protocols.agent2Agent in your manifest, then update your JSON-RPC implementation to the A2A v1.0 protocol
3️⃣ Update to Forge CLI v13.3+ with npm install -g /cli@latest

One thing to know: adding rovo:agentConnector makes the system user non-mentionable, the agent connector user takes its place, and the CLI warns and prompts for approval at deploy time.

Is your agent app ready for v1.0?

Before we help other teams work in perfect flow, we have to live it ourselves 🧡That was the spirit of our OKO: coming to...
31/07/2026

Before we help other teams work in perfect flow, we have to live it ourselves 🧡

That was the spirit of our OKO: coming together to prepare for the milestones ahead.

Three days. Two countries. ONETEEM.

We took time to strengthen the principles that shape how we work every day:

👥 TEAM: the people behind the work
🧭 ALIGNMENT: clarity before speed
🤝 TEEMWORK: sharing knowledge and building together
🔐 TRUST: the foundation for honest collaboration
⚒️ FORGE CLUB: play, learn and connect
🌿 RESET: stepping back to return with fresh energy
🚀 FORWARD. TOGETHER: one direction, one flow

Across Germany and Tunisia, these are more than words. They are how we connect across roles and locations, deliver thoughtful work and create real value for our customers.

A special thank you to WildyNess for organizing the event and creating the space for us to connect, reflect and move forward together. 🙏

Because when everyone moves together, progress becomes unstoppable.

ONETEEM. ONE FLOW 💜

No more provider accounts. No more secret rotation. No more proxy backend whose only job was to call another backend.For...
31/07/2026

No more provider accounts. No more secret rotation. No more proxy backend whose only job was to call another backend.

Forge LLMs are now generally available. It is the first Atlassian LLM API where you do not bring your own model key. You declare the LLM module in your Forge manifest and call Atlassian-hosted models straight from a Forge function.

What changes for builders:

1️⃣ Secure, Atlassian-hosted AI built directly into your app, with the latest Claude models, Haiku, Sonnet, and Opus
2️⃣ Less to own and maintain, the key store, the rotation schedule, and the extra backend all go away
3️⃣ An updated deprecation policy built for how fast AI moves now, so you plan model changes with clear notice

One honest note: less infrastructure does not mean less responsibility. You still authenticate as a Forge app, still choose your model, and still own the safety of what you ship.

If you build on Atlassian, this is the moment AI stops being a bolt-on and becomes part of the platform.

Now that the key is gone, what is the first AI feature you would add to your app?

Your idle Forge services do not need to keep the meter running.Forge Containers can now scale down to zero. When a servi...
29/07/2026

Your idle Forge services do not need to keep the meter running.

Forge Containers can now scale down to zero. When a service in a non-production environment sits idle, it stops reserving compute, so you pay for capacity only when your service is actually handling traffic.

1️⃣ Set the min scaling property to 0 for a Forge Containers service in your manifest
2️⃣ Works in development and staging, exactly where idle test services quietly cost you
3️⃣ It is one small change in manifest.yml, then redeploy

One honest note: Forge Containers is still Early Access, so this is for non-production today, not production workloads.

If your dev and staging environments scaled to zero when idle, what would you stop paying for first?

Atlassian Marketplace Partners: your customers are about to see your migration stance before you tell them.Atlassian is ...
27/07/2026

Atlassian Marketplace Partners: your customers are about to see your migration stance before you tell them.

Atlassian is now rolling out Connect end-of-support messaging directly to admins on the Connected Apps page. Which message they see depends on one thing: what your app has declared.

1️⃣ Declared your migration intent as NO or UNDECIDED, never adopted the connectToForgeMigration module, or still running as a Connect app with no Forge manifest? Admins start seeing messaging now
2️⃣ Declared YES? You get until an estimated mid-August, with at least two weeks notice before it starts
3️⃣ Provided a migration URL? Your own guidance replaces the default Atlassian notice, so the customer hears it in your words

The takeaway for every Marketplace vendor: doing nothing is now a visible choice. Silence shows up on your customers' screens as uncertainty.

The fix is not complicated. Adopt the module, declare your intent, add your migration URL, and control the story admins read.

If you build a Connect app, where are you in this migration right now?

Atlassian has opened an Early Access Program for Point-to-Point Logs Export, so your Forge app logs can flow straight in...
25/07/2026

Atlassian has opened an Early Access Program for Point-to-Point Logs Export, so your Forge app logs can flow straight into the logging tool your team already lives in.

1️⃣ Logs pushed directly to your own tool, no scraping, no glue code
2️⃣ Works across all environments, including production
3️⃣ Supported today in the EAP: Datadog, Sumo Logic, Splunk, and Amazon CloudWatch in the US region

This is Early Access, which means the sign-up is open now and early testers shape what ships.

If your Forge logs landed in your main dashboard tomorrow, what would you watch first?

Every environment has its own security story. Now your Marketplace listing can tell each one separately.Marketplace part...
24/07/2026

Every environment has its own security story. Now your Marketplace listing can tell each one separately.

Marketplace partners can provide environment-specific Privacy and Security information for Atlassian Government Cloud and Isolated Cloud app versions.

1️⃣ A dedicated Privacy and Security tab per environment, covering data handling, permissions, hosting and compliance
2️⃣ Copy from Cloud pre-populates the fields from your existing listing, so you adjust only what differs
3️⃣ Complete it in the Marketplace vendor console, review, fill the required fields, submit

For regulated buyers, the listing is the first trust signal. This lets it speak their language.

Partners, does your Government Cloud listing tell its own story yet?

Everyone can buy the same AI now. So what's actually left to compete on 🤔 ?Not the model. It's your context: what your t...
30/06/2026

Everyone can buy the same AI now. So what's actually left to compete on 🤔 ?

Not the model. It's your context: what your tools already know about your projects, your decisions, your history. Anyone can copy the smarts. Nobody can copy your context.

We put together a short video on where that context lives (Atlassian's Teamwork Graph), what's changing now that it's opening up to outside AI agents, and why your messy old tickets might be your most underrated asset.

A few minutes, no jargon. Worth a watch if you live in the Atlassian world 👇.

https://www.oneteem.com/r/104

🚨 Heads up, Jira & Rovo Dev admins: June 15 is around the corner. 👇Atlassian is turning "Rovo Dev in Jira" into the Jira...
11/06/2026

🚨 Heads up, Jira & Rovo Dev admins: June 15 is around the corner. 👇

Atlassian is turning "Rovo Dev in Jira" into the Jira Coding Agent, bundled with every paid Jira edition. Assign a work item, get a merge-ready PR from a cloud sandbox, grounded in the Teamwork Graph. No extra license. 🤖

But here's what most teams will miss: there are now two wallets. 💳
1️⃣ Jira Coding Agent runs on the Rovo credits already in your Jira plan
2️⃣ CLI, IDE, and AI code review stay behind Rovo Dev Standard with separate Rovo Dev credits
3️⃣ Rovo Dev Free (350 credits) ends after June 15, save your prompts and automation rules now

Our take at ONETEEM: bundling an autonomous coding agent into Jira at zero procurement friction is a big move. When ticket-to-PR becomes cheap, code review and credit governance become the real bottleneck. That is where the work shifts. 🎯

Check your subscriptions before June 15. And if you want help setting up the agent, governing credits, or wiring it into your workflows, you know where to find us. 🚀

Adresse

Watzmannstraße 5
Altötting
8450308:00

Öffnungszeiten

Montag 08:00 - 18:00
Dienstag 08:00 - 18:00
Mittwoch 08:00 - 18:00
Donnerstag 08:00 - 18:00
Freitag 08:00 - 18:00

Benachrichtigungen

Lassen Sie sich von uns eine E-Mail senden und seien Sie der erste der Neuigkeiten und Aktionen von Oneteem erfährt. Ihre E-Mail-Adresse wird nicht für andere Zwecke verwendet und Sie können sich jederzeit abmelden.

Verknüpfungen

Teilen

Kategorie