This came up in community conversation on this page: https://www.mediawiki.org/wiki/Talk:Growth/Focus_on_help_desk

An idea brought up in this community conversation is to also allow users to report that their question has not been answered on time.

This looks good to me in beta.

@SBisson @Etonkovidova @RHo -- I was able to replicate the issues in both Variation C and in the standard component library that @SBisson linked me to. I created videos of it, and they're in our team drive as Variation_C_iPhone_Safari_2018-12-14.mov and Standard_components_iPhone_Safari_2018-12-14.mov. I think you should view them in that order.

We have the initial set of links from both KO and CS Wikipedias. This task is remaining open because those communities are still intending to improve the links before the initial launch of the help panel in January.

Thanks, @revi. We are leaving this "In Progress" since you're still working on assembling better links.

The questions that were listed in this ticket have grown to become the full "Help Panel -- measurement specifications" document: https://docs.google.com/document/d/1rnk-eT092c3CHESBgHxwN0udiXRP8lqgbENWQ-1RhBE/edit#

@SBisson -- I just went through the whole "Help Panel -- measurement specifications" document, and also went through this whole Phab task. As you pick up this task, I think it would probably be good to take a close read of the document (including the comments) and compare it to what @Catrope has drafted for the schema, because I think that the document is a more recent set of requirements that came together after @Catrope assembled the draft schema.

This is deployed and going fine. Resolving.

Posted summary of the findings on wiki here. Resolving task.

Since I tested this in production, and it's not an issue, I am closing this.

@SBisson @RHo @Etonkovidova -- thank you for making this turn out great!

@Catrope -- I just looked at the defaults for newly created accounts in Korean and Czech (by opening the preferences of a new account), and they look like this:

Jazmin will go through the Instrumentation DACI for this small change as she does the process for T209982.

@RHo will prioritize the different issues in this task to help the team work through them.

@Etonkovidova -- could you please verify this as soon as possible?

@kostajh, @RHo, and I settled on a plan here.

Okay, I would like to keep it open.

@kostajh -- yes, the number itself should be in the header, the way it's shown in this task's description. That's the request from the community.

@SBisson -- I agree that we should not actually launch with the feature on for users who registered before the launch date but still have 0 edits. I agree that it would be a distraction. I just think we should make it possible to do so if we ever want to. I will change the description to reflect that.

Thanks, everyone, for talking this through. Taking all this together, I think it sounds like we should do @RHo's most recent design, with the second click to get to user preferences.

The major features on this project have been released for a month with no issues, and we have closed all 87 subtasks in this epic.

I completed this by adding information in this new section on the mediawiki.org page. The section now describes the improvements our project made, and contains instructions for how to use those improvements.

@kostajh -- so no QA or validation will be needed on this task -- it will all happen on the linked tasks?

When @Urbanecm was testing out Variation C in beta this morning, he brought up two questions for @RHo:

@MMiller_WMF - I thought we had made it "Finish" in var A as well in the final copy?

I think this can be up to @RHo (and I think we'll need designs for whatever route we go with).

@RHo -- one thing I noticed is that the last page of the survey has a grayed-out "Next" button. That made me feel like I had to check "Yes" on the mentorship question in order to proceed. Maybe there should be no "Next" button on that page?

Tagging @nettrom_WMF in case he wants to weigh in. @nettrom_WMF, I think this tag is what you'll need to use to remove help panel questions from our analysis of whether a user is activated.

Thanks, @Urbanecm. That makes sense.

@kostajh @RHo -- that second rule, to encourage the user to verify their email address, is something we haven't discussed. How were you thinking that would work?

The team had multiple discussions about how to automatically construct the headers for posting questions to the help desk. The discussion is below pasted from email. I will update the description of this task with the business rules, which are:

Assigning to @kostajh to implement and to put in QA afterward so that @Etonkovidova can check them.

After a team discussion today, we decided the following. I will also copy this into the task description.

Okay, great, thanks, @kostajh. @RHo, could you add language to the spreadsheet about that success message? I'll add it to the requirements now.

@Urbanecm -- thanks for doing this. Could you please summarize for us the outcome here? It looks like you decided that the links should be the same regardless of which editor someone is using. Is that correct?

@Trizek-WMF -- I think we should only create that page if YOU think it is worthwhile. If you think it is, then I think you can use T210906 to do it.

Thanks, everyone, for the responses.

So @kostajh, taking this all together, it sounds like in the near term, we don't actually have the diversity and specificity of help pages to fill out a 5x5 matrix. But we theoretically WANT to have that one day. Currently, it seems like a given wiki really could do a 2x5 matrix. So I guess it can be up to you how to engineer it to balance the near term with the long term. Does that help?

@kostajh @RHo @Trizek-WMF @Urbanecm @revi -- I think we are discussing several issues in this task:

@Trizek-WMF @Urbanecm -- how does making it a beta feature for non-newcomers work? Does this mean all users would have it as an option under "Beta"? One of my concerns is that if a lot of people try it out just to see what happens, it could flood the help desk with test questions. What do you think?

I need to go over this copy, and then I need to send it a couple collaborators outside of our team to have a look.