You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to have the rolled up grouped resource AND grouped columns at the same time. This seems like a completely natural extension of the resource view and surprised it was not already supported.
It would be implemented as simply as adding a resourceGroupField and a group: true to your resourceColumns definitions.
It would look like this:
Can't seem to implement this so I guess it's a feature request.
The text was updated successfully, but these errors were encountered:
aximuseng
changed the title
Timeline - Resource AND Column grouping
Timeline - Resource AND Column grouping [Feature Request]
Mar 31, 2020
acerix
changed the title
Timeline - Resource AND Column grouping [Feature Request]
Support resources grouped by resourceGroupField as well as being grouped by 'group: true'
Mar 31, 2020
acerix
changed the title
Support resources grouped by resourceGroupField as well as being grouped by 'group: true'
Grouping by resourceGroupField breaks when resources are also grouped with 'group: true'
Mar 31, 2020
Hello!
Is this feature still on the roadmap? I tried to replicate the view aximuseng described with the screenshot and would be very happy to accomplish this with the plugin. :)
Will this bug be addressed in one of the next releases?
Hello,
This bug is still relevant in FC 6. Are there any plans to fix it please? We have to do some "complicated" DOM manipulations to achieve this behavior.
I want to have the rolled up grouped resource AND grouped columns at the same time. This seems like a completely natural extension of the resource view and surprised it was not already supported.
It would be implemented as simply as adding a
resourceGroupField
and agroup: true
to yourresourceColumns
definitions.It would look like this:
Can't seem to implement this so I guess it's a feature request.
The text was updated successfully, but these errors were encountered: