Need help with editing a Structure automation

[Aisha M]

Hi,

I have a jira structure which is returning a lotttt of issues, due to which it does not load properly. Though it takes close to 5min for it to display the issues, clicking on AUTOMATION makes the structure load & not return anything. Due to which, we are unable to edit the structure query and minimize this load problem.

Is there any other way to edit the structure ?? This is completely interfering with the Jira performance

[Tuncay Senturk · Accepted solution]

Hi @Aisha M 

Hope you're well.

I'd like to help but I am not good at Structure. However, if you clarify, I'd try to help, for sure!

Best

[Aisha M]

Hellooo, glad to hear back from you @Tuncay Senturk  :):)

Actually, I was finally able to edit the Structure query . .  I need help with my JQL actually, seem to be having trouble with refining the query, hence thought you would be the best person to help :)

[Tuncay Senturk]

I'd be happy to help.

Yes, adding due date restriction is possible and it would definitely filter out the results.

So, if you're using Jira's duedate field, you can add the below statement to return only issues that have duedate of year 2022.

AND duedate > startOfYear()

However, if you want to exclude the issues which have duedate in one year (365 days) then you can use this query

AND duedate > startOfDay(-365)

I hope it helps

[Aisha M]

Thank you @Tuncay Senturk , Let me try that. 
I was planning on using something like

issuetype = Container AND statusCategory != Done AND updated >= -30d

This still have a huge lot of issues . . 

[Tuncay Senturk]

No worries @Aisha M 

I usually use the resolution field to filter out old issues, so it is a good idea to add

AND resolution is EMPTY

This will make your query only unresolved issues, however you might want to return recently resolved issues, in that case, you can use the resolutiondate field. As an example, if you wish to return the issues which are either not resolved or resolved within 100 days, below is the query (please be aware of the correct usage of parenthesis)

AND (resolution is EMPTY OR resolutiondate > startOfDay(-100))

 I hope it helps!

[Aisha M]

@Tuncay Senturk Awesome :):) Thank you . .  this was helpful.

Is it possible to exclude Epics that are resolved 15weeks ago ?

[Tuncay Senturk]

I think I could not get it.

If you add issuetype = 'Container' to the query, it automatically excludes all Epic issue types no matter when they were resolved.

[Aisha M]

@Tuncay Senturk Actually in Structure you can add levels (like child of the issue and etc) . . So here, based on the sorter and inserter (JQL)  it displays the issues . . 
so, here it’s displays all the containers and it’s child (portfolio epic and then it’s child Epic) So basically three levels . . 
I’m looking forward to clean up this list by excluding epics that are resolved 15weeks ago 

[Tuncay Senturk]

Hmm, I see!

As I mentioned, I'm not good at Structure. You need an if statement here, like if it is Epic then it should be resolved in 15weeks. I don't think you can achieve that in a single JQL (sorry)

[Dionathan Lopes {ALM Works}]

Hi All, 

Dionathan with ALM Works here. 

@Aisha M in this case, you could try adding a Filter Generator or a Quick Filter Transformation with the following S-JQL query and let me know if it does help:

subIssueOrIssue not in [issuetype = "Epic" and resolved < 15w]

PS: A child issue can’t be displayed in a structure without its parent (otherwise structure’s hierarchy would be broken) so when using quick transformations, instead of removing a non-matching parent, it's greyed out.

If any other questions, let me know 

Best Regards,
Dionathan Lopes
www.almworks.com 

[Aisha M]

@Dionathan Lopes {ALM Works}  Thank for the comment. The Structure is for the Container issue type . .  But it is configured in a way that it displays all of its child.

Container > Portfolio Epic > Program Epic > Feature(Epic)

Altering the inserter to look for the Epics messes up the Structure.

I tried your suggestion & getting the below prompt:

You are about to create a generator. It will be impossible to add it to the structure because of the automation installed: Cannot add generators to dynamic content. You can drag-and-drop the item to a different location

