PostHog

Atlassian + Anthropic? Lots of chatter in the usual SF coffee shops that Anthropic is in advanced talks to buy Atlassian. Hearing institutionals and Mike and Scott want $150 a share, all cash. Guess that explains why they closed Austin office and moved everything to SF. Interested to hear what everyone thinks about this. Upside: Tight integration, Confluence/JIRA getting the latest models probably for free. Downside: Probably some redundancies. submitted by /u/TurbulentTiger2567 [link] [comments]

New data contribution settings What are your opinions on this? ( https://www.atlassian.com/trust/ai/data-contribution ) I don't want anybody to learn from my data or to train LLMs with it. Neither do I like the fact that you can't switch off the use of metadata when you're on a standard plan (hey, for enterprise users no problem, you might need it for compliance reasons). Really don't like what I see here. submitted by /u/derkasek [link] [comments]

Guests in the times of... 250K user Confluence sites Adding outside collaborators as guests is a no-brainer as g uests are essentially free users. Free as in ‘you don’t have to pay for their seats'. Sure, there are limitations but you can add up to five guests per one paid seat. Admins are less thrilled and with the advent of 250K user sites , so they are naturally biased toward saying no to protect the org and their sanity. https://preview.redd.it/gakc4ui63jvg1.png?width=2200&format=png&auto=webp&s=9c8a2b09bf8c284529160ea9251cb6fdba5f3730 I only had to deal with guests on a small site (50 seat license) but it felt like I'm manning revolving doors at times. As I was the project lead AND an admin, it wasn't that bad. Anyway, here's something I observed and practiced and it may scale up if you enforce it. I hope this will be useful for both admins and project leads. The Math A small team of 10 people who are about to change the world may add 50 guests. That’s an incredible money-saving measure! And that you can manage with ease. Let’s move things up a notch . Now you have a site with 1000 users. That means 5000 potential guests. Managing 1000 carefully provisioned users is one thing. Managing even 1000 guests is what admins' nightmares are made of . And before you ask if it scales… yes, it does, unlike an admin’s stress tolerance, all the way up to the 250K-user limit per a Confluence site. And that might happen on Standard where you don't have all the perks. Define the Guest's Role The guest role was designed to enable ad hoc collaboration of teams with outsiders. Not to get a free ride. Although… Anyway, before you invite a guest user, the following best practices will help you develop a manageable workflow. Define the project guests will participate in. Determine the Confluence space the guest will access. Guests can only access a single space at a time. Do not hesitate to create an ad hoc space just for this specific collaboration. Determine the guest’s permissions within that space. Don’t forget to check the market...

JSM and Jira cloning For the past few days I am trying to do one automation, and the answer somehow always includes branching and parentkey/etc. But it shouldn't need this, or? It's a clone from JSM new item at a particular time, make new items, 5x of them. Clone them to Jira and link them. (Example is quarterly export of systems) I thought a simple sequence of create, clone and linking is suffice. I can also do all Create instead of cloning. How do you deal with certain generic errors in this part of Jira? Do you find Rovo helpful? submitted by /u/Terrible_Ad3822 [link] [comments]

PostHog showed me where my “simple” UX was actually causing friction One thing PostHog helped me realize while building Kestor.app : a flow can look simple and still create a frustrating experience. I found this in my invoice creation flow... Thankfully, PostHog helped me catch a usability issue that regular analytics probably would’ve missed. The problem showed up in the invoice creation flow. I designed it to feel simple and lightweight by breaking things into small, focused steps. On the surface, it looked clean. But once I started watching real sessions in PostHog, I noticed the same pattern over and over: people would move through the flow pretty confidently, then suddenly get blocked because they were missing required setup in settings, usually business details or tax configuration. So the flow wasn’t actually simple. It just delayed the friction. Instead of finding out upfront what was missing, users only discovered it later, had to leave invoice creation, go into settings, fix things there, and then come back. Nothing was broken, but the experience was clearly more frustrating than I expected. Watching session recordings made that obvious almost immediately. The fix wasn’t adding more complexity. I just made the missing requirements much clearer throughout the flow, so users could understand earlier what still needed to be set up. I also created a smoother first-time setup path, so they could complete those missing steps without losing the invoice they were already working on. That change made the whole experience feel much better. What I liked about PostHog was that it helped in two different ways: analytics showed me where people were slowing down or dropping off, and session recordings showed me why. Without the recordings, I probably would’ve only known that something felt off. With them, I could actually see the hesitation and fix the real issue. Good reminder that making a flow feel minimal doesn’t always make it better. Sometimes it just hides the dependencies and pushes the friction further down the line. submitted by...

How are you keeping Jira automation from turning into admin debt? I keep seeing the same pattern in bigger Jira setups: nobody is too worried when the first few automation rules get added, but after enough years/projects/owners, the environment gets hard to trust. The mess usually looks like: - duplicate or overlapping rules - unclear ownership - noisy audit history - not knowing what is safe to remove If you have admin responsibility in Jira, I would really value a reality check: - how do you review old rules today? - what part wastes the most time? - do native tools feel sufficient here, or is cleanup still mostly manual? I’m specifically trying to understand the automation governance / cleanup side once the rule count gets big.I keep seeing the same pattern in bigger Jira setups: nobody is too worried when the first few automation rules get added, but after enough years, projects, and owners, the environment gets hard to trust. submitted by /u/Diligent-Resolve8023 [link] [comments]

AWS App Runner -> Render AWS App Runner is ending new feature development. Render is the natural new home for your App Runner services. Same flow, no extra setup: Link your repo Set build & start commands Deploy (Docker images welcome too 🐳) https://render.com/docs/your-first-deploy submitted by /u/shifra-dev [link] [comments]

Opensource Browser extension for AI Code Reviews for Bitbucker PRs - powered by Ollama Hi Everyone , I want to share some exciting news , I have added support for Bitbucket cloud and Bitbucket data center to ThinkReiew browser extension The extension works on your bitbucker PRs , generates Code Review - allows you to chat with your PR Give you code suggestions as well as you can add custom review agents that run on specific conditions on your PRs The extension is fully open source , It has local ollama support as well as all frontier LLMs https://github.com/Thinkode/thinkreview-browser-extension Its available on both chrome and firefox https://thinkreview.dev/ submitted by /u/Brilliant-Vehicle994 [link] [comments]

You're doing lifecycle emails wrong Messaging tools like Customer.io and ActiveCampaign were built for a specific job: broadcast email with some segmentation on top. You upload a list, you define some basic audience filters, and set up a drip sequence. That model worked well for a long time – and it's still fine for newsletters, product announcements, and campaigns where you're addressing a stable audience with a consistent message. PLG lifecycle messaging is a different job entirely. It needs to reason about sequences of behavior. Has this user completed onboarding and then gone quiet? Have they invited a teammate before hitting the feature wall? Did they upgrade, or did they hit the paywall three times and leave? This logic requires asking arbitrarily complex questions about what a user has and hasn't done, in sequence, in real time. Messaging tools weren't designed to answer these questions – they were designed to send emails to lists. So teams end up with trigger logic that's dumber than their product data. Not because they're doing lifecycle marketing wrong, but because they're using a broadcast tool to do behavioral work. How this plays out in practice Most teams build their messaging stack early, when event tracking is still basic. Signup event, maybe a key action or two. So the sequences were time-based, because that was all you could reliably trigger on. Day 1 welcome. Day 3 nudge. Day 7 check-in. It shipped, it ran, and it was good enough. Then the product got more instrumented. Feature usage, activation milestones, plan changes – all of it flowing into the analytics tool. But the sequences kept running on the old architecture, because the open rates looked acceptable and there was always something more urgent. The result is a hybrid nobody designed: time-based triggers standing in for behavioral logic, audience definitions evaluated at sync time rather than the moment of truth, and a messaging tool working from a portrait of each user rather than a live feed. Here's what that actually looks...

Posthog mobile client made a small posthog mobile client for ios shows recent events, quick metrics, and current logs so you can check what’s happening without opening the full dashboard no login, just api key stored on device only https://apps.apple.com/us/app/posthog-client-app-phog/id6761744097 submitted by /u/rajsleeps [link] [comments]

[ Removed by Reddit ] [ Removed by Reddit on account of violating the content policy . ] submitted by /u/Federal-Register-870 [link] [comments]

is atlassian dead? Fallen angel or sleeping giant? submitted by /u/app385 [link] [comments]

First time using Render submitted by /u/hazal-mestci [link] [comments]

Experiences with JSM? Hi everyone! I'm a current MBA student working on a project on Jira Service Management. We are now conducting a diagnostic case study on the friction points of Jira Service Management (JSM). Specifically, we're looking at why JSM often struggles to displace incumbents like ServiceNow in large enterprises or why engineering-heavy teams find it "clunky" compared to other tools. We'd appreciate any perspective. Feel free to share thoughts here or DM to chat! submitted by /u/SemiempiricalArm [link] [comments]

Struggling to understand who’s working on what in Jira, so I built this. submitted by /u/Thereallario [link] [comments]

Rendering a Svelte application (not SvelteKit) on Render submitted by /u/hazal-mestci [link] [comments]

The golden rules of agent-first product engineering Companies building for agents often treat them as a bolt-on feature. This is a mistake. Agents today are more like a new form factor – an interaction layer that sits between your product and your users: That means you need to build for agents as a primary surface, not an afterthought. When done right, this opens up a whole new space of possibilities for your product, like autonomous work and asynchronous flows. Implement it poorly and you’ll lose users’ trust due to slow, buggy experiences and incorrect results. We learned this the hard way and overhauled our AI architecture two times in the last year. Now, our agent and MCP have 6K+ daily active users. Here are the golden rules of agent-first product engineering we learned along the way. 1. Let agents do everything users can If a human can do something in your product, an agent should be able to do it as well. For example, let’s say you ask an agent to set up an A/B test for a new pricing page . The agent would use the PostHog MCP to create the feature flag , create the experiment, link it to the flag it just created, and set up the insight and metrics. Now imagine if the experiment-create tool was missing because we just hadn’t prioritized it yet. The agent creates the flag and insight, but must stop and ask you to go to posthog.com, create the experiment yourself, and paste the experiment ID. This is annoying and defeats the entire point. The benefit of agents is that they reduce the time, attention, and expertise needed to complete a task. If your product doesn’t give agents the same capabilities as users, you’ll always be limited by the human in the loop. Of course, there are situations where requiring human input makes sense, like if you’re dealing with sensitive data. But these should be deliberate exceptions, not accidental gaps. What this looks like in practice In practice, this means nearly everything in your API needs to be accessible to agents. That doesn’t mean converting every endpoint into an MCP tool...

Atlassian down? Me and another employee are getting "Something went wrong on our end". We are in west coast of United States. Anyone else experiencing the issue? submitted by /u/The_Comma_Splicer [link] [comments]

Why JQL can’t really show time between statuses in Jira I used to think JQL could help answer questions like: How long did an issue stay in Review? What’s the actual time between In Progress and Done? Where are issues getting stuck in the workflow? But the deeper I looked, the clearer it became: JQL is great for finding issues, not for calculating real time metrics between statuses . Yes, you can use queries like: status CHANGED FROM "In Progress" TO "Done" DURING ("2026/04/01", "2026/04/08") That helps you find issues where the transition happened. But it still doesn’t tell you: how long the transition actually took, what the average time is between two statuses, where bottlenecks are building up, or which issues are aging in a specific step. That’s the gap a lot of teams run into. What seems to work better is using JQL as a filter , and then adding a tool that actually measures time between statuses as a metric. For example, with Time Metrics Tracker , teams can: calculate time between any statuses, create custom metrics for their own workflow, account for working hours / holidays, spot outliers and aging issues, and visualize everything with gadgets like Scatter Plot and WIP Run Chart. That makes a big difference, because instead of just seeing that a transition happened, you can finally see how long it took and where flow slows down . So for me the takeaway is: JQL is excellent for search. But if you want real cycle time, time in status, or transition analytics, you need something more than native JQL. Curious how others handle this in Jira: Do you rely on JQL + dashboards? Automation + custom fields? Or a marketplace app for time metrics? submitted by /u/KneeStriking3866 [link] [comments]

Untangling Tokio and Rayon in production: From 2s latency spikes to 94ms flat Tokio, Rayon, and a Kubernetes pod walk into a bar. Nobody gets served. Even though Rust is known for its performance and safety, overlooking its inner workings often causes you to shoot yourself in the foot. We know because it happened to us. We discovered a big performance bottleneck in the hot path of our feature flags service. Solving it reduced mean p99 latency by 4x, from 2.5 second spikes to a flat 94 ms line. Here's how we found it and everything we learned along the way. The usual suspect Feature Flags sits in a uniquely latency-sensitive spot compared to most PostHog products. It needs to be as close to real time as possible. A slow flag evaluation means a customer's application is stuck waiting for a response before it can proceed. That’s a tough requirement for a service that also needs to scale well while doing compute-intensive work. Although the Rust rewrite of our feature flag service resulted in a bunch of performance gains, as we grew to serve twice the traffic, problems arose again. Latency, which the rewrite made up to 10.6x faster, was spiking. Our application was "randomly" freezing up. Our initial thought was that it was a database issue. Connection pools were maxing out at 100% multiple times a day, and connection acquire times were spiking in direct correlation with the p99 latency spikes. That's usually a clear signal. But as we dug deeper, the database turned out to be innocent. An airtight alibi We pulled up the Aurora RDS metrics expecting to find the culprit. Instead: query execution times were fast and stable, CPU utilization was healthy, no external pressure. Something else was making it look slow from the application's point of view. We then looked at scaling. The Horizontal Pod Autoscaler (HPA), Kubernetes' mechanism for automatically adding or removing pods based on load, was kicking in during spikes, but always too late. More importantly, having more or fewer pods didn't change the latency at all. This showed it wasn't about capac...

Render Workflows is now in beta: durable background jobs and AI agent logic without the infra headache Hi everyone, I'm Shifra, a Developer Relations Engineer at Render. We just launched Render Workflows via a TypeScript and Python SDK for building reliable, long-running background processes like AI agent loops, data pipelines, and billing flows, without having to wire up your own queues, workers, and retry logic. Here are some of the things you can build with it: AI agent loops Chain LLM calls, sandboxes, and previews into a single durable workflow Let individual steps fail, retry, and recover without losing the whole run Data pipelines Parallelize heavy workloads across hundreds of concurrent containers Pay only for what you use, down to the second — scales to zero when idle Background jobs Define retry behavior, timeouts, and compute per task, right in your code Trigger tasks from your app, the Render API, or the dashboard Render handles all the execution infrastructure (queuing, worker pools, state management, and observability) so you just write code. Read the blog post to learn more. You can also try it yourself by running: render workflows init or install the agent skill to let Claude Code, Cursor, or Codex build and debug workflows for you: render skills install render-workflows Example apps: Data engineering use case (Trender) https://render.com/templates/trender Deployed on https://trender.onrender.com/ Blog thumbnail generator: https://render.com/templates/blog-thumbnail-generator-with-render-workflows Voice agent: https://render.com/templates/voice-agent-with-render-workflows Webhook: https://render.com/templates/webhook-workflow Data processor: https://render.com/templates/data-processor-workflow SEO audit: https://render.com/templates/seo-audit-with-render-workflows Resources: Docs: https://render.com/docs/workflows GitHub: https://github.com/render-oss/sdk Questions? Drop them below! We're actively extending Workflows during beta with cron triggers, pause/resume, state checkpointing, and more language support are all on the roadmap. Feedback and featur...

A 3d Automotive project i will share it's for free when done 🤩🤩 (Any advice) submitted by /u/Ibrahim-An [link] [comments]

Can't create a workplace! submitted by /u/NISMO1968 [link] [comments]

Atlassian support Has anyone else had a hard time with Atlassian, specifically their Loom support team? I’ve been trying to request support for 3 months to no avail. Each time I start a ticket they reach out, I respond, then nothing happens and the ticket is changed to resolved in the portal. I’ve never encountered a support team this passive and unhelpful. submitted by /u/Krohnowitz [link] [comments]

I built a dedicated Jira desktop client for Mac and Windows: open source, session restore, multi-tab support https://preview.redd.it/nukb6cvdxktg1.png?width=3022&format=png&auto=webp&s=625a57bcf3075d27b72ac8eadf99813412202690 Hey everyone, I recently shipped Jira Desktop — a free, open-source desktop client for Jira built with Electron, available for macOS and Windows. Why I built it: I was tired of Jira living inside a sea of browser tabs. I wanted a dedicated, distraction-free workspace that felt like a real desktop app — not just another pinned tab. Current features: Vertical sidebar with multi-tab Jira browsing in one window Pinned tabs and session restore Keyboard shortcuts for new tab / close / reload Theme toggle and lockable sidebar Restricted navigation to Jira / approved Atlassian-related hosts macOS + Windows builds on GitHub Releases It stores your Jira Cloud URL locally on first launch, and packaged builds work without extra setup. It’s MIT licensed and I’d love blunt feedback from heavy Jira users: What’s missing from your daily workflow? What breaks in SSO / login flows? What would make this better than just using Jira in a browser? Repo: https://github.com/prakharbhardwaj/jira-desktop Releases: https://github.com/prakharbhardwaj/jira-desktop/releases/latest submitted by /u/prakhar-bhardwaj [link] [comments]

Oneshot Engineering Work from Slack w/ Claude submitted by /u/KnightDotTech [link] [comments]

Dear Jira Users, how does the process of requirements engineering work in your organization, and what are your thoughts on it? Our team is building an application for product managers and software teams to streamline requirements engineering/gathering by increasing visibility of progress to clients and pointing out unclear requirements in a PRD/RFP. We also want to enable some sort of rapid prototyping so PMs can see what the client’s requirements would look like in the product and work on them accordingly. We would like to ask everyone here: How does the flow go from a client providing requirements to an approved, finished product for your team? Is this process relatively smooth in your team, and why or why not? All input would be extremely valuable. submitted by /u/SimilarSetting3097 [link] [comments]

MCP really bad, any hints? So after using the Posthog AI for some time, I started using it in Claude Code, as I do with most tools - using skills+API or MCP. With PostHog it's MCP. It was really great - a session knowing my whole app, the functions, the data, the flow, we could setup lots of insights and dashboards. Alas, the PostHog MCP eats A LOT OF TOKENS. I mean I'm on max and I hardly use up my limit, unless I work on two-three projects simulatneously. And this happenes usually one hour before the window closes, so it's not that bad. PostHog MCP eats really a lot, i see this often: "● claude.ai PostHog - cohorts-list (MCP) ⎿ ⚠ Large MCP response (~15.4k tokens), this can fill up context quickly " And it does. Recently i used my limit in like one hour! It's very inefficient even when working on a dashboard with 5-6 insights. Any hints, or ways to work efficiently woth PH from CC? submitted by /u/g00rek [link] [comments]

Loom Automation I love loom as a platform but it is so siloed. 2 things I cant get over: there is not api to grab transcripts or a way to download the videos in bulk, and the team feature is more like a shared folder, so every time you do a video you have to find it in your file and move it to the team. It's killing us because it's our meeting recorder too and for Friday meetings I won't get up with them until Monday or Tuesday to remind them to move it to the group. Then also as were trying to build out our AI internally there is so much information on those meetings and videos and only on person has the ability to download the video or the transcript (the recorder). Does anyone have any thoughts on how to solve for these so I'm not on here just to complain? submitted by /u/Last-Bar-4305 [link] [comments]

Built a 16-bit RPG inside Jira because I kept forgetting to log my time and estimate tickets Hey r/atlassian , I'm a dev and I am notoriously bad at Jira hygiene. I always forget to log my hours, update ticket statuses, or add story points until the last minute. So I got an idea for gamification app to bribe my own brain with dopamine to actually do it. Basically, it puts a little pixel-art troll in your issue panel. When you do your normal Agile chores (transitioning tickets, logging time, estimating, leaving comments), your troll gets XP, levels up, and evolves through a few stages. There's also a shared Village tab for the project. When a sprint closes, the village gets "raided". If the team actually met their sprint goals and didn't leave a ton of aging issues in the backlog, the village defends itself and building upgrades unlock. If not, it takes damage. Since everyone works differently, I drew 15 different troll types you can pick from: Chrono-troll gets bonus XP for worklogs. Estimation Sage gets a boost for accurate story points. Comment Kobold gets a multiplier for helping out on other people's tickets. App is free to use with 2 project limit. Let me know what you think or if you find any bugs! Marketplace User guide submitted by /u/drinkits [link] [comments]

First time at Team '26! Expectations given the AI pivot and recent layoffs? Hey everyone, Just realized Atlassian Team ’26 is only a month away. It’ll be my first time attending, so I’m curious to see what it’s actually like on the ground in Anaheim. There’s been a lot of noise lately around migration challenges and how tough it’s getting to list apps on the Marketplace. At the same time, with the stock taking a hit and the 1,600 layoffs to push more into AI, it feels like Atlassian is gearing up for a pretty aggressive shift this year. For those who’ve attended before, especially as exhibitors or Marketplace partners, what was your actual experience like? Was it worth it from a business or networking perspective? And what should a first-timer focus on to not waste time? Would appreciate any honest insights. submitted by /u/AmbitiousYudi1991 [link] [comments]

A beginner's guide to testing AI agents Software testing used to be relatively straightforward. You wrote business logic, defined expected outputs, and verified them with unit, integration, and UI tests. With the same input, your system behaved the same way every time. AI agents changed this. Instead of fixed logic, we now build systems powered by models that are probabilistic. The same input can produce different outputs. Behavior depends on prompts, context, tool calls, and external data. The "correct" answer is fuzzy. And yet, many teams still try to test AI agents the old way, or worse, not at all. Manual testing and bug reports quietly become the default. The good news is that testing hasn’t become impossible, it’s just changed. Like before, there is a way to systematically test and improve agent behavior. It just requires a different mental model. In this post, we’ll walk through what testing AI agents well looks like by following the life of an agent, from first build to production and beyond. The birth of the agent It all begins with the classic "Hello World", though now it's wrapped inside an SDK for creating agents, and we're not greeting the world, but rather being a helpful assistant. Testing at this stage is manual. You work hard to tweak that system prompt, choose the right model, and change the available tools and their descriptions until the agent successfully completes your happy paths and edge cases. It's just you and the agent locally battling back and forth. Once you're ready, you ship your agent to production and start rolling it out to your users. Reproducing bugs from your agent's first users How you tested the agent locally is a lot different than how people use it in production, and that leads to issues. Fixing an issue starts by replicating it, attempting a fix, checking whether it is solved, and repeating. This works well, but it has a requirement: being able to reproduce the issue. This isn't hard in theory because you just need to feed the same input to the agent, but the real...

The best HIPAA-compliant A/B testing tools A lot of popular A/B testing tools aren't HIPAA-compliant, and if you work in healthcare, the last thing you want is to realize too late that the tool you're using doesn't sign BAAs. Skipping experimentation isn't the answer, though. That's like navigating an ocean by sailing roughly in the right direction – you'll probably arrive somewhere, just not where you intended. The good news is there are solid, privacy-focused options out there. Here are a few HIPAA-compliant A/B testing tools worth considering. What you need for HIPAA compliance You need to comply the Privacy Rule and the Security Rule . Breaching either can result in hefty financial penalties, but for the sake of this guide we're mostly interested in how the Privacy Rule impacts analytics and A/B testing. There are three ways to comply with the Privacy rule when adopting analytics and testing tools: Anonymize all PHI and identifiers: There are two so-called " De-identification Standards " – "Expert Determination," where an expert verifies that data isn't personally identifiable, and "Safe Harbor" where all 18 types of identifier are removed. The former is preferable simply because applying the Safe Harbor approach can render data effectively useless for analytical purposes. Sign a BAA with a third-party tool: You must sign a Business Associate Agreement (BAA) with any third-party platform that handles your protected health information (PHI). This can mean signing multiple agreements, though, such as one with your analytical partner, but also any tools you use for importing and exporting data from your data warehouse . Self-host and keep control of all your data: The less common is to self-host tools for analytics and experimentation on your own infrastructure. This reduces the number of BAAs and general legal wrangling needed to generate user insights. The only downside is you'll need the expertise to manage self-hosted instances, or third-party support to do so, and you are wholly liable for any security...

I used Claude Code to build 10 Atlassian Forge apps — here's what happened I've been wanting to try this for a while — use Claude Code to generate, build and deploy Atlassian Forge apps for Jira and publish them on the Marketplace. The process was interesting. Claude generated 10 app ideas in about 2 minutes, built the skeleton for all of them in about 15 minutes. Deploying the first one took another 15 minutes of back and forth — wrong package versions, TypeScript conversion, multiple deploy errors. But it got there. A few things I noticed: — Claude fixed errors across all 10 apps automatically, not just the one I was working on — The Atlassian MCP server made a huge difference compared to my previous attempts without it — You still need to watch what Claude does — giving it too much freedom can cause problems This is still very much a work in progress. I still need to test the first app, deploy and test the remaining 9, and eventually publish all of them to the Atlassian Marketplace. So there's a lot more to come. I'm documenting the whole journey on YouTube. Part 1 is live if anyone is curious: https://youtu.be/-uciNUw0wxY Happy to answer any questions about the process. submitted by /u/LocalHedgehog6132 [link] [comments]

Semi-Beginner Tutorial for CSM ? Hello there, we just trial Atlassian for the CSM Module. We want to provide IT Services and Helpdesk for your external Customers. With the Help of Copilot (Yes Copilot for M365 ^^) i created the Organization and started to learn about Groups and correct licensing. I feel this was already the heavy part ^^ now i need to learn about the CSM and the Customer Experience. So we need to provide 2 Support "pipelines" for our normal customers. One Support for our own SaaS product. And one Support for classic IT Helpdesk for external customers. We are a IT Service Company too. I´m still confused how i can provide a easy Dashboard to my technicians, where the different tickets from the different "Pipelines" shows up. Now i want to start with some good Tutorial Videos or course, which Focus on ITSM and how to establish multiple Help Centers. We want to provide our Enterprise Customers a own Portal with their dedicated Knowledge Base, Chat-Agent and Ticket formular. I really hope someone can lead me to a good up2date Course or video with the newest informations about the CSM. Many older Tutorials are confusing because Atlassian Changed a lot end of last year. Thanks a lot and wish me luck :) submitted by /u/Problem_Magnet2026 [link] [comments]

How do I delete my account I just created an account in atlassian for a college class and used it once, now it's trying to take 24 USD for a subscription I've never signed for and I'm afraid this thing will try somehow to take money out of me (I haven't put any card detail) I tried to delete my account but it didn't allow me because of that "bill" they want me to pay when I've never subscribed to. I've tried to cancel the subscription but it says it will be canceled in a month, am I safe now? It's really stressing me submitted by /u/Dry-Visual-4559 [link] [comments]

Confluence: Form input to database row Hi friends! I tried to post in r/Confluence but requests to post and attempts to message the moderators consistently error/fail to send, so apologies if this is the wrong place to ask this question. I'm in the process of moving our team's documentation from Sharepoint to Confluence and I've been asked if I can move a specific user's workflows from Monday to Confluence. I know Confluence doesn't natively support forms and I'd need to request a plugin, but I'm having trouble finding one that will for sure fit the bill and need to make sure I don't look like a dingus by going through this entire approval workflow internally just to get something that doesn't work. I can't get a free trial of anything without approval either, so I'm hoping this group can point me in the right direction. This user has us submit a Monday form if we need his support with a client, as he's a singular expert with limited bandwidth. My hope is that I can rebuild the form and have it create a new row in a database every time it is submitted. This database should be able to have other columns that are edited/filled in after the fact and be visible to the rest of the team. Is there a specific solution that comes to mind for anyone? submitted by /u/Independent-Gene3733 [link] [comments]

