Bug 741478 - Document title still shows "No document selected" if you click on the document you just edit
Document title still shows "No document selected" if you click on the documen...
Product: Zanata
Classification: Community
Component: Component-UI (Show other bugs)
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Alex Eng
Ding-Yi Chen
Depends On:
  Show dependency treegraph
Reported: 2011-09-26 20:00 EDT by Ding-Yi Chen
Modified: 2011-10-28 03:34 EDT (History)
2 users (show)

See Also:
Fixed In Version: 1.4-alpha-2-SNAPSHOT (20110928-1719)
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-10-28 03:34:49 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ding-Yi Chen 2011-09-26 20:00:31 EDT
Description of problem:
Clicking Project name in the message list view brings back the
document list view. 

By clicking document A in the document list view again, it brings back the editing screen of document A, however, the title still shows

ProjectName -> No document selected

This confuses the users.

Version-Release number of selected component (if applicable):
Zanata version 1.4-alpha-2-SNAPSHOT (20110926-1021)

How reproducible:

Steps to Reproduce:
1. Log in to Zanata
2. Choose the project AboutFedora and version f13.
3. Click translate in any locale.
4. Document list view should be brought up at this stage, click a document,
say, "Article_Info" to enter document view.
5. Click on project name, AboutFedora, to go back to document list view.
6. Click on "Article_Info"

Actual results:
Title shows:
About Fedora (f13) > No document selected 

Expected results:
Title shows:
About Fedora (f13) > Article_Info

Additional info:
See also: Bug 727719, Bug 727721
Comment 1 Ding-Yi Chen 2011-09-29 00:07:30 EDT
VERIFIED with Zanata version 1.4-alpha-2-SNAPSHOT (20110928-1719)

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