Bug 1195865 - [RFE] Show event timeline for projects/languages
Summary: [RFE] Show event timeline for projects/languages
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Zanata
Classification: Retired
Component: Usability
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: ---
Assignee: Luke Brooker
QA Contact: Zanata-QA Mailling List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-24 17:57 UTC by Martin Kolman
Modified: 2016-04-18 09:37 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-07-29 03:33:09 UTC
Embargoed:


Attachments (Terms of Use)

Description Martin Kolman 2015-02-24 17:57:04 UTC
Description of problem:
There is currently no way to check if someone is actually translating your project other than manually comparing completion at different points in time.

It would be good to have some sort of a timeline showing important events, such as newly translated string, new languages being added, source document updates, etc.

The only current feature that is kinda close to this is the "last updated/last translated" column.

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


How reproducible:
always

Steps to Reproduce:
1. got to a project website
2. try to find what's happening in the project

Actual results:
There is no easy way to do that.

Expected results:
There is a "project timeline" page/tab/view showing what's happening in the project.

Additional info:

Comment 1 Luke Brooker 2015-02-24 23:15:31 UTC
Hi Martin,

Thanks for submitting this. Project activity is something I have wanted for a while too and I even have it in my initial prototypes. I think there is just some backend work to be done before it's completed.

I'll make sure this is updated with any progress.

Comment 2 Zanata Migrator 2015-07-29 03:33:09 UTC
Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-318


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