Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,364,119
Community Members
 
Community Events
168
Community Groups

Dependencies between different projects

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.

 

 

1 answer

1 accepted

0 votes
Answer accepted

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

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() ??

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

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.

Hi @sarathgd ,

You are very welcome.  

The formula should do, and does in my testing, the following:

IF there is at least one "blocks" link and no "depends" link:  "Blocks"
IF there is no "blocks" link and at least one "depends" link:  "Depends"
IF there is at least one "blocks" link and at least one "depends" link:  "Blocks, Depends"
IF there are no "blocks" and no "depends" link: (blank)
(for all four, ignore other issue link types)

Is it doing something different for you?

If it is doing something different, you will want to contact our support team directly to review the behavior and identify potential causes.  You can reach us via email support@almworks.com or through our customer portal support.almworks.com.

If it is doing what I describe above, then we will need to review your use case in more detail to understand all of the variables and end goal.  Here too it may be best to contact our support team directly.

Best Regards,
David

Thanks David for quick reply, I'm looking for logic if issue have both blocks and Depends.

 

IF there is at least one "blocks" link and at least one "depends" link:  "Blocks, Depends"

Hello @sarathgd ,

This should work:

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

IF link_filter.SIZE()=2:
link_filter

It looks at the number of elements the original formula returns and if it is = 2, then it returns the values.

Best,
David

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events