提问 HN：为什么将外部合作伙伴集成到 Jira 这么难？
1 分•作者: dnlh_lvg•6 个月前
我一直在航空航天/国防和其他受监管的 B2B 项目中听到同样的事情。即使两家公司内部都使用 Jira，一旦客户（或其他外部合作伙伴）建议“我们来共享一个 Jira 项目吧”，就会变成一个需要 IT 和信息安全团队数周/数月才能解决的难题…… 因此，团队最终还是回到了电子邮件 + Excel 跟踪表。<p>如果你经历过这种情况，我很想听听详细的故事。一些讨论话题：<p>>> 究竟是什么让它变得困难？（SSO/身份提供商、用户配置、域策略、MFA、VPN、IP 白名单、Atlassian Access、SCIM、承包商等）<p>>> 阻碍通常是来自 IT、安全、合规、采购/供应商风险，还是 Jira 管理员本身？<p>>> Jira Cloud vs Jira Data Center：哪个更不利于外部协作，为什么？<p>>> 哪些是导致直接拒绝的常见“策略红线”？（最小权限、租户隔离、可审计性、数据驻留、CUI/ITAR、SOC2 等）<p>>> 你最终使用了哪些替代方案（共享电子表格、共享邮箱、单独的“影子 Jira”、Confluence 页面等），以及哪些方案失败了？<p>>> 如果你成功实现了跨组织 Jira 的协作，最终通过的设置是什么，花了多长时间？如果你没有成功，发生了什么？<p>背景：我试图了解真正的根本原因和失效模式——这主要是技术问题（身份和权限）还是主要是组织/策略问题，以及哪些部分是真正可以解决的。
查看原文
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.