Top Menu

Jump to content
Home
    Modules
      • Projects
      • Activity
      • Work packages
      • Gantt charts
      • Calendars
      • Team planners
      • Boards
      • News
    • Getting started
    • Introduction video
      Welcome to OpenProject Community
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.

    • Help and support
    • Upgrade to Enterprise edition
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Enterprise support

    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
    Activity
  • Roadmap
  • Work packages
    Work packages
  • Gantt charts
    Gantt charts
  • Calendars
    Calendars
  • Team planners
    Team planners
  • Boards
    Boards
  • News
  • Forums

Content

General discussion
  1. OpenProject
  2. Forums
  3. General discussion
  4. Hiding history clutter

Hiding history clutter

Added by joão Silva about 10 years ago

Hi all,

Is there a way to hide all that history clutter of type, version, progress change and what not to make the discussion about a work package stand out?
I feel that this puts off completely people who don’t come from the redmine/trac background.

If not can it be on your feature list a “hide clutter” button somewhere? Perhaps in the project or user settings?

Best,

João.


Replies (5)

RE: Hiding history clutter - Added by Niels Lindenthal about 10 years ago

Hi João,

very often I feel the same way. There should be some filter so the user can select what kind of changes he wants to see:

In this visual you can seen an early draft of the new work package from build with AngularJS:
http://clients.zzmedia.net/openproject/workpackages/fullscreen/small/

What do you think?

@all: any opinions?

Regards
Niels

RE: Hiding history clutter - Added by joão Silva about 10 years ago

Hi Niels,

It looks much cleaner. But nevertheless I would provide an option to filter all of the automatic messages (progress, type, status, assignee, etc…) and leave only the human made comments visible.

João.

RE: Hiding history clutter - Added by Marcus Liebhardt almost 10 years ago

Fully agreeing with Joao here!
I also like to add that this filter needs to apply to the email notifications as well. It’s easy to miss important work package changes, because of being spam’ed by unimportant changes.

Later on it would be nice, if this filter could be modified in more detail (like advanced settings). That is, one can mark for which property changes messages should been show (and send out).

Niels, the screenshot you provided looks nice. I’m surprised though that although “show comments only” is checked, there are still messages visible, which show the work package’s properties changes (e.g. “status change from new to in development”).

RE: Hiding history clutter - Added by Niels Lindenthal almost 10 years ago

Marcus Liebhardt wrote:

Later on it would be nice, if this filter could be modified in more detail (like advanced settings). That is, one can mark for which property changes messages should been show (and send out).

I agree. This feature will not be implemented with OP 4.2 so we should use the time to come up with a plan.

Niels, the screenshot you provided looks nice. I’m surprised though that although “show comments only” is checked, there are still messages visible, which show the work package’s properties changes (e.g. “status change from new to in development”).
You are right. The visul is inconsistent.

RE: Hiding history clutter - Added by Joan Dooth over 9 years ago

Niels Lindenthal wrote:

I agree. This feature will not be implemented with OP 4.2 so we should use the time to come up with a plan.

Do you already have a schedule or #id for this feature?

  • (1 - 5/5)
Loading...