Structure page not working
The topic display with unavailable item for some users
how to fix?
Hi Chatchai,
The most probable cause for this issue is that the users in question do not have Jira access to the issues marked as Unavailable, but can still see their children in the Software structure. Providing access to these users or reformulating the structure (how - depends on the usecase) would be needed to remove Unavailable items, but it may not be necessary if the users only need to access children items here.
Regards,
Egor Tasa
ALM Works
Hi Egor,
Is there a way where we can hide the "unavailable items" in Structures view?
Thanks,
Poojaa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Poojaa,
Hiding Unavailable items means hiding their children. If you can hide those, then you will hide Unavailable items as well. Note though that in some cases Unavailable items are shown as such only to some users, while others see the actual issues there.
Regards,
Egor
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Egor,
Let me quickly brief you the scenario which I'm trying to implement.
I've created a structure that displays all the issues and grouped by project, displaying all projects and issues underneath it. This structure will be global and all users can view this. The structure displays the projects for which the user has access to and remaining projects are displayed as "Unavailable Items".
My requirement is, the user should only see his project data and unavailable items should not be visible.
Is this something feasible?
Thanks,
Poojaa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Poojaa,
The user must be able to see something under those unavailable items or they would not be displayed. You should be able to use transformation filter S-JQL: ancestorOrself not in item(* , Unavailable) to hide the whole branch.
Regards,
Egor
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Egor, I was able to debug based on your input.
Am also grouping the structure based on Teams. So, it's like issues --> grouped by Teams --> grouped by project. If 2 projects have same value for this Teams field then it get's displayed as "Unavailable item". Here, Teams is a custom single select field.
I've tried using s-jql query that you provided but still, I'm able to view those - PFB screenshot.
Thanks,
Poojaa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry, Poojaa, I wrote too soon,
S-JQL or JQL will not help us here as Unavailable Item cannot be referenced. But it seems you have empty folders under it, so let's try not (not item(issue) and leaf) - it will remove all empty non-issues.
Regards,
Egor
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Egor.
I tweaked the query little bit: not (not item(issue) and leaf) and leaf
This worked for me. But I was able to make this work only in Quick Transformation. The same query on putting under Automation, doesn't work. Any thoughts?
Regards,
Poojaa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Poojaa,
This is because grouping is happening after filtering in Automation, but Transformations are applied after all generators have run. We plan to eventually make possible to change the order of generators, but no dates yet.
Regards,
Egor
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.