Enhancement Request – Query Builder

  • I like the functionality of Query Builder for defining repeatable admin queries. But….

    It seems to store queries per user. If I save a query, others in my team can’t reference it.

    I can see the argument for private queries but I can also argue for public, saved queries.

    Is this possible? Practical? This is not an urgent requirement.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Passionate Programmer Peter

    (@peterschulznl)

    Hi Charles,

    Good te hear from you! Good to have you back! ??

    I can see the need for public queries and teh need to share them. What would be your preferred workflow? Always save as private and explicitly save as public? Keep them both? Or only one? Allow others to update? What do you think/need?

    Hope you don’t mind I’ll give it a lower priority? I’m currently working on version 5. A huge update, the largest so far. Hope to release next month, with some really great stuff!

    Thanks for you input as always… ??

    Best regards,
    Peter

    Thread Starter charlesgodwin

    (@charlesgodwin)

    Peter; This is definitely low priority.

    I think you treat them the same as other backend resources. All queries are available to those with admin privileges. I guess you can call that ‘public’.

    Charles

    Plugin Author Passionate Programmer Peter

    (@peterschulznl)

    I’ll see what I can do Charles…

    Have a great weekend,
    Peter

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Enhancement Request – Query Builder’ is closed to new replies.