The "Relevant To" section of the document adding/editing UI needs to be changed to reflect bug 674920 comment 3, that is the check boxes need to be reduced to a few *products*, and checking/unchecking them should add/remove tags. Product Tag --------------------- Desktop desktop Mobile mobile Sync sync Home fxhome Michael, do those products and tags work for you? I think they match what we use in Questions.
The product names look good to me. I'm not sure if capitalization is important but the existing Home tag is "FxHome". The others are correct.
Does it make sense to show this on the Edit document page? At that point, topics will be visible and they can remove/add from there. I think it makes most sense to show it on the new document form and use that to prepopulate topics. From that point on, you deal with topics directly. Thoughts? Complaints?
Even if they are the same in the back-end, I'd like to keep those separate in the UI. The list here is restricted. We will change those 4 products very, very seldom, if at all. The topics (tags) on the other hand will fluctuate much more, so it makes sense to have a structured way to change those constant 4 tags/products and a less rigid way to add/remove other tags/topics.
(In reply to Kadir Topal [:atopal] from comment #3) Are you saying that these four topics are special cases and shouldn't show up under topics then? I just don't like having two ways of changing the same thing in a form. I find it confusing and it makes it harder to implement (have to keep the two fields sync'd in the front-end and back-end)
FTR, the four products are stored as tags in the backend but are not listed in the topics section of the document form. You can only change them using the checkboxes under "Relevant to". https://github.com/jsocol/kitsune/commit/96893ac127980c6184e7b7cb6ce2d5b747ab2428
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Verified four checkboxes display for the tags above when creating a kb article or editing the 'relevant to' section in the description
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.