So glad I didn’t take a job at getdx Yikes - burning friends and advisors is cold blooded. Not a good look for Abi Noda and DX team. submitted by /u/Insurance_Muted [link] [comments]

SOS help w.JQL syntax Hey there! I need a little help with a JQL query to find bugs that do NOT have a "relates to" link type. I tried issueLinkType != "relates to" but it also returns bugs that DO have a "relates to" link if they have any other link type as well. issueLinkType is EMPTY only returns bugs with no links at all. We're on Jira Cloud without ScriptRunner. Is there any native JQL syntax to handle this? - thanks a bunch! :)) submitted by /u/AgileWave3644 [link] [comments]

Is your Confluence admin’s grip on permissions tighter than Iron Maiden’s? 🎸 I was writing a piece about benefits of Free Confluence with Iron Maiden's Somewhere in Time album ) playing in the background. One thing led to another... Ever tried to add a macro That you know they've blocked ten times before? Isn't it strange? Have you asked for space permissions And you know the "Reject" is coming next? It feels pre-arranged Cause you know that they've blocked it before And you feel that getting access is surreal Cause you know when you feel Deja-No... Denied like I've been here before B locked like I've been here before Denied like I've been here before B locked like I've been here before submitted by /u/Kris_K15t [link] [comments]

How to find issues WITHOUT attachments via JQL? Hey everyone, I’m trying to audit our "Bug" reports from the last sprint. Our policy is that every bug must have a screenshot or a log file attached, but I can't find a way to filter the ones that are missing attachments. I tried attachments is empty and issue.attachments is null, but Jira just throws an error or returns nothing. It’s wild that such a basic metadata field isn't queryable by default. Does anyone know a workaround? I really don't want to open 150 tickets one by one to check for screenshots. Any lightweight app or script advice that doesn't break the bank? submitted by /u/Dear-Chemical- [link] [comments]

