Filter for Topics needs new copies

RESOLVED FIXED in 2013Q2

Status

support.mozilla.org
Questions
P4
normal
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: ibai, Assigned: rrosario)

Tracking

unspecified
2013Q2

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: u=contributor c=questions p=1 s=2013.8)

(Reporter)

Description

5 years ago
See https://support.mozilla.org/en-US/forums/contributors/709119

The Filter that have implemented for Topics in the forum is great. We need to fix the copies to adapt them to the space that we are using, at the moment some of them are cut and you can't read them.

Thanks!
(Assignee)

Comment 1

5 years ago
The topic display titles can be changed by any admin:
https://support.mozilla.org/admin/topics/topic/

The are no code changes required for that.

It looks like the feature is working just fine, right?

Comment 2

5 years ago
So that's fundamentally the problem. The Titles that are good in one place (the Topic selection in the Home Page) are not good in this drop down.

We could change the titles and make them shorter, but that could backfire (those titles are way more used than this drop down...so I think is better to compromise in the dropdown).

Could we limit the title to the first 30 characters or something in that range?
(Assignee)

Comment 3

5 years ago
Truncating is a solution, sure! Also making the font smaller.

IMO, this feature is more about utility than beautification. So, I'd go with the easiest thing that prevents people from puking on their keyboard. :-D

Comment 4

5 years ago
Agree!

Although...puking on the keyboard could be considered a feature :D
I am not sure this has any easy quick fix. Maybe this needs changing into a research bug, or the background discussion taken elsewhere. It was rather a major modification to introduce without discussion & testing. 

Just shortening without changing the word order gives two titles saying "slowness". Although for  instance modifying
>Fix slowness, crashing, error messages and other problems
to
>Problems: error messages, slowness, crashing and other problems 
gives two distinct short options
>Fix slowness,cras
&
>Problems: error m
removes the previous ambiguity between those two topics, but still does not work.

It is still a clumsy compromise. You could say it has changed from a crass solution to a mess ;-D

An easy fix like that leaves the user loosing out on information with the description not matching the content.

The prior method to filter by tags was bad partly because the Tags were not really discoverable. Now instead we have have broader topics with descriptions that can not be read. 

Crashes, Slowness; & Error Messages are each included as a separate topic, are these actually all included in the
>Fix slowness, crashing, error messages and other problems
?

If so the category (problems other) 
> other problems 
is getting buried amongst other posts.    

I suppose the answer may be to have a two stage selection. That fits in with how the refine and focus option works for example
> https://support.mozilla.org/en-US/products/firefox/fix-problems
Title "Fix slowness, crashing, error messages and other problems"

But then instead of > 50 kb articles break it down into |slowness|crashing|error messages|other problems|. We already have the first three of those topics,the third presumably is easily obtainable by subtraction

This change has also removed the tags options,something Madalina & Patrick appear to have been wishing to amend and make use of https://support.mozilla.org/en-US/forums/contributors/709033?last=51765&page=3#post-51755

Comment 6

5 years ago
John, we still have tags, and we decided to map the AAQ flow to the topic tree (taxonomy) that we developed early last year after a lot of user research.

What you are saying is not that the topics are too verbose but that the topics that we use are too broad...or basically both. This bug only covers the first piece.

There're 2 additional projects (out of scope of a bug) that would help increase the granularity of this topics: 

https://sumo.etherpad.mozilla.org/revamped-aaq
https://sumo.etherpad.mozilla.org/ia-navigation

They are empty for now, but basically the idea is that this quarter we will simplify the AAQ flow, incorporate FxOS and the subtopics. Also, we are going to be working on adding the next level of Subtopics from the taxonomy that we never implemented. 

If this don't cover what you need, please, open a new bug stating your problem so we can discuss it there.
(Assignee)

Comment 7

5 years ago
As John99 mentioned here:
https://support.mozilla.org/en-US/forums/contributors/709127

We should limit the dropdown selections to only the top 10 topics we use in the AAQ.
(Assignee)

Comment 8

5 years ago
Some small UI tweaks needed => 1pt
Whiteboard: u=contributor c=questions p=1 s=2013.8

Comment 9

5 years ago
Take into consideration that this may change if we go all in and we are able to do a better job with the AAQ to categorize threads to the level of the subtopic.
(In reply to :ibai from comment #6)
> John, we still have tags, and we decided to map the AAQ flow to the topic
> tree (taxonomy) that we developed early last year after a lot of user
> research.
Yes I followed that research, and I see we still have tags, although I understand tags are being deprecated.
For now tags can be combined with a topic when filtering answers. 

> What you are saying is not that the topics are too verbose but that the
> topics that we use are too broad...or basically both. This bug only covers
> the first piece.
I am saying there are 26 options in total visible now, but 
1. the verbose description does not display in full
2. if it is shortened so that it does display in the current space will they make sense and allow a user to discriminate the topic content from the short description
(There was a suggestion to change the justification so they do display fully in the available space without being cut off )  
>> https://support.mozilla.org/en-US/forums/contributors/709119#post-51828
>> http://stackoverflow.com/questions/5369393/css-to-align-drop-down-to-the-right 

> There're 2 additional projects (out of scope of a bug) that would help
> increase the granularity of this topics: 
You still have 26 categories displaying, presumably they work I have not tried them all. 

> https://sumo.etherpad.mozilla.org/revamped-aaq
> https://sumo.etherpad.mozilla.org/ia-navigation
The above are presumably private etherpads that I do not have access to.
 
> They are empty for now, but basically the idea is that this quarter we will
> simplify the AAQ flow, incorporate FxOS and the subtopics. Also, we are
> going to be working on adding the next level of Subtopics from the taxonomy
> that we never implemented. 
Not sure what is empty for now 

> If this don't cover what you need, please, open a new bug stating your
> problem so we can discuss it there.

Look at the current topic options, slowness, crashing, error messages, etc. are duplicated in the dropdown listing.
(In reply to Ricky Rosario [:rrosario, :r1cky] from comment #7)
> As John99 mentioned here:
> https://support.mozilla.org/en-US/forums/contributors/709127
> 
> We should limit the dropdown selections to only the top 10 topics we use in
> the AAQ.

I filed Bug 859771
(I guess I do not see an add bugs field in someone-else's bug)
As far as I can tell only one topic is rather long, but even that is not really truncated on my computer (not a particularly high res one either). John, maybe it's Firefox on Linux doing the truncating?

About the topics: yeah, some are rather broad, but it sometimes makes sense. While we do distinguish between slowness, crashing, and hanging, most people don't make that distinction. It's the same for them. 

Let's use this bug to reduce the listed topics to 10. It makes no sense to show more for now since we are not using them to tag questions. Thanks for the report, John!
(Assignee)

Updated

5 years ago
Priority: -- → P4
Target Milestone: --- → 2013Q2
(Assignee)

Comment 13

5 years ago
We are just reducing the topics to the top 10. *grabbing*
Assignee: nobody → rrosario
(Assignee)

Comment 16

5 years ago
Rehan just deployed to prod.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.