Page MenuHomePhabricator

Fix issues found during Content Translation templates research
Open, Needs TriagePublic

Description

As the a result of the research sessions on Template translation (T161188), different issues were identified.
Some are specific to the translation of templates, other are more general (since users also made general use of Content Translation).
Check the sub-tickets or view the full list.

Related Objects

StatusSubtypeAssignedTask
OpenNone
OpenNone
ResolvedPginer-WMF
OpenNone
OpenNone
OpenNone
Resolvedsanthosh
OpenNone
OpenNone
Resolved Petar.petkovic
OpenNone
OpenNone
OpenNone
ResolvedPginer-WMF
OpenNone
DuplicateNone
OpenNone
ResolvedNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
Resolveddchen
OpenNone
OpenNone
OpenNone
Duplicatedchen
Declineddchen
OpenNone
Resolveddchen
OpenNone
OpenNone
Resolveddchen
Resolveddchen
Declineddchen
OpenNone

Event Timeline

dchen created this task.Mar 23 2017, 1:45 AM
dchen moved this task from Backlog to Doing on the Contributors-UX-Research board.
Pginer-WMF renamed this task from Content Translation_templates research; issues found to Fix issues found during Content Translation templates research.Mar 23 2017, 9:53 AM
Pginer-WMF updated the task description. (Show Details)May 1 2017, 9:46 AM
dchen moved this task from Doing to Done on the Contributors-UX-Research board.Jun 6 2017, 6:13 PM
He7d3r added a subscriber: He7d3r.Jan 11 2018, 10:10 AM
Arrbee added a subscriber: Arrbee.Jun 26 2018, 7:57 PM

@Pginer-WMF do we still need this ticket?

@Pginer-WMF do we still need this ticket?

The main purpose of this ticket is grouping together the tickets that were generated after a user research study. It allows to check what came out of it and how much got solved over time. We can think of it as a tracker, but not a main tracker since it is not representing a whole functional area. It compiles mostly template-related issues and other issues found in the way.

Aklapper removed dchen as the assignee of this task.Jun 19 2020, 4:14 PM

This task has been assigned to the same task owner for more than two years. Resetting task assignee due to inactivity, to decrease task cookie-licking and to get a slightly more realistic overview of plans. Please feel free to assign this task to yourself again if you still realistically work or plan to work on this task - it would be welcome!

For tips how to manage individual work in Phabricator (noisy notifications, lists of task, etc.), see https://phabricator.wikimedia.org/T228575#6237124 for available options.
(For the records, two emails were sent to assignee addresses before resetting assignees. See T228575 for more info and for potential feedback. Thanks!)