Struggling with servicedesk knowledge base layout Hi everyone I have been tasked with setting up a knowledge base for some of our products in Servicedesk - so I built it in Confluence, connected it to the project in JSM and now its visible in our Servicedesk portal. Most of our customers will see the knowledge base on mobile, and unfortunately the layout on mobile, especially iOS is not very user-friendly or nice-looking. I feel like I've tried every layout option in confluence, adjusting width, creating tables, informationboxes, moving all content to just text with no tables/boxes for structuring etc. But still, all my content gets squeezed into a narrow column, or does not adjust and I have to scroll horizontally when viewing in Servicedesk. Does anybody have any ideas for what I can do? Or is there no solution? Thanks in advance for tips! submitted by /u/Positive_Put_5350 [link] [comments]

The best customer data platforms (CDPs) for developers, compared The promise of a Customer Data Platform (CDP) is simple: collect data from everywhere, unify it into coherent customer profiles, and pipe it wherever you need it. The reality is that most CDPs were designed for marketing teams running ad campaigns, not developers who care about instrumentation, data quality, and control. If you're a developer who wants flexible SDKs and APIs, predictable pipelines, raw data access via SQL, and integrations that fit into their existing tooling – not a black box optimized for ad platforms – you're in the right place. This guide compares the best CDPs for developers to help you collect, unify, query, and move customer data with confidence. What features do you need in a CDP? At a minimum, a CDP should include: Data collection from multiple sources (web, mobile, server, third-party tools) Identity resolution to stitch together anonymous and known users Audience segmentation and cohort building Integrations with downstream tools (CRMs, ad platforms, email, warehouses) Real-time or batch data syncing The best CDPs go further and give you analytics capabilities so you can actually answer questions with your data: Event-based tracking , with full control over your data schema Funnels, retention, and cohort analysis , to understand user journeys Session replay and behavioral context , to see what users actually did SQL access and raw data exports , for custom queries and external tooling Data warehouse integration , so your CDP works with (not against) your existing stack Privacy-first design , to stay GDPR/CCPA compliant without extra work Here's how some of the most popular CDPs compare: You might notice some absences: Salesforce Data Cloud , Adobe Real-Time CDP , and Treasure Data are all major enterprise players. They're powerful, but they're also designed for large marketing orgs with dedicated implementation teams and big budgets to match. This guide focuses on tools that developers can actually evaluate, set up, and get value from wit...

