Closed Bug 641503 Opened 15 years ago Closed 13 years ago

Add feature: Articles that link to this article

Categories

(support.mozilla.org :: Knowledge Base Software, task, P4)

Tracking

(Not tracked)

RESOLVED FIXED
2013Q1

People

(Reporter: atopal, Assigned: mythmon)

References

Details

(Whiteboard: u=contributor c=wiki p=2 s=2013.7)

Please add the "Articles that link to this article" feature to the KB to make it easier for people to understand how articles are used (especially with templates)
Target Milestone: 2011Q2 → 2011Q3
A "what links here" feature would also help in decisions about whether or not an article or template should be archived (the more "backlinks" it contains, the more important it is the the KB). It would also help when updating an article, to see what other articles link there; for example, you may be changing a heading title or removing a section in an article that another article is linking to. Ref: http://en.wikipedia.org/wiki/Help:What_links_here
This is a non-trivial (i.e. big, complicated) thing to do. Not sure when we'll have a chance to work on it.
Target Milestone: 2011Q3 → ---
When (if?) this bug is fixed, would Image pages like https://support.mozilla.org/en-US/gallery/image/8726 also show what KB article (or KB article forum post) links to that image? For example, see this Image page on MozillaZine, which shows, at the bottom, two articles that link to that image: http://kb.mozillazine.org/Image:FolderOptions.png This feature would help clean up the Media Gallery, since "orphan" images that are unrelated to KB articles could be deleted.
(In reply to James Socol [:jsocol, :james] from comment #2) > This is a non-trivial (i.e. big, complicated) thing to do. Not sure when > we'll have a chance to work on it. Any hope that this will get worked on? The need for a "what links here" feature just came up in a discussion about potentially archiving or redirecting a KB article. See https://support.mozilla.org/kb/latest-firefox-issues/discuss/2417
Yeah, this has come up a number of times, and each time you edit a template it's a gamble whether it still fits into the paragraphs it is inserted into, especially for other languages that can be quite tricky. I'm putting this into the 11th sprint tentatively, so we can discuss this beforehand and see how big it is. It might go into that sprint or into one after that.
Target Milestone: --- → 2012.11
Like jsocol said in Comment 2, this is non trivial. We could turn this into a research bug to figure out what we want to do and then estimate the outcome of that.
Whiteboard: u=contributor c=wiki p=
Priority: -- → P4
Per comment #5 and comment #6, I spun off a research bug which I'm putting in the 2012.11 sprint. I'm taking this bug out because we don't know what's involved, yet.
Target Milestone: 2012.11 → 2012Q2
Moving 2012Q2 bugs to Future.
Target Milestone: 2012Q2 → Future
Depends on: 790785
Blocks: 790785
No longer depends on: 790785
Whiteboard: u=contributor c=wiki p= → u=contributor c=wiki p= s=2012.22
No longer blocks: 761582
Depends on: 761582
Whiteboard: u=contributor c=wiki p= s=2012.22 → u=contributor c=wiki p= s=2012.23
Target Milestone: Future → 2012Q4
We aren't ready to implement this yet.
Whiteboard: u=contributor c=wiki p= s=2012.23 → u=contributor c=wiki p= s=2012.24
No longer blocks: 790785
Whiteboard: u=contributor c=wiki p= s=2012.24 → u=contributor c=wiki p= s=2013.1
Target Milestone: 2012Q4 → 2013Q1
moving to next sprint, while we do the research in this sprint: bug 825621
Whiteboard: u=contributor c=wiki p= s=2013.1 → u=contributor c=wiki p= s=2013.2
After some research in bug 825621, I am pretty confident about how to do this. Grabbing it and estimating at 2pts, which is a bit of a safe estimate.
Assignee: nobody → mcooper
Whiteboard: u=contributor c=wiki p= s=2013.2 → u=contributor c=wiki p=2 s=2013.2
Falling to next sprint.
Whiteboard: u=contributor c=wiki p=2 s=2013.2 → u=contributor c=wiki p=2 s=2013.3
Falling to next sprint.
Whiteboard: u=contributor c=wiki p=2 s=2013.3 → u=contributor c=wiki p=2 s=2013.4
Assigning to backlog for an appropriate sprint.
Whiteboard: u=contributor c=wiki p=2 s=2013.4 → u=contributor c=wiki p=2 s=2013.backlog
Whiteboard: u=contributor c=wiki p=2 s=2013.backlog → u=contributor c=wiki p=2 s=2013.7
Deployed to prod now.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
I don't think this is working: 1. Start at https://support.mozilla.org/en-US/kb/How%20to%20set%20the%20home%20page 2. Click the first link in the article - https://support.mozilla.org/en-US/kb/firefox-says-its-just-updated-every-time-it-starts 3. Check to see what links to that article and you get the message: "No other documents link to Firefox says it's just updated every time it starts - how to fix."
(In reply to Verdi [:verdi] from comment #18) > I don't think this is working: Sorry I should've mentioned, it will take up to six hours for all the data to be in place. We need to reparse an rerender the entire KB.
Hello All I have seen several times contributors reporting images as spam and admins keep deleting it(without having any proof). Is it possible to have link to every image(like we do with templates "what links here") and we can easily find whether the image is sumo related or not?
This should be possible, with a little elbow grease, but it belongs in new bug. Can you file one for it?
Filed bug 935068 to " Add feature: Articles that link to this image"
You need to log in before you can comment on or make changes to this bug.