No data creep – The snappiest way to Jira reports just turned into a zero data risk app.

Written by Rina Nir

No data creep. The snappiest way to Jira reports just turned into a zero data risk app.
Author

Rina Nir

Date

Apr 13, 2024

Category

For Project & Product Managers | Pharma & Medical Devices

Share:

Yes, we mean what you think it means. As of May 2022, Jira Snapshots for Confluence stores all your data inside the Atlassian infrastructure. Zero data risk means that we do not store your sensitive data, like the Jira report data, on our infrastructure.

Cloud is the future and we all are going there. We all wished we could do that while keeping total control of our data. Because, while we all want:

  1. better networking,
  2. speedier processing,
  3. more features,
  4. daily software updates,
  5. beautiful interfaces
  6. and 99.9999% availability

without having our own IT powerhouse.
The single thing we do not want is increased data risks. Our data is the beating heart of our organization and we want to protect it at all costs.

You have made one giant step and moved to the Atlassian Cloud. You even have done the careful due diligence of Atlassian and are keeping up to date with their trust practices. Now, what to do about those Marketplace Apps? How does the power or convenience that the app brings weight against the risk of data control creep? Is trusting yet another vendor with storing bits of your data worth it?

This is not a tradeoff you need to be forced to make. That’s why we invested in making Jira Snapshots into a zero data risk app. When you use Jira Snapshots for Confluence, no sensitive data bits find themselves lurking anywhere outside Confluence.

Yes, Jira Snapshots is a data-intensive app without the data control creep effect. It stores all the Jira reports it generates in Confluence.

So, how did we design this data-intensive app to remove any data control creep?

Jira Snapshot is a data-intensive application. It grabs Jira data and creates static Jira reports in Confluence. So where do we store this static Jira data?

When we set out to get to zero data control creep we relied on the same guiding principles that always guide us. Jira Snapshot is an extension to Confluence and it needs to feel like a native part of Confluence. The unsuspecting user should be oblivious to the seeming points between Snapshots and Confluence. Jira Snapshots is like an extra button on your car’s steering wheel. Exactly like this extra button, it needs to wire itself into the existing wiring, and play by the rules. We did not want to create our external wiring in the already sophisticated platform that Confluence provides.

So when Jira snapshot generates a snapshot, it stores it in a location that is natural to Confluence: as an attachment to the Confluence page, it belongs to. Attachments are first-class citizens in Confluence so we get a lot of good features out of the box. For example- attachments may have many versions. This means that we store many versions of the same snapshot without cluttering the attachment areas. Another advantage is that attachments can be very large. In fact, you can adjust the attachment size limit and increase it as you need. The default limit is 100MB (which is anyway an overkill as far as snapshot sizes go)

What more do we do to increase the credibility of Jira Snapshots?

We want to be the most trustworthy way for Jira reports. Reaching zero data risk was one step. We are already hard at work on the next milestones.

As we write this post, we are onboarding the app to the marketplace security bug bounty program. Our other app, Speedy PDF Sign-Offs for Jira is a long-time member of the program. All our learnings from that experience are already informing the design of Jira snapshots. But as you know, security is an ever-evolving expertise so we expect to learn even more from this new experience.

To top this up, we are also in process of joining the Atlassian Marketplace Fortified Apps program. The program is designed to help enterprise customers identify enterprise-ready cloud apps. We will share the news when we achieve this milestone.

Does your team export Jira reports from Jira to a file? Well, that’s a data creep

Does your team export Jira reports from Jira to a file? Well, that’s a data creep
While we are in data control territory, le’s talk about exports of Jira data. Yes- these are excel or word documents your team exports for Jira. These consist of sensitive data hiding in emails, google drives, slack channels, WhatsApp messages, and who knows where.
Jira data is exported and shared much more than any one of us wants to admit. Why not give your team a more secure and easy way to share that data?

You can try Jira Snapshots for free. People tell us that using it is as easy as it gets.
Download it here.

Sounds like something that might help your organization?

Try Report Builder for 30 days free of charge!

Don’t miss these

Jira Snapshots integrated with Scroll Documents, for a smooth regulatory submissions flow

Jira Snapshots integrated with Scroll Documents, for a smooth regulatory submissions flow

With the latest integration between K15t’s Scroll Documents for Confluence and RadBee’s Jira Snapshots for Confluence, product teams can manage multiple versions of their specifications documents. This ensures that the documentation is preserved exactly as it was upon submission. Jira Snapshots helps generate the specifications documentation from Jira, while Scroll Documents makes it possible to compile these pages into one neat submission.

Have more questions?

Or reach out to us and we’ll show you how we can make your work easier, faster and help you get more done.