Bug 923461 - Update document list view and link to the violated entries after project wide validation
Summary: Update document list view and link to the violated entries after project wide...
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Zanata
Classification: Retired
Component: Usability
Version: 2.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 2.3
Assignee: Alex Eng
QA Contact: Ding-Yi Chen
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-19 22:13 UTC by Alex Eng
Modified: 2013-11-27 03:36 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2013-11-27 03:25:43 UTC


Attachments (Terms of Use)

Description Alex Eng 2013-03-19 22:13:32 UTC
Description of problem:
After running validation check in document list view, a report should be provided with link to transunit in editor

Comment 1 Alex Eng 2013-03-24 21:55:27 UTC
Change of implementation, instead of having a single page report, update the document list view that has error, and when user click on the "has error" documents, it display all entry that has error in the document by using the view filter in the editor.

Also, suggest to change the document list view to use asynchronous call for the run validation. This might involve in changing the document list view table type.

Comment 4 Ding-Yi Chen 2013-04-09 05:01:50 UTC
VERIFIED with Zanata version 2.3-SNAPSHOT (20130409-1233)

Comment 5 Sean Flanigan 2013-11-27 03:16:23 UTC
Closing VERIFIED bugs for Zanata versions <= 3.1.

Comment 6 Sean Flanigan 2013-11-27 03:17:20 UTC
Closing VERIFIED bugs for Zanata versions <= 3.1.

Comment 7 Sean Flanigan 2013-11-27 03:19:47 UTC
Closing VERIFIED bugs for Zanata versions <= 3.1.

Comment 8 Sean Flanigan 2013-11-27 03:25:43 UTC
Closing VERIFIED bugs for Zanata versions <= 3.1.

Comment 9 Sean Flanigan 2013-11-27 03:34:36 UTC
Closing VERIFIED bugs for Zanata versions <= 3.1.

Comment 10 Sean Flanigan 2013-11-27 03:36:44 UTC
Closing VERIFIED bugs for Zanata versions <= 3.1.


Note You need to log in before you can comment on or make changes to this bug.