Separate support forums per product per language

RESOLVED FIXED in 2014Q4

Status

support.mozilla.org
Questions
P2
normal
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: madalina, Assigned: rehan)

Tracking

(Blocks: 1 bug)

unspecified
2014Q4

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: u=contributor c=questions p=3 s=2014.18)

(Reporter)

Description

3 years ago
Currently our questions forum platform does not support separate forums.

Each time we need to launch a new product or language forum we automatically open forums for all products/all languages which leads to a whole bunch of ghost forums where questions pile up without anybody answering them.

This is particularly important now as we are bound by contract to launch a Firefox OS Bengali forum. Doing it with the current platform would mean opening up forums in Bengali for all Mozilla products present on support.mozilla.org

We need to have separate forums per product and per language so that we can open and close them without affecting the other products or locales.

Updated

3 years ago
Blocks: 1074879
Priority: -- → P2
Whiteboard: u=contributor c=questions p= s=2014.18
Target Milestone: --- → 2014Q4
(Assignee)

Updated

3 years ago
Whiteboard: u=contributor c=questions p= s=2014.18 → u=contributor c=questions p=3 s=2014.18
This is for Rehan.
Assignee: nobody → rdalal
Can we have an update on this? Is this ready to land?
Flags: needinfo?(rdalal)
There is no spec or mockup for this feature :(. It makes it hard to know if we implemented it right.
There was quite a migration dance we had to do, but it landed on master:
https://github.com/mozilla/kitsune/compare/814710971ad1c8a848a91e235b8ea512cc83cae8...cedfad6f8e9373eecbe37b3b439e682b112ec713
The pull requests were here:
https://github.com/mozilla/kitsune/pull/2153
https://github.com/mozilla/kitsune/pull/2175
https://github.com/mozilla/kitsune/pull/2182

This is on prod now.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Flags: needinfo?(rdalal)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.