Every entry is just a single line of text. If you use long-ish, descriptive issue/story names, the timeline becomes very hard to read, especially when dealing with tasks inside stories.
Have a look at your github dashboard for a better example. It uses short entries for simple events, but more interesting events get multiple lines, icons, images, etc. to keep things easy to "parse".
Repeated events are... well, repeated. Say for example I'll edit a wiki page multiple times as I work on something. Each and every edit will show up in the timeline. This is needlessly verbose, and repeated events should be collapsed.
The prose could probably use some work. "
When doing anything with a task, the timeline will contain the full title of the task, the story it belongs to, along with a very verbose description of what happened. All on a single line of light grey mixed with light green.
This module needs love!
Hi @mkaito
We have been talking about this and reduced drastically the amount of information displayed in the timeline. We agree that it could be improved.
Could you please give us an example on how would you improve those verbose timeline entries?
And which would you make more important?
Thanks!
Well, you can always click into a story/task detail page to get more info. So just show the essentials in the timeline. And use multiple lines, icons and colours to make things easier to parse at a glance.
Thanks for the feedback, I agree,
The design team will review this idea to see if we can make it easier to parse.
Is there an option to change the default landing page of a project so that it opens the Kanban/Scrum view instead of the timeline?
That would already make the uselessness of the timeline more acceptable :)
@stevenroose no, the timeline is the default page.
Is there an opened issue already to make it possible to change that?
On Sep 16, 2016 12:16, "Xaviju" [email protected] wrote:
@stevenroose https://github.com/stevenroose no, the timeline is the
default page.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/taigaio/taiga-front/issues/748#issuecomment-247566424,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0F3DLkUGZe15hxyhccWGqanTVmDao3ks5qqmyFgaJpZM4GoDHu
.
We have been doing some housecleaning work prior to Taiga6 upcoming release and we are rejecting old issues that we didn't correctly attend back then. Since Taiga6 brings a significant UX/UI rework, we encourage you to wait and see if Taiga6 satisfies this need and open a new issue if that's not the case. This time we will make sure to review it when it comes through. Thank you very much on behalf of the Taiga Team!
Closed
Most helpful comment
Is there an opened issue already to make it possible to change that?
On Sep 16, 2016 12:16, "Xaviju" [email protected] wrote: