Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Desktop activity list is not the activity stream #1443

Closed
MTRichards opened this issue Feb 18, 2014 · 10 comments
Closed

Desktop activity list is not the activity stream #1443

MTRichards opened this issue Feb 18, 2014 · 10 comments
Assignees
Labels
Design & UX Enhancement p2-high Escalation, on top of current planning, release blocker
Milestone

Comments

@MTRichards
Copy link

Currently, the Activity tab of the desktop client is not the same as the server activity stream. While the desktop activity list is QUITE helpful, it should be called something like sync log, and the actual server activity stream should load in the activity tab.

@MTRichards MTRichards added this to the 1.7 - UI Enhancements milestone Feb 18, 2014
@jancborchardt
Copy link
Member

The plan was to just combine it instead of having two separate things which essentially are the same: A history of file activity.

@MTRichards
Copy link
Author

Ok. That works. Ideally you can filter to see one or the other :). and also text search them of course. But lets start with combining them.

Then we need to make it possible to clear them.

And then text filter search them.

@dragotin dragotin modified the milestones: 1.9 - Multi-account, 1.8 - UI Enhancements Jan 19, 2015
@guruz
Copy link
Contributor

guruz commented Jun 24, 2015

@MTRichards I don't think this is feasible still for 2.0
Move?

@MTRichards MTRichards modified the milestones: 2.1-next, 2.0 - Multi-account Jun 24, 2015
@MTRichards
Copy link
Author

Updated to 2.1, thanks for the ping.

@jancborchardt
Copy link
Member

Ref #2530 #1745

@MTRichards
Copy link
Author

owncloud/activity#349

@guruz guruz added the p2-high Escalation, on top of current planning, release blocker label Nov 3, 2015
@guruz guruz added the ReadyToTest QA, please validate the fix/enhancement label Nov 18, 2015
@Dianafg76 Dianafg76 removed the ReadyToTest QA, please validate the fix/enhancement label Nov 19, 2015
@Dianafg76
Copy link

Related #3732 , #4083

@dragotin
Copy link
Contributor

I think this is only a high level view on #3732, closing hence, lets track over there.

@jancborchardt
Copy link
Member

I disagree with closing this as now the low-level technical detail overruled the high-level plan which is easier for people to relate.

See feedback from @jospoortvliet at #3737 (comment) and my counter points at #4083 (comment)

@dragotin
Copy link
Contributor

See new issue #4208

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Design & UX Enhancement p2-high Escalation, on top of current planning, release blocker
Projects
None yet
Development

No branches or pull requests

5 participants