nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How can I share Jira tickets with a client who is so locked down and security conscious?

Claire Buckley

They are adding requirements to their new Jira for Server Instance, but have not set up any syncing or sharing with our Cloud instance.

They are new to Jira and are unsure about data security and so refuse to share requirements via a sync add-on.

They are expecting a human to be the double entry slave which with the number of tickets we have and the number of files shared, becomes hugely problematic.

What reassurance is out there regarding data security that I can provide to them so that I can set up a seamless collaboration and work flow?

Accepted answers

Brant Schroeder

Claire,

If you are using the Cloud you can point them here for security information. https://www.atlassian.com/trust/security

If they are concerned about a sync tool that you want to use you can always have them utilize webhooks and the JIRA API to create issues in your cloud instance. This way they would be in full control of what information is sent to your instance. It wouldn't keep the issues synced in the future though.

Matthias Gaiser _K15t_

Hi @Claire Buckley,

I am working for such a sync add-on, Backbone Issue Sync.

What best worked for us in the past with similar customers was to have a joint call with both partners talking about their fears and addressing their specific needs. So my advice would be: Choose a syncing add-on you like and arrange a joint meeting.

For Backbone, I would assure them that full Jira permissions are respected and only a limited subset of issues or fields of an issue will be synchronized.

Cheers,
Matthias.

PS: If you would like to have a call with us, drop us a line at support@k15t.com.

francis

(I'm with the team that builds Exalate - also a synchronisation solution)

You might use an argumentation build around the fact that having a human copying data is not a guarantee that sensitive data is not leaking. Human do make mistakes.

Using a systematic approach for exchanging information brings more control on what information is shared when.

Synchronisation solutions provide you fined grained control and traceability and less friction in the process.

All comments

Brant Schroeder

Claire,

If you are using the Cloud you can point them here for security information. https://www.atlassian.com/trust/security

Matthias Gaiser _K15t_

Hi @Claire Buckley,

I am working for such a sync add-on, Backbone Issue Sync.

For Backbone, I would assure them that full Jira permissions are respected and only a limited subset of issues or fields of an issue will be synchronized.

Cheers,
Matthias.

PS: If you would like to have a call with us, drop us a line at support@k15t.com.

francis

(I'm with the team that builds Exalate - also a synchronisation solution)

You might use an argumentation build around the fact that having a human copying data is not a guarantee that sensitive data is not leaking. Human do make mistakes.

Using a systematic approach for exchanging information brings more control on what information is shared when.

Synchronisation solutions provide you fined grained control and traceability and less friction in the process.

Claire Buckley

Thank you Mattias! They are slamming it down but I will persevere!

Claire Buckley

Thank you. This is really helpful! I will forward that to their Info sec team.

Claire Buckley

Thank you. Good argument and I will also look at your tool for syncing.

Scott Theus

@Claire Buckley, if you are interested here are some instructions on how to set up a bi-directional sync with Backbone.

https://community.atlassian.com/t5/Marketplace-Apps-questions/Jira-Backbone-issue-quot-backsync-quot/qaq-p/742781

If it helps, I used it to sync from our instance at Parker to a vendor instance. Our network is also locked down tight, but since the application uses a Jira user to access the instance we were able to treat it just like any other user.

-Scott

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-software

app

sync

client