Can I remove parent issue in custom structure view without removing/unlinking in actual structure

[Ramsha Deshmukh]

Hi,

I am trying to create some custom structure views for different projects, In the extender, I am selecting "relates" instead of "relate->" or "relate<-" and that pulls all the parent issues in the view. When I try to remove the parent issue using "X" button from the top bar, it unlinks the parent issue from the actual/main structure project folder.

How can I safely remove parent issues without removing/unlinking it from the main structure? 

[Egor Tasa [ALM Works] · Accepted solution]

Hi Ramsha,

I believe you would have to filter them out either through generator or transformation, but only if those parent issues are actually in a children's position in your structure. It is a bit unclear what is their actual position. Seeing the structure would allow me to provide more specific instruction.

Regards,
Egor

[Ramsha Deshmukh]

Thank you very much Egor, I will try filtering them out. Basically we have 5 level hierarchy in our instance - project folder->portfolio -> program-> projects->milestones->Subtaks ..If I am trying to custom a view at a project level it is pulling everything in that view which is linked to it for eg- program/portfolio from the top hierarchy. Apparently this was actually making the view more messier and killing the purpose of customizing. 

But i think adding a transformation  issuetype =! Program and portfolio should work 

thanks again 

[Ramsha Deshmukh]

Hi Egor,

Thank you again for the filter suggestion looks like there two things happening

(1) it just greys out that parents issue if I add it as transformation+filter and do not filter out from the view plus when I hover over the greyed issue I am still able to drill down to child issues under it.

(2) If I am adding a JQL query using the "automation" button it does not work at all. Can you guide me on what I am doing wrong?

Attaching both pictures for your reference

Please help!

Thanks!

[Egor Tasa [ALM Works]]

Hi Ramsha,

That's what I meant when I mentioned that issues would have to be in child positions. Issues cannot be completely hidden from Structure without their children, as this breaks the hierarchy. You can hide parent and its children if you restrict the filter to the level of the parent (by default filter applies to all levels and may keep children that pass it).

Sorry for missing your earlier comment, strange that it did not register in my email.

Regards,

Egor

[Ramsha Deshmukh]

Hi Egor

Thank you for immediate reply. Much appreciated!

Can you please explain what you mean by "....You can hide parent and its children if you restrict the filter to the level of the parent"

Here my entire goal is to remove parent issues from the custom structure view
In this particular instance, I want to remove the portfolio item ("DSI-30" is a portfolio item) and want to keep everything in the view from the program level and below.

Following is the hierarchy level we follow- 

 [Basically we have 5 level hierarchy in our instance = project folder->portfolio -> program-> projects->milestones->Subtaks ]

 For which I added a filter query issuetype =! portfolio . As a result, its just greys out and not remove from the view.

I think I restricted the filter at level of the parent but doesn't seems to be working :(

Not sure what I am missing 

[Egor Tasa [ALM Works]]

Here is an example, Ramsha,

Let's say we have a hierarchy 

X
-Y
--Z

And I filter Y out. If in the filter, I select to filter at All levels, I get

X
-Y
--Z

But if I select to filter at level 2 only, where Y is situated. Then I get only

X

You can change the filtering level if you double-click on existing generator filter, or edit your transformation via its dropdown. Is this explanation helpful?

Regards,
Egor

[Ramsha Deshmukh]

Thanks for the explanation Egor, I did select "current level" and tried to filter out the portfolio unfortunately,I still see portfolio (DSI-30) in the filtered view.  Per you above example I am trying to filter of X and just want to see "y" & "z"

[Egor Tasa [ALM Works]]

Hi Ramsha,

You cannot filter out parents, they will always be present if their children are passing the filter. One of the alternatives can be: create a different structure and insert issues in structure("Test Backlog Structure", "child of root") this will show you the second level of the first structure, which you can extend with the same extender you used in the first structure to get levels 2 and 3 only. 

Regards,
Egor

[Ramsha Deshmukh]

Thank you again for the diligent service Egor. In your alternative, do you mean that I should create a new structure and pull all subtasks and then add jql extender (issuetype != portfolio) and level = ‘manual’ and select 2,3 level ? 

Can you you please explain a lil further ? Pardon my naiveness, I am a beginner with jira structure setup 

I appreciate all the help :) 

[Egor Tasa [ALM Works]]

Hi Ramsha,

Sorry for being not clear. You'd have to create a new structure and use Automation+>Insert>JQL Query, with JQL issue in structure("Test Backlog Structure", "child of child of root"), this will bring in only program items. Then use the same extenders you have in original structure except for those responsible for bringing in portfolio and program items. Without seeing generators in your structure and links in your issues, I cannot tell which ones exactly are those extenders, but technically you can copy all extenders.

Regards,
Egor

[Ramsha Deshmukh]

A heartfelt THANKS to you! Looks like this alternative is working for my custom structure view. Finally, not seeing the portfolio in there :) . I thoroughly appreciate your help and patience 

Stay Safe! 

I am 

[Egor Tasa [ALM Works]]

Glad I could help!

[Brian Shields]

I have an extended question to this. Say I insert children as directed above but also want to  sort by the parent rank so that the children appear in the sort order of parent rank?

[Mario O.G]

Hi Brian,

Is there a chance you could clarify what you mean by 'directed above'?

Are the parent items present in the hierarchy?

If so, would the Sort by Rank be of any help here?

Automation > + > Sort > Rank

Cheers,

Mario Gomes
[ALM Works]