Hosting, not selling. onpoint with our Atlassian colleagues and guests in Lagos — the people who build the product, in the same room as the people who have to run it. There is a version of being a technology partner that involves reselling licences and answering support tickets. It is a perfectly respectable business. It is not the business we are in. Over the past two years, onpoint has hosted members of the Atlassian team here in Lagos — Lesley Masibi and Stanley — not for
Release notes that tell the truth A fix can travel through more than one release without being new more than once. That small distinction is where a lot of release-note confusion begins. The short version: use Fix Version for releases where the change is actually new. Track later carry-forward releases separately, then explain them in a human-written note. The scenario Imagine a bug is fixed on Tuesday. It needs to ship today in hotfix 4.2.1, and the same branch change will a
If your finance team spends hours manually exporting data from Microsoft Dynamics 365 Business Central or NAV just to build reports in Excel, you're working harder than necessary. Jet Reports bridges this gap by letting you pull live ERP data directly into Excel. But here's the catch: without proper training, most teams barely scratch the surface of what this tool can do. That's where Jet Reports training comes in. Whether you're a finance manager building monthly board repor
Hosting, not selling. onpoint with our Atlassian colleagues and guests in Lagos — the people who build the product, in the same room as the people who have to run it. There is a version of being a technology partner that involves reselling licences and answering support tickets. It is a perfectly respectable business. It is not the business we are in. Over the past two years, onpoint has hosted members of the Atlassian team here in Lagos — Lesley Masibi and Stanley — not for
Release notes that tell the truth A fix can travel through more than one release without being new more than once. That small distinction is where a lot of release-note confusion begins. The short version: use Fix Version for releases where the change is actually new. Track later carry-forward releases separately, then explain them in a human-written note. The scenario Imagine a bug is fixed on Tuesday. It needs to ship today in hotfix 4.2.1, and the same branch change will a
Atlassian’s Team ’26, held on May 6, 2026 in Anaheim, was not the usual product demo. Atlassian pushed Rovo from assistant to agentic executor and opened the Teamwork Graph as the company’s context engine, Rovo and Teamwork Graph are now the centerpieces of an AI‑native pitch that Atlassian says already spans 150 billion connections and is in open beta for developer tooling. Atlassian’s play: agents plus context Atlassian’s CEO Mike Cannon‑Brookes framed Team ’26 as the momen
Three years after ChatGPT entered the mainstream, AI has moved from experimental curiosity to workplace essential. However, it is becoming clearer that the organisations seeing real returns aren't the ones with the biggest AI budgets. They're the ones that figured out how to make humans and AI work together. According to the latest Harvard Business Review survey of 100+ C-level executives, 99% now prioritize AI investments. Yet 93% of those same leaders cite human and cultura
You have until January 1, 2027. That's the deadline in CBN circular PSS/DIR/PUB/CIR/001/004, issued June 15, 2026 and signed by Rakiya O. Yusuf, Director of the Payments System Supervision Department. Every bank, fintech, mobile money operator, and payment service provider in Nigeria now has to store and manage payment transaction data domestically. Do the math. That's 6 and a half months. There's a second clock running too. A market-structure rule capping share at 25% in car
Every default Jira bug workflow looks fine in the demo. Open, In Progress, Done. Three statuses, clean board, everyone nods. Then week 6 hits. You've got 80 open bugs, half of them stuck in "In Progress" for reasons no one can explain, three duplicates of the same login crash, and a customer-reported bug from your service desk that somehow never made it to the dev team's board at all. This is the setup that does. Statuses, fields, the severity/priority split almost everyone g