I would like to create a Structure of Structures for structure navigation, whereby specific child elements allow you open the referenced structure. I have many structures that contain the same data, just displayed differently for different user groups.

The use case is in essence:
Parent - Folder (a name listing a group of similar or related structures)
Child - New Structure Link - simply a mechanism to either open or navigate to the referenced structure - includes description.

Implementation:
Is it possible to add a new Structure element into the "Add" Dropdown called "New Structure Link". (i.e. New Issue, New Folder, New Memo, New Structure Link) allows the building of an index structure.

First iteration could allow manual creation only, but with use of metadata in future could allow auto generation.

Allow Gantt bars to consider an issue's "Remaining Estimate" value when computing the resource usage. Currently, we have issues with a start and end date, and are using time tracking which keeps track of "Remaining Estimate".

But the Gantt bars are allocating by default, the value of "1.0". So the quadrant for resource usage is computing a total resource need that is assuming everyone is allocated 1 full day for every assignment. If an assignee has 8 things going on in a given day, it's reporting 64 hours need by that person per day! If instead the resource usage would use "remaining estimate" as the numerator, then the total need for the person in a given day would be leveled more logically.

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.

For users who are not well versed in JQL, it would be nice to have the ability to add Jira filters in a way that is comparable to Jira's "Basic" search feature, rather than by inputting the JQL manually.

Perhaps, on the dialog that is displayed when the user adds a JQL insert automation for the first time, we could have a "Basic" link that converts the query to the basic view, just like Jira's issue navigator. Then, all the JQL would be converted into a series of UI inputs (user pickers, drop-downs, etc).

In addition to this, it would be nice to be able to use this "Basic" feature when specifying "issuekey = ..." conditions. Jira's basic search does not allow you to use these conditions - it forces you to switch to the "Advanced" (JQL) search. This would be helpful for us because we find that we often use structure to display a list of linked issues to one specific issue key. Having this ability would allow the user viewing the structure to simply pick another issue key in a dynamic drop-down, updating the structure. :)

Hi Almworks,

We need very simple capacity management in Structure. For this to work we have almost everything:
- ability to aggregate from tasks to Epics (and higher levels) for remaining estimates and spent
- Top-level group can act as a teams, for which we can defined daily capacity and planned work ratio (using field with CASE() for example)

What we lack is we can't calculate remaining capacity considering resources availability, mostly because we can't use production calendars (similar to NETWORKDAYS() of Excel) If we had this ability we could automatically build Structure view which shows current remaining estimates vs. remaining capacity (until a release) which is huge in terms of giving product management big picture of the release.

We understand maybe it was intended to use Gantt to achieve this, missing ability to work calendars is so sad, it could allow to completely through out Excels, use Structure for 'what if' analysis, etc.