Closed (fixed)
Project:
Translation Management Tool
Version:
8.x-1.x-dev
Component:
Translator: Local
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
19 Jan 2016 at 10:40 UTC
Updated:
5 Feb 2016 at 10:34 UTC
Jump to comment: Most recent, Most recent file

Comments
Comment #2
miro_dietikerThe primary problem here is that progress is not accessible.
And yeah if adding a type helps gaining overview, let's add that too.
Comment #3
edurenye commentedNot sure about the link in the label, where should go, to the JobItem? Most probably the assigned user will not be able to open the link. So to the content? I'm not sure if make sense, now the label is from the JobItem, not the content. And most important we don't do that in JobItem, so won't be coherent. Maybe I should open a followup to change it everywhere?
Added progress, word_count, type and empty message. We discussed that we don't want to add changed.
Comment #4
miro_dietikerThat looks good, but our tests should also check that each item is present.
Links yeah, are unrelated to this issue and should be consistent.
So you are telling me the content of the row might be inaccessible as long as the user is not assigned to the job?
I'm not so sure about that. One one hand a user thus only sees what he needs to see. But looking at a job content before deciding might be important for some cases.
Might need a permission.
Let's create a separate issue about consistently linking labels with this permission dependency discussion... and skip it here.
Comment #5
edurenye commentedAdded tests and created the followup #2654248: Add links to labels consistently.
Comment #7
miro_dietikerHow about an assertJobItemProgress($row, $text)?
Example: $this->asserJobItemProgress(2, '0/0/1')
Comment #8
edurenye commentedDone.
Comment #9
miro_dietikerYes this looks nice!
BTW: Are we safe now with invalidating these elements when items change? We previously had issues with progress markers that was cached and not updated. But i think there is a separate issue about that... :-)
Comment #11
edurenye commentedYes, we are fixing the caching here #2652678: Errors in views in local translator.
Here are the visual changes that we did in this issue: