Bug 1098407 - Copy Translations box does not close if process halted via Process Manager
Summary: Copy Translations box does not close if process halted via Process Manager
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Zanata
Classification: Retired
Component: Component-UI
Version: development
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 3.5
Assignee: Alex Eng
QA Contact: Zanata-QA Mailling List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-16 06:25 UTC by Damian Jansen
Modified: 2015-01-26 23:27 UTC (History)
2 users (show)

Fixed In Version: 3.5.0-SNAPSHOT (git-server-3.4.1-39-g2204aa2)
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-01-26 23:27:48 UTC
Embargoed:


Attachments (Terms of Use)

Description Damian Jansen 2014-05-16 06:25:37 UTC
Description of problem:
If the Copy Translations process is halted via the admin Process Manager, the progress indicator stops but the box is still in the active state.

Version-Release number of selected component (if applicable):
dev

How reproducible:
Easy always

Steps to Reproduce:
Pre: reasonable large project with documents
1. Log into zanata as admin and open two tabs
2. Go to the project version implied above, and in the other tab go Menu -> Administration -> Process manager
3. In tab 1, start a copy translations process
4. In tab 2, Cancel that process when it shows in the list

Actual results:
The Copy Translations box in tab one loses the progress bar, but remains

Expected results:
The box should either disappear, or indicate the process has been cancelled and say "Ok" instead of "Cancel"
Also, bringing the Copy Translations window back up at this point should just have the Start button, not Cancel

Additional info:

Comment 1 Alex Eng 2014-05-28 04:05:42 UTC
Pull request:
https://github.com/zanata/zanata-server/pull/470

Comment 2 Ding-Yi Chen 2014-06-02 00:15:19 UTC
VERIFIED with Zanata 3.5.0-SNAPSHOT (git-server-3.4.1-39-g2204aa2)


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