Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

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,463,576
Community Members
 
Community Events
176
Community Groups

Strange Query: Checking Stories sub-tasks without extender

Hey everyone, need some help again.

If i had a structure showing only features and didn't want to use the extend function as it would slow the structure down and show too much information but wanted to do some checks on the lower hierarchy i know i can use epicstories.FILTER etc

Now lets say i have this set up

Feature > Story > Sub-Task

i want a structure at feature level but i want to check a Sub Task of a story, i have tried the following

Epicstories.FILTER($.issuetype = "story" and query = 1).key

where query is a Query Match of the following;

issueFunction in parentsOf ("issuetype = Sub-Task and component = COMP1")

So the key showed should be those of any story where is has a subtask with a component of COMP1

This doesnt seem to be working, and i am not sure if its possible? is there a work around without having to use extenders?

Love a head scratcher 

2 answers

1 accepted

0 votes
Answer accepted

Hello  @Ian Porter

Yulia from ALM Works here!

I have tested the last formula you have provided on Structure v.7.4,  and it works! Well done!!

So I have a few questions for you:

1. Which version of Structure are you currently using? 

  • We have added a lot of additional Formula functionality starting with version 7.0. The ability to reference issues that are not part of the structure in a formula is one of them.

2. What issue link type do you use to link features to the story?

Looking forward to hearing from you.

Best regards
Yulia Barbash
www.almworks.com

Hey, 

We are using v7.2.0 and the formula is not working, is this the reason?

Also our stories are Issues in Epics so parent child link

also which code did you get to work, i have had some success with my first one but it was pulling back all stories and not doing the second filter

Thanks Yulia, with a little working out we know have this working and for anyone else, our final code is;

 

with SubTaskExist = 
epicstories.FILTER($.issuetype = "story"
and
$.subtasks.FILTER($.components = "COMP1"))
.key:

with gstat =
epicstories.FILTER($.labels = "COMP1"
and
$.issuetype = "Task").key:

with TaskExist = if(epicstories.FILTER($.labels = "COMP1"
and
$.issuetype = "Task"
and
($.status = "Done" or $.status = "Ready To Accept" ))
.key;
"Good"):

WITH addBackground(value, color) = """{panel:bgColor=$color|borderWidth=0px}$value{panel}""":

If(Issuetype = "feature";
if( TaskExist = "Good";
"{color:green} *Pass* {color}";
if( TaskExist != "Good";
If( gstat = undefined and SubTaskExist= undefined;
"{color:gray} _No Task_ {color}";
If( gstat = undefined and SubTaskExist != undefined;
addBackground("Missing", "#FF4C33");
addBackground(gstat, "#FF4C33") )))))

Hello @Ian Porter

That is an amazing job!

Thank you for sharing it.

In case you have any questions, you are also always welcome to reach us directly by emailing support@almworks.com.

Best regards
Yulia Barbash

i maybe getting closer using this, but not quite got the code right;

epicstories.FILTER($.issuetype = "story" and $.subtasks.FILTER($.components = "COMP1")).key

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events