The best error tracking tools for developers, compared Every developer has shipped a bug that slipped through tests: no one is perfect. What matters is how quickly you find out, understand the cause, and ship a fix. Enter, error tracking tools. A good error tracking tool will give you context, not just stack traces: it'll show you what the user did right before the exception, which release it came from, and what else broke as a result. This guide compares the most popular error tracking tools for developers right now, what features they do and don't offer, and who they're built for, so you can decide which one is right for your needs. What features do you need in your error tracking tool? At a minimum, most good error tracking tools will offer things like: Real-time error capture and grouping Full stack traces, source maps, and contextual metadata Alerts and assignment workflows for triage SDKs for major languages and frameworks Integration with CI/CD, logs, and performance data The absolute best error tools tend to go a bit further by including things like: Integration with session replay: Useful for linking session recordings to real user sessions, so you can better understand the context of when an error occurs and debug the steps. Integration with product analytics: Useful so you can correlate the impact of errors on product usage, conversion, and revenue. Very broad SDK and framework support: Support for the likes of Next.js, Python, and React are typical among all the tools in this list, but some tools go deeper by offering SDKs for less popular frameworks, and even video game engines like Unreal Engine and Unity. Here's how some of the most popular error tracking tools compare at a glance: What's the best error tracking tool for developers? 1. PostHog PostHog is an all-in-one developer platform that goes beyond error tracking and stack traces by combining error tracking , session replay , analytics , and feature flags into one platform. Each exception can be linked to the related session replay, user, and feature...

