Contextual Menu for Work Plan

What's New

An enhanced contextual menu (right-click on Windows, or secondary click on MAC) for Work Items gives you quick access to common actions, related items, and custom actions.

How it Works

  1. Go to Settings > Profiles, and select the Work Item (for example, Project). 
  2. Expand Actions, and click Edit on Contextual menu - additional Work Plan items.
  3. Customize the contextual menu by adding or removing items.

mceclip0.png

The updated menu

mceclip1.png

 

How to Restrict the Additional Menu Actions

The new contextual menu is enabled by default, and adds additional actions.

Some profiles such as Customer Portal / External Collaborator may not require the additions. 

As an admin, you can remove the additions, either manually by editing the Profile settings, or by completely removing the new menu using css.

Editing the Profile

  1. Go to Settings > Profiles, and open the relevant Profile.
  2. Expand Actions, and on the relevant item, such as Contextual menu, click Edit.
  3. Click on the x to remove an action from the menu.

remove-actions.png

        4. Save your settings.

Remove the Menu Using Custom CSS

  1. Go to Settings > Profiles, and open the relevant Profile.
  2. Expand Settings, and scroll down to Custom CSS.
  3. Enter the following snippet:
    #PreviewPopUpDialogContextMenu {display:none !important;}
  4. Click Save.
Have more questions? Submit a request

Comments

  • Avatar
    Shannon Kirkham

    Like most things published by Clarizen, I have to spend extra cycles determining why, when and how this might be useful to my user community. A use case would go a long way to explain the value of the enhancement, versus instructions to enable/disable.

  • Avatar
    David Goulden

    Shannon - thank you! this is great feedback. We'll incorporate additional use case and value details into the release notes going forward.

  • Avatar
    Rebecca Blonde

    As with each Clarizen release and being an admin I would find it extremely helpful if things were deployed to SBX first so that admins could build any necessary training material or determine if this is something we wanted to disable on release day. It is very difficult to manage when the functionality hits production and our users get functionality we have yet to test or build material around. Advanced notice and putting this in SBX would set admins up for better success and user adoption once things hit production on the release day.