Create a Star/Snowflake Schema and DAX measures in Excel
You are not wrong if you call PowerBI an upgraded Excel. The major components of PowerBI are Power Query, Power Pivot and Power View....
top of page
Recent Articles
Unlocking Atlassian Teamwork Collection: A Comprehensive Guide for 2026
74% of leaders say ineffective communication is slowing their teams down. Not lack of talent. Not lack of tools. Communication breakdowns. The irony? Most organizations already have plenty of software. Jira for tracking. Confluence for documentation. Slack for chat. Loom for video. The problem is that these tools don't talk to each other. Information gets trapped in silos. Context gets lost between apps. And people spend more time hunting for answers than actually doing the w
JSM Knowledge Base Setup & Knowledge-Centered Service Loop
Most JSM knowledge base setups fail because teams don't understand three things: They think they need to buy a Confluence license for every customer who reads an article (they don't, if configured correctly). They write articles the way humans scan them (in prose walls), which breaks Atlassian's AI engines trying to parse the content for Rovo-powered deflection. They build the knowledge base as a static library instead of a living system where agents turn solved tickets into
Why your JSM CSAT surveys fire at the wrong time (and how to fix it)
A customer receives a satisfaction survey, but their ticket is not actually resolved. It has simply moved to a status that looks like Done This is not an edge case. It is the default behavior in Jira Service Management (JSM). Here is why it happens, and the setting that can prevent it. The default behavior many teams miss By default, JSM sends a CSAT survey when a ticket moves into the Done status category. It does this even when the Resolution field is empty. That distinctio
Atlassian
Unlocking Atlassian Teamwork Collection: A Comprehensive Guide for 2026
74% of leaders say ineffective communication is slowing their teams down. Not lack of talent. Not lack of tools. Communication breakdowns. The irony? Most organizations already have plenty of software. Jira for tracking. Confluence for documentation. Slack for chat. Loom for video. The problem is that these tools don't talk to each other. Information gets trapped in silos. Context gets lost between apps. And people spend more time hunting for answers than actually doing the w
JSM Knowledge Base Setup & Knowledge-Centered Service Loop
Most JSM knowledge base setups fail because teams don't understand three things: They think they need to buy a Confluence license for every customer who reads an article (they don't, if configured correctly). They write articles the way humans scan them (in prose walls), which breaks Atlassian's AI engines trying to parse the content for Rovo-powered deflection. They build the knowledge base as a static library instead of a living system where agents turn solved tickets into
Why your JSM CSAT surveys fire at the wrong time (and how to fix it)
A customer receives a satisfaction survey, but their ticket is not actually resolved. It has simply moved to a status that looks like Done This is not an edge case. It is the default behavior in Jira Service Management (JSM). Here is why it happens, and the setting that can prevent it. The default behavior many teams miss By default, JSM sends a CSAT survey when a ticket moves into the Done status category. It does this even when the Resolution field is empty. That distinctio
The Jira fix version mistake that duplicates your release notes
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
5 Atlassian updates from 2026 that actually matter for IT service teams
Most "what's new at Atlassian" roundups this year lead with AI, Summarize buttons, drafting assistants, chat search. Useful, and we've covered that ground already. This is the other list: five releases from Jira and Confluence's 2026 Spring and Summer cycles that change how a service desk or IT ops team actually works day to day, verified against Atlassian's own release notes, not marketing copy. 1. Formula fields in Jira Part of Jira's Summer 2026 release, formula fields let
We Brought Atlassian to Lagos. Twice.
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
Finance
bottom of page