Job market for senior / Atlassian folks, what’s it looking like? submitted by /u/SadBoy-86 [link] [comments]

7 best session replay tools for mobile apps There are plenty of session replay tools out there, but not all of them support mobile, and those that do vary significantly in depth, platform support, and what they capture alongside replays. This guide covers the seven best mobile session replay tools: what they do better, which frameworks they cover (iOS, Android, Flutter, React Native...), where they fall short, and who they're actually for. 1. PostHog What is PostHog? PostHog (that's us 👋) is an all-in-one developer platform built to enable engineers to create better products. It includes session replays and a whole bunch more, such as product analytics , LLM analytics , error tracking , experiments , and feature flags . It's designed for product-minded engineers, founders, growth teams, and product managers who need to move fast and iterate based on reliable, actionable insights. Supported features div>div]:!block max-w-screen " dir="ltr"> div]:px-2 w-min [&>div]:py-2 "> Supported platforms Mobile platforms where session replay is available Android, iOS, React Native, Flutter, Unity (alpha) Console logs Capture console output from the browser for debugging ✓ Network monitoring Monitor network activity during sessions ✓ Filter recordings by user or event Find specific recordings by filtering for users or events ✓ AI summaries AI-generated summaries of session recordings Beta Conditional recording Only capture the sessions you want based on conditions ✓ Privacy masking for sensitive content Automatic and manual masking of sensitive user data ✓ Heatmaps Visualize where users click and scroll on your website ✓ Scrollmaps Visualize how far users scroll on your website ✓ Rage clicks Track repeated clicks in the same place ✓ Rage taps Identify repetitive taps made out of frustration ✓ Dead taps Detect taps on elements that do not respond or trigger an action ✗ Crash reports Learn what happens before a crash without complex debugging or reproduction ✗ Experiments Run statistically rigorous A/B/n tests and validate id...

Atlassian application stuck “Under Review” for months — what does this mean? Hi everyone, I applied to multiple Software Engineer II roles at Atlassian and wanted to understand what “Under Review” really implies in my case. Here’s my situation: Software Engineer II roles Status: Under Review since Jan 6, 2026 (2 applications) Status: Under Review since Nov 17, 2025 (1 application) No communication or updates so far Out of my total applications: I have received a rejection email for one role The other three roles are still showing “Under Review” with no updates My questions: Does “Under Review” for this long usually mean silent rejection / backlog / hiring freeze? Is there still a realistic chance of getting a response after 2–4 months? Should I follow up somewhere, or just assume it’s inactive? Has anyone experienced delayed responses from Atlassian like this? Would really appreciate insights from anyone who has gone through their hiring process. Thanks in advance! submitted by /u/Expensive_Regular203 [link] [comments]

What we wish we knew about building AI agents One thing on every startup’s mind: Should we build an AI agent? We had this thought two years ago, released an “AI product assistant” 6 months later, iterated, and then relaunched as PostHog AI in November last year. We learned a lot along the way that we wished we knew when we started. With that knowledge, we could have… Launched months earlier. Provided a better early experience to users. Made progress on capabilities faster. To help you build a better agent faster, we’re sharing what we wished we had known about building AI agents. 1. Should you build an MCP server instead? Should you even build an AI agent into your product? The capabilities of agents are unquestionably valuable but this does not mean you need to build a custom one. Making your product accessible to agents is often a better option. Could your agent capabilities just be an MCP server ? These are simpler to build and require less maintenance, and for us, is used as much as our built-in agent, PostHog AI. For example, 34% of dashboards created by AI were done through our MCP server (18% of all dashboards created). Sources of dashboards created last week MCP servers are great if you expect your users to be developers or people combining your product with others in their ✨ agentic workflows ✨. Just as importantly, MCP servers validate demand for further agentic capabilities. Custom agents are better when your users are non-engineers , when compliance blocks external agents, or when you need full control of the user experience (for example, custom image generation). Even when you decide to go custom, consider if simpler alternatives fit your use case: For one-shot Q&A like generating product descriptions, try a simple LLM call with good prompting For a single task like SQL or code generation, use a specialized model with structured output For a multi-step but predictable flow like email classification plus response drafting, create a hardcoded workflow with LLM steps Although PostHog AI is an agent no...

