问HN：为什么将外部合作伙伴整合到Jira中这么困难？
我在航空航天/国防以及其他受监管的B2B项目中不断听到相同的事情。即使两家公司内部都使用Jira，一旦客户（或其他外部合作伙伴）提议“我们就共享一个Jira项目”，这就会变成一个持续数周或数月的IT和信息安全的折磨……因此团队最终还是回到了电子邮件和Excel跟踪表的方式。
如果你经历过这种情况，我很想听听详细的故事。一些可以引发讨论的话题：
>> 到底是什么让这变得困难？（单点登录/身份提供者、用户配置、域策略、多因素认证、VPN、IP白名单、Atlassian Access、SCIM、承包商等）
>> 阻碍因素通常是IT、安全、合规、采购/供应商风险，还是Jira管理员本身？
>> Jira Cloud与Jira Data Center：哪个在外部协作方面更糟，为什么？
>> 常见的“政策红线”是什么，导致坚决拒绝？（最小权限、租户分离、可审计性、数据驻留、CUI/ITAR、SOC2等）
>> 最终你使用了什么变通方法（共享电子表格、共享邮箱、独立的“影子Jira”、Confluence页面等），以及出现了什么问题？
>> 如果你成功实现了跨组织的Jira协作，最终的设置是什么，花了多长时间？如果没有成功，发生了什么？
背景：我试图理解真正的根本原因和失败模式——这主要是技术性的问题（身份和权限）还是主要是组织/政策方面的问题，以及哪些部分实际上是可以解决的。
查看原文
I keep hearing the same thing across aerospace/defense and other regulated B2B programs. Even when both companies use Jira internally, the moment a customer (or other external partner) suggests “let’s just share a Jira project,” it turns into a weeks/months-long IT + infosec ordeal… so teams fall back to email + Excel trackers.<p>If you’ve lived this, I’d love detailed stories. Some conversation starters:<p>>> What exactly made it hard? (SSO/IdP, user provisioning, domain policies, MFA, VPN, IP allowlists, Atlassian Access, SCIM, contractors, etc.)<p>>> Is the blocker usually IT, security, compliance, procurement/vendor risk, or the Jira admins themselves?<p>>> Jira Cloud vs Jira Data Center: which is worse for external collaboration and why?<p>>> What are the common “policy red lines” that cause a hard no? (least privilege, separation of tenants, auditability, data residency, CUI/ITAR, SOC2, etc.)<p>>> What workarounds did you end up using instead (shared spreadsheet, shared mailbox, separate “shadow Jira,” Confluence page, etc.) and what broke?<p>>> If you did make cross-org Jira work, what was the setup that finally passed and how long did it take? If you didn't make it work, what happened?<p>Context: I’m trying to understand the true root causes and failure modes -- whether this is mostly technical (identity + permissions) or mostly organizational/policy, and what parts are actually solvable.