Our team uses JIRA for both requirement management and bug tracking. This setup worked fine when we handled one project at a time. Now we’re dealing with three different project proposals that have overlapping requirements. For example, one requirement might be needed for projects A and B, while another requirement is shared between projects B and C. I want to create one JIRA ticket for each requirement instead of duplicating them across projects. The problem is that JIRA tickets are tied to specific projects in a one-to-one mapping. Is there a workaround in JIRA to handle this situation? Maybe there’s an add-on or plugin that can help? I’m also open to suggestions for other tools that might work better with JIRA for this type of cross-project requirement tracking.
We hit the same problem last year managing requirements across multiple client projects. JIRA’s Components feature saved us - we set up a dedicated requirements project where each shared requirement becomes a component you can tag and filter across different projects. Then you just create epic links or issue links to connect these components to specific project tickets. Way cleaner visibility than duplicate tickets, and reporting’s straightforward since there’s one source of truth for each requirement. We also tried Confluence integration for detailed requirement docs while keeping lightweight tracking tickets in JIRA. Cut our duplicate maintenance overhead big time and made cross-project planning meetings way more productive.
check out jira portfolio or advanced roadmaps. we used to struggle too, so we made a “shared requirements” proj and linked tickets to the actual ones. yeah, it’s more work, but it totally helps with keeping track of deps.
Been there, done that. I use issue linking and labels to track everything. Set up a master project called ‘Core Requirements’ where all shared requirements live as epics or stories. In each actual project, I link back to the master requirement using ‘relates to’ or ‘implements.’ Labels show which projects need each requirement - ‘proj-A’, ‘proj-B’, whatever. The trick is staying disciplined about updating the master requirement when linked tickets change status. Takes some setup work upfront, but it beats the hell out of syncing duplicate requirements everywhere. Status reporting becomes way easier since you can see implementation progress from the master view.