We need to use quick transformation filters that behave as if they are connected with an "OR" instead of an "AND" clause. I realize doing that would be problematic, but there would be a simple workaround if it were possible to merely invert the effect of selecting the filter buttons. Specifically, when the button is deselected (the default state) the filter would be applied, and when selected the filter would be deactivated.

This could be implemented by providing a single checkbox in the edit screen for a quick filter that inverts the effect of the filter. So instead of not showing non-matching items, selecting the button would now show non-matching items. This may sound confusing at first, but only the creators of the filter buttons need to understand the logic. Most users would just see a button that says "include x" or something to that extent and know that selecting it shows "x" which was filtered out by default.

When such a filter is created, it would be written according to its default (button deselected) behavior so that it filters out the items that selecting the button are intended to show. However, it should be named according to its deactivated (button selected) behavior so that users know its effect is to include rather than hide certain items.

As an example, let's say that I have a number of possible statuses for each issue, and I want buttons for each status that when selected show all issues having that status. As it stands, the only options are (1) have the buttons filter out every other status besides the desired one or (2) design the buttons to hide all issues with a given status. The obvious problem with (1) is that selecting more than one button returns nothing. The problem with (2) is that it is cumbersome to select every single status that one wishes to hide, just to show one or two of them.

If it were possible to simply invert the effect of the "hide" buttons in method (2), then by default (when deselected) these filters would all be active, showing none of those statuses. The buttons would obviously be renamed as "show x" rather than "hide" so users know to select the desired subset of statuses, instead of the undesired subset.

It is a widely adopted practice to not share specific dates in long term planning and it would therefore be helpful if I could hide the dates/timeline in the gantt view.

The only option today is to zoom out but that is not practical as the feature-bars will become to small and the timeline is still visible but in years.

I want to be able to show how feature A is scheduled before Feature B and that it is dependent upon Feature C being completed without having to show when the features will be worked upon.

Simply hiding, or making the dates blank, will do just that.

I miss the "Send to Top" and "Send to Bottom" functionality that is in the context menu on Agile boards. I learned how to cut/paste to move tickets but that is a lot of clicks and scrolling for a common (for me) action.
I saw a comment from Igor in another suggestion to open a new panel with the same structure, and drag the ticket to the top/bottom of the new panel. I tried to do this and I got this error "Cannot move issues inside JQL query result."
I'm still feeling my way around structure so maybe I'm doing something wrong. I just really want to right-click->"Send to Top" :)
thanks!

Jira has a "issue filter subscription" feature, which runs a filter at a certain time of the day and email the user with the results. Structure could have a similar subscription feature tied to a particular structure's view, where a snapshot of that view would be taken at a certain time of the email and the results would be exported to excel and emailed to the user.

My company currently use structure to keep track of our day-to-day progress by manually exporting structures to excel at the same time each day. Automating the exporting would allow us to automate the remaining of the pipeline and remove any room for human error.

Ideally, when subscribing to a structure you would be able to not only choose a view (which determines the fields to be exported) but also any filters or transformations that are applied to that structure. So the act of subscribing would take a snapshot of all those settings, and then an "export to excel" would be run at a recurrent schedule and emailed to the user.

Hi! I am using version 4.6.5

When you select a ticket, the yellow "x items selected" box appears, and visually pushes the entire ticket list down so you visually "lose" the item you just clicked on.

To see the problem in action, scroll to the very bottom and select the circle for the very last ticket. Instantly, the ticket gets pushed downward and disappears, so you have to scroll down to see it again.

It's also a problem when I have some tickets selected, then do ctrl-A, ctrl-A to deselect all tickets. The yellow bar that was there goes away, and whatever ticket I was looking at jumps upward.

A minor complaint but it happens all the time. Would it be possible for the view to maintain the position of the bottom ticket, so the entire list doesn't scroll when the yellow box appears?

thanks!