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; } } }

Dependencies between different projects

sarathgd

Hi,

I have two projects X&Y, which will have multiple issues like EPIC>>Feature>>Story>>Task>Sub-task/s, in a structure.

Some of the Issues in each of these projects are blocked or depends which I am trying to show in a column by using below logic:

issueLinks.type.filter(array("Blocks").contains($)).

But the problem is - for some of the rows (different issue types) - entries in the column showing dependencies multiple times like - blocks, blocks, blocks etc

Ex:

EPIC ---- Blocks, Blocks - my understanding is - since child entries of EPIC having blocks - here structure showing blocks more than once.

Feature - Blocks - means if i understand correctly - Feature is blocking EPIC

Stroy - Blocks - means if I understand correctly - Story blocking feature

My requirement is I want to show 'blocks' only once at EPIC/feature/story level though child entries have blocks.

Appreciate any help here.

Accepted answers

David Niro

Hello @sarathgd ,

David from ALM Works here.

For this, you will want to use the UNIQUE function. The formula below should work for you.

issueLinks.type
  .FILTER($.CONTAINS("Blocks"))
    .UNIQUE()

Please let me know if this helps.

Best,
David

All comments

David Niro

Hello @sarathgd ,

David from ALM Works here.

For this, you will want to use the UNIQUE function. The formula below should work for you.

issueLinks.type
  .FILTER($.CONTAINS("Blocks"))
    .UNIQUE()

Please let me know if this helps.

Best,
David

sarathgd

Thanks David this really worked.

One more question is - if I have to filter out one more dependency type like 'Depends" can I use same approach?

issueeLinks.type

.filter($.contains("Blocks","Depends"))

Unique() ??

David Niro

Hello @sarathgd ,

We just need to adjust the FILTER slightly. This should work:

issueLinks.type 
  .FILTER($ = "Blocks" OR $ = "Depends") 
    .UNIQUE()

Please let me know if it helps.

Best,
David

sarathgd

Thanks David for quick help here. Now the structure shows Blocks and Depends when ever there is any dependencies.

By any chance will there be any case like both Blocks and Depends applicable between any issues type? Can that be achieved like -

$="Blocks" AND $="Depends"?

If apply this logic, none of either Blocks or Depends are appearing in the structure.

Ana Cornejo

Hey friends! - fellow begginer Jira user here, I sue

Initiative (main project) ¬ Epic (Main workstream header) ¬ Stories ¬ then tasks.

Collaboration with other teams often involves them creating related stories and tasks in their respective Jira projects.

While I can link these tasks via issue linking, a critical limitation arises: I cannot establish dependencies between these linked tasks and my primary initiative's tasks, nor do they appear on my main project plan.

Is there a way I can achieve this on a formula?

Is it feasible to incorporate these external tasks as dependencies and visualize them within my project plan?

Thanks!

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud