Date   

moderated Re: Feature request/enhancement -- Enlarge the vertical size of the "Your Groups" pull-down menu #suggestion

Gerald Boutin <groupsio@...>
 

On Fri, Jan 3, 2020 at 08:04 AM, Sandi D wrote:
On Fri, Jan 3, 2020 at 05:09 AM, Samuel Murray wrote:
the groups in the pull-down menu aren't in any logical order,
The order they appear for me seems to based on the historical order of my last visits. The most recent one I visited is on the top.
 
--
Sandi Dickenson
ASG Volunteers Group.
No, they are in alphabetical order based on the name the group was created as. The list however displays the wording that the owner has chosen as the group's display name.
 
--
Gerald


moderated Re: Feature request/enhancement -- Enlarge the vertical size of the "Your Groups" pull-down menu #suggestion

Sandi D
 

On Fri, Jan 3, 2020 at 05:09 AM, Samuel Murray wrote:
the groups in the pull-down menu aren't in any logical order,
The order they appear for me seems to based on the historical order of my last visits. The most recent one I visited is on the top.
 
--
Sandi Dickenson
ASG Volunteers Group.


moderated Re: Feature request/enhancement -- Enlarge the vertical size of the "Your Groups" pull-down menu #suggestion

Samuel Murrayy
 

On 03 Jan 2020 11:09, Samuel Murray wrote:

Yes, that bothers me too.  But a little-known secret is that you can get to https://groups.io/groups very easily by simply clicking on the "Groups.io" logo in the top left of the screen.
I must eat my words. The logo link is even less intuitive than that. It sometimes take you to whatever page you visted previously, e.g. Feed, Your Groups, Topics, etc.

Samuel


moderated Re: Feature request/enhancement -- Enlarge the vertical size of the "Your Groups" pull-down menu #suggestion

Samuel Murrayy
 

On 02 Jan 2020 22:36, Christos G. Psarras wrote:

It would be helpful to vertically-enlarge the "Your Groups" pull-down menu to account for screen Y-size and allow for more viewable groups and less scrolling.
Yes, that bothers me too. But a little-known secret is that you can get to https://groups.io/groups very easily by simply clicking on the "Groups.io" logo in the top left of the screen.

I know it's a bit odd that clicking the web site logo does not take you to the web site's main page (as one would expect), but to a page listing your subscriptions, but fortunately for us, that's the way it is.

(In addition, sorry for maybe hijacking the thread, the groups in the pull-down menu aren't in any logical order, whereas the groups on the Your Groups page are alphabetical, with owned groups at the top.)

Samuel


moderated Re: The Groups.io Beta Group - Digest #668

Laurence Marks
 

At IBM, the response to a bug report where the product didn't perform to user expectations was "Working as Designed," often abbreviated to "WAD."

No matter what you do, you're always going to have that situation.

Larry

--
Larry Marks


moderated Feature request/enhancement -- Enlarge the vertical size of the "Your Groups" pull-down menu #suggestion

Christos G. Psarras
 

 
It would be helpful to vertically-enlarge the "Your Groups" pull-down menu to account for screen Y-size and allow for more viewable groups and less scrolling:


 
Right now it's always the same height (not big enough IMO) regardless of the screen's vertical-size, so there is scrolling that much of it can be avoided if the menu's vertical size/height was bigger.

Thanks and Cheers,
Christos


moderated Re: The Groups.io Beta Group - Digest #668

KWKloeber
 


>>> superfluous or confusing<<<

If you think in a logical linear fashion, not at all. 

A bug isn’t confirmed until Mark receives the email and verifies it’s a bug (or is not.)

The prefix (ie, qualifier) “bug”report@ is technically incorrect because no one knows when submitting it that’s it’s a bug (vs potential) until it’s verified to be as such by Mark. 
Someone could think,  “I don’t know whether it’s a true bug or user error, or machine/browser error, so I better not use that address.”

(Subsequent silence on this doesn’t indicate agreement with left coast logic.  LOL)



On Jan 2, 2020, at 2:25 PM, main@beta.groups.io <digestnoreply@groups.io> wrote:

superfluous or confusing


moderated Re: Feature requests/Canny after two weeks

 

Exactly, so the adjective is either superfluous or confusing, depending on who is using it. It serves no purpose. 😊


On Jan 2, 2020, at 11:21 AM, Ken Kloeber via Groups.Io <KWKloeber@...> wrote:

>>>On Thu, Jan 2, 2020 at 07:51 AM, J_Catlady wrote:
“potential”<<<
LOL, I’m not that presumptuous to be certain enough that a “potential” bug, is an “actual” bug. 

--
J

Messages are the sole opinion of the author, especially the fishy ones.
My humanity is bound up in yours, for we can only be human together. - Desmond Tutu


moderated Re: Feature requests/Canny after two weeks

KWKloeber
 

>>>On Thu, Jan 2, 2020 at 07:51 AM, J_Catlady wrote:
“potential”<<<
LOL, I’m not that presumptuous to be certain enough that a “potential” bug, is an “actual” bug. 


moderated Re: Members Download information #suggestion

Duane
 

On Thu, Jan 2, 2020 at 08:39 AM, Duane wrote:
and "member_notes"
Drat, faulty memory.  Should be "moderator_notes".

Duane


moderated Members Download information #suggestion

Duane
 

While playing with various things the last few days, relative to some questions that have been asked recently, I realized that it would be beneficial to have some additional information included when using the Download button on the Members page.  In this case, it would specifically be the "id", "user_id", and "member_notes" that are included in the export (JSON) file.  Ideally, all of the information contained in the export could be included in the download, but that might be stretching it a bit.

Thanks,
Duane


moderated Re: Feature requests/Canny after two weeks

 

For an email address, you could use the term bugreport.


On Jan 2, 2020, at 4:51 AM, J_Catlady via Groups.Io <j.olivia.catlady@...> wrote:

Hashtag, email address, whatever. It’s the qualifier “potential” that’s the problem. 


On Jan 2, 2020, at 1:32 AM, Ken Kloeber via Groups.Io <KWKloeber@...> wrote:

>>>
potential-bug@“ could differentiate general support vs bug reporting.
I don't think a hashtag like that will be effective.<<<

In response to Sandi’s comment about both bugs and support questions addressed to <support@>, <potential-bug@> (or whatever@) would be an address specifically for bugs. 
i.e., @ being common for an email address, not for a (#) hashtag. 
Focus LOL. 



--
J

Messages are the sole opinion of the author, especially the fishy ones.
My humanity is bound up in yours, for we can only be human together. - Desmond Tutu


--
J

Messages are the sole opinion of the author, especially the fishy ones.
My humanity is bound up in yours, for we can only be human together. - Desmond Tutu


moderated Re: Feature requests/Canny after two weeks

 

Bug reports in the bug forum could be required to be tagged from a set of defined hashtags that relate to specific features, plus an #other tag. That would help.


On Jan 2, 2020, at 1:38 AM, Ken Kloeber via Groups.Io <KWKloeber@...> wrote:

>>>On Wed, Jan 1, 2020 at 04:37 PM, J_Catlady wrote:
useful only if bugs are easily identifiable there by subject lines, and there again you fall prey to possible widespread misuse in not identifying bugs properly, etc.<<<
Ok I can buy into the benefit of a bug-specific forum. (BUT good luck with the above caveat.)  Arrrgh. 

--
J

Messages are the sole opinion of the author, especially the fishy ones.
My humanity is bound up in yours, for we can only be human together. - Desmond Tutu


moderated Re: Feature requests/Canny after two weeks

 

Hashtag, email address, whatever. It’s the qualifier “potential” that’s the problem. 


On Jan 2, 2020, at 1:32 AM, Ken Kloeber via Groups.Io <KWKloeber@...> wrote:

>>>
potential-bug@“ could differentiate general support vs bug reporting.
I don't think a hashtag like that will be effective.<<<

In response to Sandi’s comment about both bugs and support questions addressed to <support@>, <potential-bug@> (or whatever@) would be an address specifically for bugs. 
i.e., @ being common for an email address, not for a (#) hashtag. 
Focus LOL. 



--
J

Messages are the sole opinion of the author, especially the fishy ones.
My humanity is bound up in yours, for we can only be human together. - Desmond Tutu


moderated Re: Bugs sent to support not generating acknowledgements #Bug about bugs #bug

Sandi D
 

On Wed, Jan 1, 2020 at 11:11 AM, J_Catlady wrote:
I have not been receiving the standard acknowledgement of any bugs I've sent to the support address
I posted in another thread how it would be useful to have a "bug" group. The reason being, I was interested in following their reporting and which ones were being addressed. I had no idea that bugs sent to Support were ever acknowledged. As a newbie to GIO bug reporting, I thought it was normal for Support emails to vanished into a black hole of sorts. Nice to know that isn't how it used to be. 
 
--
Sandi Dickenson
ASG Volunteers Group.


moderated Joining subgroup via e-mail directly only subscribes user to main group #bug

Samuel Murrayy
 

Hello

I have tested whether a user can join a subgroup directly after responding to an invite, and yes: he can. However, if a user tries to join a subgroup directly via e-mail, Groups.io sends out conflicting responses and does subscribe the user to the subgroup.

1. In a test, a user (i.e. me) tried to subscribe to my test group's subgroup directly, via e-mail (not via invite).
2. Groups.io replied (from the subgroup), telling the person to "reply" to confirm the subscription (to the subgroup).  The reply from Groups.io mentioned the subgroup specifically and not the main group at all.
3. After the user replied to the message, the moderator received a message from Groups.io that the test user wants to join the *main* group (not the subgroup).
4. After the moderator approved the membership, the test user is a member of the main group, but not of the subgroup.
5. After a few minutes, the test user received a welcome message from the *main* group, and the moderator received confirmation that the test user joined the main group.
6. The test user is still not subscribed to the subgroup, and (presumably) has to try to join the subgroup a second time.

Samuel


moderated After accepting invite to subgroup, Groups.io tells user to use plus-style address to post #bug

Samuel Murrayy
 

Hello

In a test, a user who accepted an invitation to a subgroup is told to use the plus-style address for posting to the subgroup (see image attached).  This is not ideal.  I suspect the template for that page just needs to be updated.

Samuel

[By the way, posting to the plus-style address works fine, although when the reply is received again, it comes from the subdomain-style address, which would mean that users would then end up with two different addresses in their e-mail program's address book.]


moderated Re: Feature requests/Canny after two weeks

KWKloeber
 

>>>On Wed, Jan 1, 2020 at 04:37 PM, J_Catlady wrote:
useful only if bugs are easily identifiable there by subject lines, and there again you fall prey to possible widespread misuse in not identifying bugs properly, etc.<<<
Ok I can buy into the benefit of a bug-specific forum. (BUT good luck with the above caveat.)  Arrrgh. 


moderated Re: Feature requests/Canny after two weeks

KWKloeber
 

>>>
potential-bug@“ could differentiate general support vs bug reporting.
I don't think a hashtag like that will be effective.<<<

In response to Sandi’s comment about both bugs and support questions addressed to <support@>, <potential-bug@> (or whatever@) would be an address specifically for bugs. 
i.e., @ being common for an email address, not for a (#) hashtag. 
Focus LOL. 



moderated Re: Feature requests/Canny after two weeks

 

On Wed, Jan 1, 2020 at 12:56 PM, Ken Kloeber wrote:
potential-bug@“ could differentiate general support vs bug reporting.
I don't think a hashtag like that will be effective. You'll get a plethora of people using it identically to #bug, either sometimes or all the time, either because most bugs *are* still potential until they're confirmed (either by the reporting user or others), and/or because they don't know the difference between "general support" and "bug reporting," etc. etc. etc. It will be a complete mish-mosh. 

a forum to browse bugs MIGHT be helpful, but (hopefully) anything posted/searched/browsed for on there would be moot (the bug was subsequently corrected/addressed so the bug will no longer exist
I think a bugs forum might be very helpful so that you could check whether a bug you notice has already been reported and not repeat it (and/or you could add details to the thread when you find a bug you've also experienced; but I think it would be useful only if bugs are easily identifiable there by subject lines, and there again you fall prey to possible widespread misuse in not identifying bugs properly, etc. I don't think anything in a bugs forum would be "moot." First, bugs take awhile to get fixed around here; second, a fixed bug should not be removed from the system, but marked "fixed", so that people still experiencing it can report that it's not really fixed.

Regarding the prioritization of feature suggestions based on user payment rather than suggestion quality, we agree.
 
--
J

Messages are the sole opinion of the author, especially the fishy ones.
My humanity is bound up in yours, for we can only be human together. - Desmond Tutu