When in structure view and clicking on the 'quick transformation' button, there are two quick filter: * Unresolved * Assigned to Me How can custom filters be added there? I would like to add some custom JQL / S-JQL filter there for easy access for my Project Manager.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Structure: How to add new filter to default filter list

Matthias Kannenberg

When in structure view and clicking on the 'quick transformation' button, there are two quick filter:

Unresolved
Assigned to Me

How can custom filters be added there? I would like to add some custom JQL / S-JQL filter there for easy access for my Project Manager.

Accepted answers

Eugene Sokhransky _ALM Works_

Hello Matthias,

At the moment there is no way to save such filters, but it's coming in the future version. However, there is a workaround - you can use the Perspectives feature, to generate a link, which will open the structure with all the transformations applied:

https://wiki.almworks.com/display/structure/Sharing+a+Perspective

The screenshot is not updated yet - in the new version you can find the share button on the right side of the main toolbar next to the Export.

I hope this helps.

Regards,

Eugene

ALM Works

All comments

Eugene Sokhransky _ALM Works_

Hello Matthias,

https://wiki.almworks.com/display/structure/Sharing+a+Perspective

The screenshot is not updated yet - in the new version you can find the share button on the right side of the main toolbar next to the Export.

I hope this helps.

Regards,

Eugene

ALM Works

Matthias Kannenberg

Great to hear that this is planed. We are currently evaluating Structure for our project and while it is great feature wise, we have some issues usability wise, where it is hard for a non-power user (like someone not able to write JQL queries) to use structure effectivly.. having selectable quick filter buttons would be a great help here.

(another thing we are missing is being able to quickly place issue in our folder structure because using drag&drop on a large structure is pretty cumbersome.. Ideally, there would be some simple folder selection, like the subcompontens plugin uses for component selection (https://marketplace-cdn.atlassian.com/files/images/cc64e3fd-f7de-4a68-ab7a-8d2a215ffad0.png), or at least a possibility to display all available folders in pin mode (in the issue view) to place the issue without scrolling through all the existing other issues)

Eugene Sokhransky _ALM Works_

Matthias, thanks a lot for your feedback. This makes perfect sense.

Regarding the first case - do they need to switch between the filters? If so, then the only solution would be to create several perspectives. If not - there is another option. You can add Structure gadget to the Dashboard and apply and additional filter there.

As for the second case - that is an interesting idea and there are a few different ways to approach it. Could you please provide some more details on the use of such a feature? Do you often need to do some sort of triaging and need to quickly put issues in different folders?

Also, have you checked the grouping functionality, which allows you to automatically group issues by different fields?

Matthias Kannenberg

Maybe I should explain our case a bit more in detail to make things clearer:
We basically separate our backlog in 2 parts:
An active backlog: these are issues which people are currently actively working on. Like writing concepts, doing estimation/refinement or waiting for sprint assignment.. basically issues targeted for for the next 3-5 sprints..
A passive backlog: These are issues in their first stages.. basically only ideas, rough concepts, client communication etc which are not relevant in the near future, but still important to be worked on..

Since this passive backlog easily grows to a size where it is not manageable by a kanban board, I decided to test structure, to structure all of our epic-story-subtask things into a higher level structure, like frontend->Component A->Subcomponent B, to enable my project manager to drill down and look at issues (basically a "okay, our next big thing will be to improve Subcomponent B, so let me see all issues and ideas which are relevant for subcomponent .

For this work, the Structure Plugin is perfect, because you can drill down and the perspectives give you a good overview of what is happening there (much better then using components and search)!

So we created our folder hierarchy and I added a synchronizer to add all epics and bugs and stories without an epic link. I also added automation expanders to expand the children of epics and stories.. And while this was hard to figure out at first, it works great now!

Now our use cases would be:

My Project Manager would like to hide all epics and stories which are not in the initial workflow stage any longer (are currently worked on, active backlog) to judge what issue next to move from passive to active backlog
My Project Manager would like to display only the epics, to export this list to excel to discuss in a client meeting (thanks for having the export to excel, huge plus!)

Now, these use cases are easy for someone who knows JQL and S-JQL, but for someone who doesn't, a simple button to click to do this filtering would be perfect. Your perspective workaround is okay for now, but I would need to provide my PM with an external link list, which kind of feels not as polished of an experience as I would like it to be, if you know what I mean (using structure was my proposal and I have to convince my team)..

For my second case, it's quite simple: If I create a new Epic, I want to place this immediately into our existing folder structure. The current workflow to do this would be

Create the Epic
Go into the Structure View and search for the created epic
Use Drag&drop or cut&paste to move this into the folder I want

As our folder structure is very important to us for keeping an overview, this would be a mandatory step for every epic creation (or bug if it is not part of an epic). Also, the mini structure view in the issue details screen is not really helpful at this point, because scrolling through a larger list of folders and issues is hard enough in the structure view, but next to impossible with the limited screen size in the issue details... The mini structure view in the issue details is great for viewing of the placement of the issue, but not really feasible for any editing purposes.

So what we would need (best case) would a simple button in the issue create screen the user can click, look at the existing folder structure (without any other epics, stories etc.) and simply select one folder. Making this mandatory would be a bonus. This way I can assure that every newly created epic would be properly categorized.

A much easier to implement workaround be to have a check box in pin mode to display all folders anyway. This way, at least the sorting process would be a lot easier because a user could

Pin the issue he wants to move
check to display all folders anyway
Easily navigate through the folder structure only which is a much smaller structure then having all other issues there

This would in my opinion greatly increase user experience (at least in the case how we are using structure).

I hope this clarifies our usecases a bit more. Thank you for your great support!

Sathish Kumar_yp5d2j

How do you create a filter to pull data via external plugin ??. Any idea on this ??

Vlad L.

Vlad[ALM Works]

Hi Sathish,

Thanks for posting.

Can you provide a bit more information on what you're trying to accomplish, please?

I look forward to assisting you.

Vlad

ALM Works

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software

structure

addon-com.almworks.jira.structure