Uploaded image for project: 'Jira Software Cloud'
  1. Jira Software Cloud
  2. JSWCLOUD-17623

Cross Project Issues Dependencies



    • Feedback Policy:

      Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.


      Yes, there is a way both in classic and next get projects to link issues with "blocked by" and "blocks" link types between issues in different projects, but that is very cumbersome to setup and therefore usually not being used (too much friction, steps to complete, switching between projects, etc). So, as a result various  workarounds are used. One example (that we are using in classic projects) is to have 2 boards for each project : 1 board is "traditional" and filters in only the issues fro that project and 2nd board is "cross team" board that filters in issues like this: 

      project = MYPRJ or labels = MYPRJ ORDER BY Rank ASC

      So, when other projects add a label to their issues that matches the project key of the project they depend on - their issue will show up on that "cross team" board. Very easy to use, but creates other problems as you can imagine, since this is technically a "hack" or workaround if you will.

      So, the request here is to add a cross project issues dependencies functionality to next-gen projects that could combine the pros of traditional old school issue linking and the hacks/workaround as one described above and make it so it is easy to setup a scenario where an issue from one project depends on another project - either the same issue shared between both or a new one created in the other project and linked IN ONE STEP and from the same screen/page of the original issue that has a dependency. The key here is that it must be simple and accessible, therefore use case / acceptance criteria:

      1. User John creates issue PRJA- in project PRJA
      2. User John  opens details page for the issue PRJA-1
      3. In that screen user John adds a dependency on the PRJB
      4. Either creating issue PRJB-1 directly in PRJB, but without leaving the screen of PRJA-1
      5. Or somehow specifying PRJB project key as dependency
      1. When user Bob looks at the board of PRJB they either
      2. see PRJB-1 created and linked to PRJA-1
      3. or somehow see that PRJA and specifically PRJA-1 issue has a dependency on PRJB


      As far as issue types - either story, task, bug or even a "special" issue type for such inter-dependencies - does not really matter as long as it is easy to setup without switching back and forth between screens of two projects/issues.




            Unassigned Unassigned
            yury.zhytkou Yury Zhytkou
            2 Vote for this issue
            2 Start watching this issue