External Share for Jira Earns “Apps in the Spotlight” Badge!

We’ve got some nice news to share - External Share for Jira has been featured in the latest “Apps in the Spotlight”.

This program highlights apps that have shown steady growth and strong adoption over the past quarter. It’s a small badge, but for us it means a lot. It tells us we’re heading in the right direction and building something that people actually find useful.

Why this matters to us

We’ve been working on External Share for Jira for quite a while now, focusing on a simple goal: making it easier to share Jira content with people outside your organization, without creating extra friction or losing control over what’s shared. Over time, more teams have started using the app in their daily work. That gradual growth - new users, new use cases, ongoing feedback - has shaped what the app looks like today. This recognition feels like a reflection of that steady progress.

We’re genuinely grateful for how the app has been received so far. It’s grown thanks to real use, honest feedback, and many small improvements along the way. There’s no single big moment behind it, just consistent work from the team and conversations with users who tell us what works and what doesn’t. That’s what keeps the app moving forward.

The story of the External Share

We also asked Krzysztof Bogdan , Co-CEO, co-founder, and currently leading the External Share for Jira team, to answer some questions about the app. Let’s dive into the External Share story.

How the idea was born

What problem were you trying to solve when you first thought about External Share (the exact moment/situation/personal experience that pushed you toward building this app)?

While I was working in a big corporation, I saw multiple internal Jira instances. Sometimes it was painful to get access to those when needed. Endless e-mails, required approvals, etc., just to collaborate on one ticket. That’s when I thought - there should be a better way.

Beginnings

What did the first version of the app look like?
It was super basic: 1 ticket - 1 share link. Share link had maybe 3 options. There was no way to see how many links were created, no customization, just the basic functionality. But at the time, there weren’t any alternatives on the Atlassian Marketplace; the closest one was Email This Issue, but it didn’t solve all the problems.

Technical challenges

What was the biggest technical struggle while creating the app? At what stage did you involve the team to help you?
The biggest challenge I remember was the custom-domain feature - a big feature with plenty of changes. So it took weeks of my work to provide it.
I remember that just after release, I found a significant security problem within the feature, and initially, I thought there was no way to fix it. I had the option to revert the feature or fix the problem somehow. The first option was naturally easier, but since I already invested so much time and effort in the development process, I knew I had to come up with a solution… and I did! It was complex, uneasy, but (as you can see) doable. If I knew beforehand about the problem and its scale, I am sure I would give up.

Atlassian Marketplace

When you launched the app on the Atlassian Marketplace for the first time? What was the initial feedback?
That was mid 2019, I think. The app was basic at that time, but it was already solving some real pain points in day-to-day work. Initially, the installation count wasn’t high, but feedback was really positive, so it encouraged us to develop the app further.

Growth

How has External Share evolved since its initial release? What features or changes were driven directly by user feedback?

I would say - it is not the same app. Comparing the current version and the first one is like comparing a smartwatch with a sundial. Back in 2019, I couldn’t predict or imagine how much the app would evolve. And the best part is that, I think, around 90% of the app features are based on customer feedback. That’s the best proof that the app is fulfilling its purpose and solves real-life struggles of our customers.

Future

What’s next for External Share? How do you see the product evolving in the next few years?

We closely watch how Jira evolves, and we adapt to it. We make it possible to share what Jira offers. It started with sharing a single work item. Then the filter view, board, and roadmap. We are limited to what is possible to access via API, but within that, we try to make Jira open to external users.

In terms of future development, what is definitely a never-ending story: adding more knobs to customize how data is shared - and it is not an easy task. Adding more checkboxes chaotically does make the UI complicated and feels cluttered. Everything needs to fit well in what we already have. That is where most work goes.

Thanks for being part of it

If you’re using External Share for Jira - thank you. Your feedback and trust are a big part of how the app evolves.

We’re glad to see it growing, and we’ll keep working on making it better.