Page MenuHomePhabricator

[Story] Usage Tracking: correctly track redirect usage
Open, LowestPublic

Description

When a redirect is resolved while accessing repo data from a client wiki,

  • the usage should be associated with the redirect target
  • the usage of the redirect itself should be tracked (using aspect X or a new R aspect)

When a redirect is created or changed, this should be considered an X change, since it affects all types of usage.

This could be solved by doing a reverse redirect lookup when processing changes: When handing a change for Q12, find all redirects to Q12. Do the change processing for Q12 and all the redirects.

Related Objects

View Standalone Graph
This task is connected to more than 200 other tasks. Only direct parents and subtasks are shown here. Use View Standalone Graph to show more of the graph.

Event Timeline

daniel created this task.Mar 19 2015, 11:15 AM
daniel raised the priority of this task from to Normal.
daniel updated the task description. (Show Details)
daniel added a subscriber: daniel.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMar 19 2015, 11:15 AM
daniel updated the task description. (Show Details)Mar 19 2015, 11:17 AM
daniel set Security to None.
daniel added a subscriber: adrianheine.
Lydia_Pintscher renamed this task from Usage Tracking: correctly track redirect usage to [Story] Usage Tracking: correctly track redirect usage.Sep 10 2015, 12:29 PM
daniel updated the task description. (Show Details)Nov 27 2016, 1:01 PM
Lydia_Pintscher lowered the priority of this task from Normal to Lowest.Mar 2 2018, 11:50 AM