ALM Structure : Group by - Link Names

[Avi Bachar]

Hi 

This question relate to grouping in Structure

I have Epics in the structure (first level insert)

then I extend with 2 types of "links"

1. by epic link

2. by a specific link. ("GA Assessment" , just for the record)

I would like to see under the epic 2 groups one for each

how do I do that?

illustration:

Epic XYZ

   -- "EpicLink" (Group)

        --- Story A

        ----Story B

         --- Bug C

  --"GA Assessment" (Group)

         --- Story Z

         ---- Epic ABC

         ---- Bug B

[Avi Bachar]

Hi @Stepan Kholodov _ALM Works_ 

Thanks for the input

in this ticket

https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Structure-Group-by-Link-Type/qaq-p/1595389

With your permission I will continue in this thread cause the issue is different from the previous one.

So I followed your instructions:

OK, so I have done what you said because I have done such in the past 

BUT something strange happens 

The "label" as you called it is a formula:

This is the formula: 

WITH GA_EPICS_ABOVE_TREE = ARRAY#ancestors{if(issuetype="epic" and epictype="GA Assessment";key)}.COMPACT().FIRST()
:
WITH LINKED_GA_EPICS = issuelinks.FILTER(x -> x.type="GA Assessment Content" and x.destination=key).MAP(x -> x.source).COMPACT().JOIN()
:
WITH IS_GA_ASSESSMENT= SEARCH(GA_EPICS_ABOVE_TREE , LINKED_GA_EPICS )
:
WITH FolderName = if(IS_GA_ASSESSMENT;"GA Assessment";"Other")
:
FolderName 

what the formula does?

GA_EPICS_ABOVE_TREE - return the key of the Parent "GA Assessment" Epic above (if exists)

LINKED_GA_EPICS - returns all the keys of Epics linked to the current issue with "GA Assessment Content" link

IS_GA_ASSESSMENT - check if the Parent in the Structure is actually has a link of "GA Assessment Content" (otherwise it is "Other" kind of link)

Now here is the Strange Thing happening:

you see the "Formula" Column it has this code and as you can see it result with "GA Assessment" which is correct 

if I use it in Transformation, creating a Group in Transformation, again it works fine.

HOWEVER

The when I use the same formula in Automation Group

it does not work.

In this picture

you can see in Green that the result is correct, but in Red you can see the Automation Grouping with the same formula resulting bad.

P.S.
I keep the discussion here and not in email to support cause it might help others.

if this is too specific and you prefer support I will send.

10x

[Avi Bachar]

P.S.2:

this is the case where I didn't use Automation Group but Transformation Group

[Stepan Kholodov _ALM Works_]

Thank you @Avi Bachar

If I understand correctly, the formula works correctly but you get different results when using it for grouping by a generator and by a transformation. In this case, it's not obvious what could be the cause of it and we would need to investigate this matter. Please submit a support request at our portal and we'll go from there.

Best regards,
Stepan Kholodov
ALM Works

[Dave Rosenlund _Trundl_]

Just in case you need it, @Avi Bachar, here's a short URL to our support portal:

https://alm.works/support

Best,

-dave [ALM Works]

[Avi Bachar]

10x @Dave Rosenlund _Trundl_ 
can't sign up to the site getting errors

any way I sent email to support@almworks.com

[Dave Rosenlund _Trundl_]

Thanks, @Avi Bachar!  I was able to reproduce the problem and our IT team is on it.

I'm glad you knew about the email method :) 

---

UPDATE: Hi again, Avi. It turns out there's Jira Service Management (JSM) issue that probably resulted in this happening to you.

If you have previously created a JSM account on the support portal in question, JSM throws that error message — not one that says "An account with this email address already exists... etc."

The workaround is to send an email to the JSM support portal in question, as you did today, OR to select the "Forgot Password" option on the support portal login page.

I ran into the same problem you did when trying to replicate the issue myself. I used a Gmail address that I had apparently used once before to create a test support account on our system. :(