[Dionathan Lopes {ALM Works}]

Hi @Aisha M 

It could be happening due to "where" you are adding the Filter Generator.

Generators' scope is defined by their position within the structure, so you may need to place the generator at the top, and it will impact the entire structure. 

You can find more information and instructions about it Here 

One more thing, you mentioned that your hierarchy is "Container > Portfolio Epic > Program Epic > Feature(Epic)", so you may need to specify which Epic you want to filter out on the S-JQL code:

subIssueOrIssue not in [issuetype = "Epic" and resolved < 15w]

Let me know if it does help.

Best Regards,
Dionathan Lopes

[Aisha M]

@Dionathan Lopes {ALM Works}  Thank you . . Actually, Specifying the Epic shouldn't be a problem, coz its referred to as Feature.

[Dionathan Lopes {ALM Works}]

You are welcome, @Aisha M 

You could try adding it as the first row of your Structure and let me know how it goes.

"Actually, Specifying the Epic shouldn't be a problem, coz its referred to as Feature."

Right, in this case, you just need to make sure to update the S-JQL code accordingly.

If any other questions, I'm happy to help.

Best Regards,
Dionathan Lopes

[Aisha M]

@Dionathan Lopes {ALM Works}  Thank you for helping out. I have one issue,

I tried clicking the + icon on the automation and selected the Filter option. But when I add the SJQL, I get the same prompt - You are about to create a generator. It will be impossible to add it to the structure because of the automation installed: Cannot add generators to dynamic content. You can drag-and-drop the item to a different location  & the filter doesn't get added to the generator after i acknowledge the prompt. 

I tried checking the help link you provided, but nothing specifies how to add the Filter to the top of the list. Do I need to make some modifications while adding the filter ? 

[Dionathan Lopes {ALM Works}]

Hi @Aisha M 

It would be great if we have a quick screen share to check what could be happening, what do you think?

If you agree, please contact us directly at support.almworks.com and I will be happy to help you.

Looking forward to hearing from you.

Best Regards,
Dionathan Lopes

[Aisha M]

@Dionathan Lopes {ALM Works}  Thank you for helping out with the issue.

Unfortunately, due to compliance , I cannot share screenshots.

But I can list out the steps I followed

1) Click Automation

2) Select - Filter

3) Select S-JQL 

4) Provided the query in the prompt box

Is this the right sequence, or do I need to modify the levels ?

[Dionathan Lopes {ALM Works}]

Hi @Aisha M 

Thank you for letting me know, and for your time and patience on this matter.

The Steps you are following are correct, we just need to place the Filter generator in the right place. Here are the steps:

1) Click on the First row of your structure (the one with your Structure Name). In the below example, it will be the "Demo Structure" row:

Then follow the steps you have mentioned. It should place the filter on the top of your Structure and you should not see that message again.

Please let me know how it goes.

Best Regards,
Dionathan Lopes

[Aisha M]

@Dionathan Lopes {ALM Works}  Works !!!!!! Thank you so much for helping out . . Really appreciate the help !

@Tuncay Senturk  Thank you once again for looking into my question and helping me out :):) 

[Dionathan Lopes {ALM Works}]

@Aisha M 

You are always welcome! I'm glad I could help.

Best Regards,
Dionathan Lopes

[Dionathan Lopes {ALM Works} · Accepted solution]

Hello @Aisha M 

Dionathan with ALM Works here. Hope you are doing great.

We would need some more information to understand better your use case.

If possible, please contact us directly at support.almworks.com and we'll take a detailed look at your set-up.

Best Regards,
Dionathan L
www.almworks.com 

[Aisha M]

Hi @Dionathan Lopes {ALM Works} , Thank you for the comment. We have already assessed the problem with the ALM support. They mentioned the only way is to edit the structure & alter the query, as the structure was returning a huge number of results. 

[Aisha M]

Hi @Tuncay Senturk Hope you are well :):) Can you please help me out with a query to help refine my structure