7 best free open source business intelligence tools right now Not everyone has money to dish out for an enterprise Tableau contract, and not everyone wants to send their data to Looker (Google) either. Free and open source business intelligence tools solve both these problems by making BI accessible and keeping you in control of your data. The challenge becomes choosing the best one. To help you, we've put together this list of the top free and open source business intelligence tools you can use. How are these tools being evaluated? We evaluated these tools based on their: Ability to connect to data sources, query them with SQL, and build dashboards Their open source credentials (GitHub stars, license, etc.) Their unique positioning in the business intelligence space What is the best business intelligence tool for startups? PostHog provides startups like HeadshotPro , with a full suite of tools they need to build a great product, including pre-built web and revenue analytics dashboards, simple connectors for their existing data sources ( Postgres , Stripe , Hubspot , etc.), and a bunch more. What is the best business intelligence tool for data analysts? Metabase provides a comprehensive set of database connectors as well as powerful query building and visualization tools that make it easy for data analysts to build dashboards and insights. What is the best business intelligence tool for infra engineers? Grafana provides engineers with the "intelligence" their looking for: observability, monitoring, and more for their infrastructure. They also provide a ton of plugins for all the tools and services engineers use. What is the best business intelligence tool for product managers? Because it can easily combine product and business data, PostHog is the best business intelligence tool for product managers. It enables them to get a complete view of their product while also providing the advanced SQL querying they need to go deeper. What are the best free and open source BI tools right now? 1. PostHog License: MIT GitHub stars: 32.1k ...

I added PostHog dashboard import to my native macOS/iOS companion app Hey! I'm the developer of HogLens, a native PostHog companion app for macOS and iOS. Just shipped v1.2 with a feature I've been working on for a while: you can now import dashboards directly from PostHog via API. The import workflow analyzes each insight for compatibility, handles duplicates, and supports Trends, Funnels, Retention, Lifecycle, and Stickiness queries. Legacy filter-based insights (pre-2023) are auto-converted too. Other new stuff in this release: Funnel charts — stepped visualization with conversion rates Retention charts — cohort-based grids with heatmap cells Re-Sync — check for changes in the original PostHog dashboard and review before applying Re-Analyze — automatically detects when previously incompatible insights become supported I built this because I wanted to use my existing PostHog dashboards on my Mac and iPhone without recreating them manually. Curious if anyone else finds this useful. Website: hoglens.app Full details: https://hoglens.link/f8c submitted by /u/KREANIQS [link] [comments]

WTF does a product manager do? (and why engineers should care) In our last issue, Ian Vanagas wrote about how engineering has escaped the codebase. How engineering tools, mindset, and identity increasingly shape every function, especially at startups. We’ve seen this first-hand at PostHog , but it’s not an isolated trend. The lines between product management and engineering are blurring, too. 1 Thanks to LLMs, figuring out what to build is now a greater bottleneck than how to build it, and it’s forcing engineers to think more like product managers (PMs). In this issue, we’ll help you take advantage of what product managers have already figured out by going over the top three skills in their playbook. 1. Gather the right context Providing context is a product manager’s most important job. What exactly do we mean by context? In the same way that sailors used to navigate by the stars, engineers depend on context to make the right product decisions. Good context points teams in the right direction; great context can change a company’s entire trajectory. Take Duolingo for example. In a guest edition of Lenny’s Newsletter , Duolingo’s Head of Product, Jorge Mazal, recounted how the company fixed its stalling growth problem. The team initially focused on friend referrals, premium trials, and in-game mechanics. Nothing worked, and daily active users (DAU) continued to decline. But then Mazal and the data science team discovered that current user retention rates (CURR) were 5x more impactful on DAU than any other projected metric. That single piece of context completely shifted the product roadmap. Instead of trying to acquire new users, the team invested in keeping existing learners hooked with leaderboards, daily streaks, and – of course – passive-aggressive push notifications from everybody’s favorite lime green owl. Four years later, Duolingo successfully exited with massive 4.5x DAU gainz. Product metrics like CURR and DAU in Duolingo’s story are just one form of context. There are many more, such as: Competitor landscape. What are...

Migrate your Heroku app to Render in minutes with AI agent skills submitted by /u/anurag-render [link] [comments]

I am sending out moderator team invites Hello all. I will be sending out moderator team invites here shortly to a list of people who expressed interest in being on the moderator team. I will let them coordinate amongst themselves and after a few months (or six) I will re-sort the moderator team based on a) if they have a consensus on who would be a good fit as the top mod and b) possibly some input from me based on observation and who is actually doing the work of active moderating on the subreddit. Otherwise, I am going to cede moderation duties to this team and will be otherwise uninvolved in the moderation of this subreddit. But wait, you were going to have us vote on the new mods! Yes, I was, and I was in the middle of setting up a nice ranked choice voting website with all of these applications, which I paid ACTUAL money to do. But then I have to deal with [absolutely insane rants] [imgur link] like this one, and I've officially lost my patience due to this harassment. This is why we can't have nice things, guys. This list of people have all expressed interest in being moderators and all seem like they would be operating in good faith. So I am sending out invites to them. Moderators can always be added later if there are additional interested and qualified people. And if there are problem mods after 3-6 months, I will keep my account linked as top mod for now only for the purpose of reshuffling the moderator team and any issues can be dealt with at that time]. [u/jlin8293] [u/Redditdotlimo] [u/anamexis] [u/jackrschumacher11] [u/Tr3v0r] [u/GarfoTheCat] [u/Zurkarak] [u/standingyon] There are a few other candidates who've expressed interest in modmail and chat who I think would be very good additions as well. I will wait on their official "applications" before sending any invites to them. To anyone who doesn't like this decision, I invite you to read the screed linked above and that should give you enough context as to why I don't want to continue participating in active moderation of this subreddit and...

