# Vote for User Specific Roll-Ups

**URL:** <https://community.glideapps.com/t/vote-for-user-specific-roll-ups/16517>\
**Category:** Feature Requests\
**Created:** [September 29, 2020, 4:13pm UTC](https://community.glideapps.com/t/vote-for-user-specific-roll-ups/16517 "2020-09-29T16:13:00Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![Deena](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/deena/32/9877_2.png) [@Deena](https://community.glideapps.com/u/Deena)\
**Post date:** [September 29, 2020, 4:39pm UTC](https://community.glideapps.com/t/vote-for-user-specific-roll-ups/16517/21 "2020-09-29T16:39:02Z")

</div>

Please don’t make me repeat my ted talk about how there should be a single source for feature requests and the app isn’t cutting it. Deep linking helps? Let’s see where we get with this one in the next 48 hours because I just really want to know who does NOT need/want this…I mean, just ask me if I want two arms, two legs, ten fingers and toes…Yes, and I want user specific ROLL UPS too. (And my background screen during loading). lol

---

<div class="post-metadata">

**Author:** ![S\_C](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/s_c/32/12766_2.png) [@S\_C](https://community.glideapps.com/u/S_C)\
**Post date:** [September 29, 2020, 4:39pm UTC](https://community.glideapps.com/t/vote-for-user-specific-roll-ups/16517/22 "2020-09-29T16:39:55Z")

</div>

> [@Deena](#):
>
> my ted talk

You go girl! 😄

---

<div class="post-metadata">

**Author:** ![Lucas\_Pires](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/lucas_pires/32/64863_2.png) [@Lucas\_Pires](https://community.glideapps.com/u/Lucas_Pires)\
**Post date:** [September 29, 2020, 4:42pm UTC](https://community.glideapps.com/t/vote-for-user-specific-roll-ups/16517/23 "2020-09-29T16:42:26Z")

</div>

> [@Deena](#):
>
> my ted talk

![](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/2X/8/82681ea988d6473a84fe8667ecb3f42d630f3d0b.gif "High Five Great Job GIF by Dogtopia - Find & Share on GIPHY")

---

<div class="post-metadata">

**Author:** ![S\_C](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/s_c/32/12766_2.png) [@S\_C](https://community.glideapps.com/u/S_C)\
**Post date:** [September 29, 2020, 4:47pm UTC](https://community.glideapps.com/t/vote-for-user-specific-roll-ups/16517/24 "2020-09-29T16:47:33Z")

</div>

Look at this example:

> **[Feature Requests](https://features.staging.glideapp.io/dl/ewAiAHQAIgA6ADAALAAiAHMAIgA6ACIAYwBsAGEAcwBzAC0ARgBlAGEAdAB1AHIAZQBzACIALAAiAHIAIgA6ACIAcABTADkAcAA2AG8ATgA1AFQAVgBhAG8AegBRAC8AMQBrAC8ANABuAFAAdwAiACwAIgBuACIAOgAiAEwAaQBrAGUAIABjAG8AdQBuAHQAIgB9AA==)**
>
> Feature requests for Glide Apps

This one also needs the same feature. 6 votes wasted on a use case rather than an actual backend feature.

---

<div class="post-metadata">

**Author:** ![Deena](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/deena/32/9877_2.png) [@Deena](https://community.glideapps.com/u/Deena)\
**Post date:** [September 29, 2020, 4:49pm UTC](https://community.glideapps.com/t/vote-for-user-specific-roll-ups/16517/25 "2020-09-29T16:49:26Z")

</div>

How about 5 votes to not have to rebuild tabs and forms? BTW, really not piling on here against the Glide team or anything…I just think the feature requests process is not effective and needs to be revamped. Deep linking isn’t going to fix it. Even if use case needs to be submitted (totally fair), just putting the form and everything here in the community where people are like 1000x more engaged than with the features request app makes much more sense.

> [@Critical Features that will save countless hours of development - Link to Tab Action + Reuse Forms](https://community.glideapps.com/t/critical-features-that-will-save-countless-hours-of-development-link-to-tab-action-reuse-forms/13406/6):
>
> Please vote for the ability to link new tabs to existing screens (meaning screens that are existing tabs with their layout already set; not just to sheets, which we can already do, but then we have to do all the layout work).

---

<div class="post-metadata">

**Author:** ![Lucas\_Pires](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/lucas_pires/32/64863_2.png) [@Lucas\_Pires](https://community.glideapps.com/u/Lucas_Pires)\
**Post date:** [September 29, 2020, 4:55pm UTC](https://community.glideapps.com/t/vote-for-user-specific-roll-ups/16517/26 "2020-09-29T16:55:18Z")

</div>

Yeah, I understand you. I try always to think in both sides… maybe what’s easy to me, it’s not easy for them. Vice versa.

---

<div class="post-metadata">

**Author:** ![Deena](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/deena/32/9877_2.png) [@Deena](https://community.glideapps.com/u/Deena)\
**Post date:** [September 29, 2020, 4:56pm UTC](https://community.glideapps.com/t/vote-for-user-specific-roll-ups/16517/27 "2020-09-29T16:56:59Z")

</div>

Agreed, but in the end if it’s not effective it’s good for no one…I am personally happy to do it either way, and I see some of us cooperating as we’re asked to do _using the features app_ but you see that there is a huge disparity in the number of threads regarding new features than actually get translated to “votes”…but I’m totally with you @Lucas_Pires, I want to be helpful and cooperative.

---

<div class="post-metadata">

**Author:** ![Manan\_Mehta](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/manan_mehta/32/13957_2.png) [@Manan\_Mehta](https://community.glideapps.com/u/Manan_Mehta)\
**Post date:** [September 29, 2020, 5:01pm UTC](https://community.glideapps.com/t/vote-for-user-specific-roll-ups/16517/28 "2020-09-29T17:01:50Z")

</div>

The votes for this one and the rollup should be merged and added. It’s the same thing.

---

<div class="post-metadata">

**Author:** ![Lucas\_Pires](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/lucas_pires/32/64863_2.png) [@Lucas\_Pires](https://community.glideapps.com/u/Lucas_Pires)\
**Post date:** [September 29, 2020, 5:07pm UTC](https://community.glideapps.com/t/vote-for-user-specific-roll-ups/16517/29 "2020-09-29T17:07:09Z")

</div>

Agreed. Actually everything sums up in “we wanna count also user-specific columns, plz”

---

<div class="post-metadata">

**Author:** ![Rasha](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rasha/32/4585_2.png) [@Rasha](https://community.glideapps.com/u/Rasha)\
**Post date:** [September 29, 2020, 5:53pm UTC](https://community.glideapps.com/t/vote-for-user-specific-roll-ups/16517/30 "2020-09-29T17:53:29Z")

</div>

@S_C , @Deena , @Lucas_Pires this seems like a fun place to plop this post down.  
What’s the middle ground? I know for fact the Glide team is super attentive to the feature request app.

> [@Feature Requests Q](https://community.glideapps.com/t/feature-requests-q/13615/19):
>
> Hi @JackVaughan - this looks great. Some suggestions/observations, if I may: Shipped tab - A date would be a plus. Add a “planned” tab? 5 shipped features with 1 vote total - are these added after being shipped? Can’t imagine that’s indicative of high value/urgency. For feature requests and tracking, we’re in need of a single source of truth. A decent number of posts regularly get tagged [#feature-requests](https://community.glideapps.com/c/feature-requests/9) and I suspect the existence of this app is unknown to most folks on the forum. Absent o…

---

<div class="post-metadata">

**Author:** ![Deena](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/deena/32/9877_2.png) [@Deena](https://community.glideapps.com/u/Deena)\
**Post date:** [September 29, 2020, 6:08pm UTC](https://community.glideapps.com/t/vote-for-user-specific-roll-ups/16517/31 "2020-09-29T18:08:16Z")

</div>

Agreed, it is about middle ground but only if there is some synthesis between features request here and in the app. But my take, based on conversations with @JackVaughan is that the app is more effective. That’s why it is bothersome that the app is less used than the community. But I could be totally wrong and happy to stand corrected. Generally, I think we are all grateful just to have a voice and have such an amazing team at Glide to hear us.

Case in point though:

> [@Feature Request Process Confusion](https://community.glideapps.com/t/feature-request-process-confusion/16522):
>
> I’m confused on the best place to post feature request. It’s confusing having a feature request app AND a feature request topic in the forum. I don’t know if I should post my requests here or in the app or both? Glide, can you give us direction on the best pathway to getting our feature requests published?

@_eric Your message was very timely. I am cross-referencing here to agree with you.

---

<div class="post-metadata">

**Author:** ![S\_C](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/s_c/32/12766_2.png) [@S\_C](https://community.glideapps.com/u/S_C)\
**Post date:** [September 29, 2020, 6:26pm UTC](https://community.glideapps.com/t/vote-for-user-specific-roll-ups/16517/32 "2020-09-29T18:26:28Z")

</div>

We don’t know the priorities of Glide team. Therefore, all we can do is to submit feature requests, vote, and “whine” here. It would be great to see what they are working on so that we can build and request accordingly. Some of our requests are redundant at times but we can’t hold back as we don’t know if something is already getting a priority or not.

I had suggested a middle ground a while back. No official response.

> [@Glide feature request wait time and status](https://community.glideapps.com/t/glide-feature-request-wait-time-and-status/12038):
>
> Does anyone know after how many votes Glide team puts a feature on their task list? It would be great if there was a status that could tell users if Glide team is ‘Waiting for enough votes’, ‘Started Working’, ‘In Progress’, or ‘Considered but rejected at this time’ kind of status for Gliders. Thoughts?

Anyhow, this is norm among Glide’s peers. For example, Adalo has such a feature. [Feature Requests | Adalo](https://ideas.adalo.com/feature-requests)

Hopefully, this post is considered a part of constructive criticism by Glide and not taken against me.

---

<div class="post-metadata">

**Author:** ![Rasha](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rasha/32/4585_2.png) [@Rasha](https://community.glideapps.com/u/Rasha)\
**Post date:** [September 29, 2020, 6:29pm UTC](https://community.glideapps.com/t/vote-for-user-specific-roll-ups/16517/33 "2020-09-29T18:29:22Z")

</div>

It’s a tough solve. I suspect it’s difficult for **both sides.** But frustration is mounting so hopefully this will be addressed.

---

<div class="post-metadata">

**Author:** ![Les\_Henderson](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/les_henderson/32/1142_2.png) [@Les\_Henderson](https://community.glideapps.com/u/Les_Henderson)\
**Post date:** [September 29, 2020, 7:09pm UTC](https://community.glideapps.com/t/vote-for-user-specific-roll-ups/16517/34 "2020-09-29T19:09:31Z")

</div>

Perhaps a multiple of votes could also given by the experts and others at some point as they climb the forum ranks.

Elite contributors with numerous apps and brilliance would get 10 votes per vote while qualified Experts could outright insist that the Glide team work weekends on requested features. Ha.

As for sharing their deep secrets, I have to think they don’t want to give up any first strike advantage. Google Tables will be a hit but always a clone of Airtable. You want to at least retain bragging rights for after you get crushed or bought out.

---

<div class="post-metadata">

**Author:** ![Rasha](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rasha/32/4585_2.png) [@Rasha](https://community.glideapps.com/u/Rasha)\
**Post date:** [September 29, 2020, 7:27pm UTC](https://community.glideapps.com/t/vote-for-user-specific-roll-ups/16517/35 "2020-09-29T19:27:24Z")

</div>

> [@Les\_Henderson](#):
>
> Perhaps a multiple of votes could also given by the experts and others at some point as they climb the forum ranks.

weighted voting? Those experiments don’t usually work out really well.

---

<div class="post-metadata">

**Author:** ![Les\_Henderson](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/les_henderson/32/1142_2.png) [@Les\_Henderson](https://community.glideapps.com/u/Les_Henderson)\
**Post date:** [September 29, 2020, 7:34pm UTC](https://community.glideapps.com/t/vote-for-user-specific-roll-ups/16517/36 "2020-09-29T19:34:59Z")

</div>

How can you say that?

“One Ring to Rule Them All” turned into a blockbuster franchise. 😄

What could possibly go wrong by giving a select few more voting rights than the populace in a general election? Oh, never mind. As I slap myself.

---

<div class="post-metadata">

**Author:** ![Lucas\_Pires](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/lucas_pires/32/64863_2.png) [@Lucas\_Pires](https://community.glideapps.com/u/Lucas_Pires)\
**Post date:** [September 29, 2020, 7:42pm UTC](https://community.glideapps.com/t/vote-for-user-specific-roll-ups/16517/37 "2020-09-29T19:42:01Z")

</div>

> [@Les\_Henderson](#):
>
> Oh, never mind. As I slap myself.

Lol

---

<div class="post-metadata">

**Author:** ![Lucas\_Pires](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/lucas_pires/32/64863_2.png) [@Lucas\_Pires](https://community.glideapps.com/u/Lucas_Pires)\
**Post date:** [September 29, 2020, 7:46pm UTC](https://community.glideapps.com/t/vote-for-user-specific-roll-ups/16517/38 "2020-09-29T19:46:20Z")

</div>

> [@Glide feature request wait time and status](https://community.glideapps.com/t/glide-feature-request-wait-time-and-status/12038/1):
>
> It would be great if there was a status that could tell users if Glide team is ‘Waiting for enough votes’, ‘Started Working’, ‘In Progress’, or ‘Considered but rejected at this time’ kind of status for Gliders.

For sure! My anxiety would thank for that 😂

---

<div class="post-metadata">

**Author:** ![S\_C](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/s_c/32/12766_2.png) [@S\_C](https://community.glideapps.com/u/S_C)\
**Post date:** [September 29, 2020, 7:57pm UTC](https://community.glideapps.com/t/vote-for-user-specific-roll-ups/16517/39 "2020-09-29T19:57:10Z")

</div>

It won’t just be helpful for us but for Glide as well - improved customer satisfaction and loyalty

---

<div class="post-metadata">

**Author:** ![JackVaughan](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jackvaughan/32/49023_2.png) [@JackVaughan](https://community.glideapps.com/u/JackVaughan)\
**Post date:** [September 30, 2020, 10:29am UTC](https://community.glideapps.com/t/vote-for-user-specific-roll-ups/16517/40 "2020-09-30T10:29:21Z")

</div>

I appreciate the separation between the app and this forum isn’t ideal. At the moment, we don’t have the capacity to work on a solution to this but we hear you. We appreciate you guys sharing links to features in here.

We’ve chatted recently about what we’re working on in a [community meetup](https://community.glideapps.com/t/glide-community-meetup-this-thursday/14586/41). But a public roadmap is still not something we’re likely to do soon.

[Previous page](https://community.glideapps.com/t/vote-for-user-specific-roll-ups/16517.md?page=1)