Todoist pricing update: Addressing your Questions (from the Todoist team) Hey everyone 👋🏽 Dominique here, Head of Product at Doist, makers of Todoist. I want to address some of the questions and concerns you’ve shared about the upcoming pricing changes. Firstly, thank you to those who’ve shared feedback. We’ve been reading every comment, and welcome your honesty. Both the support and the criticism genuinely help us do our jobs and build a better Todoist. What’s changing Starting December 10, 2025, our pricing will be updated as follows: Pro plan : $7/month or $60/year (previously $5/month or $48/year) Business plan : $10/month per user or $96/year per user (previously $8/month per user or $72/year per user) We know price increases are never welcome news, and this wasn’t a decision we made lightly. To keep Todoist fast, dependable, and improving for everyone, we sometimes need to adjust our pricing so we can keep building for individuals and teams. We’re in it for the long term. Legacy pricing plans I'd like to apologize for the confusion we created around legacy pricing 🙏🏽 Please let me clarify: If you’ve been continuously subscribed to Pro since before June 2022, you’ll remain on your legacy pricing with what we’re now calling the “Pro Legacy plan.” Similarly, if you subscribe through the App Store (regardless of when you subscribed), you’ll stay at your current price due to App Store policies. All App Store subscriptions will be on the Pro Legacy plan and have the ability to upgrade to the current Pro plan and its limits on or after December 10, 2025. The Pro Legacy plan will continue to receive all bug fixes, security updates, and any new features that are released to our free plans. However, new paid features released after December 10, 2025, won't be added to this plan. Some newer features, such as Ramble, will continue to be available on the Legacy Pro plan, but with the same usage limits that apply to the free plan. If you believe you should be on the Pro Legacy plan but received an email about a price increase, please reach out to...

Help with pricing and production deployment So, I need 2 or 4 services for a e-commerce application. I want to create a nextjs app for the front, I need a db and probably a api and a react app just for the admin part. I want to know how much something like that would cost, for example I can see that api that is a web service would be like 7usd but with the nextjs app idk if I can use static site that is free or do I need to use a web service because nextjs is a server render. Also my account is free but I see that I can pay 19usd for some features. Do I need to pay those 19 for deploying my app? And I remember somewhere I read something about free postgre db idk if that's true. Can you help me to know how much something like this would cost? The ideal project would be: 1. Nextjs 2. Api 3. Db 4. React for the admin If that’s too expensive I'm thinking on merge everything on nextjs because you can do api on nextjs so it would be: Nextjs with the api inside Db React (I'm guessing reacts service is free) Also: what's the limits on the free static site service? submitted by /u/Tyrone2209 [link] [comments]

The DuckDuckGo subscription now includes more advanced AI chat models Our subscription now unlocks premium AI models like GPT-5 and Claude 4 Sonnet in Duck.ai at no extra cost (along with our VPN, Personal Info Removal and ID Theft Restoration)! AI tools have quickly become a significant part of people's online experience, but there's a gap between how often we use AI, and how safe and in control we feel about it. That's why we created Duck.ai , which gives you access to popular AI models with the following added protections built by us: Anonymized chats No AI training Local chat storage Instant deletion Today, we're expanding Duck.ai by giving subscribers access to more advanced AI models that are better at following detailed instructions, maintaining context through extended chats, and delivering deeper, more nuanced responses. https://preview.redd.it/g1wh77b6y4nf1.jpg?width=3840&format=pjpg&auto=webp&s=f348e3d16180068cd1237520650f5acad6a274b0 The DuckDuckGo subscription expands the great protection you get from our free offerings, covering even more of what you do online: DuckDuckGo VPN Personal Info Removal (US only) Identity Theft Restoration Premium AI Models And the price is staying the same in all regions: $9.99 USD/month or $99 USD/year. Want to learn more? Check our blog post . Ready to give it a try? Start your 7-day free trial at 👉 duckduckgo.com/subscribe Already a subscriber? Update your DuckDuckGo app to get access to this new feature. submitted by /u/duckduckgo [link] [comments]

A statement from our CEO on the US v Google remedies A statement from our CEO on the US v Google remedies: "We do not believe the remedies ordered by the court will force the changes necessary to adequately address Google’s illegal behavior. Google will still be allowed to continue to use its monopoly to hold back competitors, including in AI search. As a result, consumers will continue to suffer. We believe Congress should now step in to swiftly make Google do the thing it fears the most: compete on a level playing field." — Gabriel Weinberg submitted by /u/duckduckgo [link] [comments]

Need help with PostHog? Looking for help with PostHog? Great! Here are some resources to help you get the information you need quickly... Official support Community support Official docs Tutorials, guides, blogposts ​ submitted by /u/Narrow-Battle [link] [comments]

New rules on self-promo Hello r/Substack , The subreddit is getting crowded with low-effort posts linked to Substack posts and it is getting increasingly difficult to weed out the spam. r/Substack is a place to have meaningful discussions about the Substack platform and help fellow Susbtackers make good use of the platform. Hence, moving forward this subreddit will not tolerate any self-promotion. The only exception to this is if your post is about Substack or tips and strategies to grow on the platform. The flair for self-promotion has also been removed. Don’t worry, this update will not mess with your dreams of building a purple-ticked newsletter. This was never a good place to advertise your work, anyway. See our other pinned post for more information on that. Another spammy area that we have been seeing a lot of uptick these past few months is posts asking for recommendations. If you are looking for recommendations, Substack’s leaderboard on specific topics is a much better resource than this subreddit. This is not the space to solicit hyper-specific recommendations for individual users. Usually, these posts end up with new users promoting their newsletters and not in actual thoughtful recommendations. Henceforth, such posts will also be removed. The third spammy category is the increase in posts soliciting cross-recommendations. While this is a space where r/Substack can be useful, individual posts in this regard are unnecessary. For this purpose, you can use the new master thread pinned on the r/Substack home page. I hope these changes will make this subreddit a more helpful place for anyone looking to learn more about Substack. -xx u/AerieFreyrie submitted by /u/aeriefreyrie [link] [comments]

Thread: Soliciting Recommendations Hello r/Substack , As we have seen an uptick in posts soliciting cross-recommendations, here is a thread to make these requests. This will help in keeping the discussion on the main subreddit more on topic. Please leave any cross-recommendation requests below. Please go through other recommendations requests and reply to relevant comments. We hope you find what you are looking for from this community. -xx u/AerieFreyrie submitted by /u/aeriefreyrie [link] [comments]