Top Menu

Jump to content
Home
    • Projects
    • Work packages
    • 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
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Professional 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?
      Create a new account

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
  • Roadmap
  • Work packages
  • Calendars
  • Team planners
  • Boards
  • Forums
  • Wiki
    • Table of contents
      • Expanded. Click to collapseCollapsed. Click to showDeveloper
        • Hierarchy leafAccessibility Checklist
        • Hierarchy leafCode Review Guidelines
        • Expanded. Click to collapseCollapsed. Click to showContribution
          • Hierarchy leafGit Workflow
          • Hierarchy leafTranslations
        • Expanded. Click to collapseCollapsed. Click to showDeveloping Plugins
          • Hierarchy leafDeveloping an OmniAuth Authentication Plugin
        • Hierarchy leafRelease Process
        • Hierarchy leafReport a bug
        • Hierarchy leafSecurity
        • Hierarchy leafSetting up an OpenLDAP server for testing
        • Hierarchy leafTheme Features
      • Hierarchy leafDownload
      • Expanded. Click to collapseCollapsed. Click to showFeature tour
        • Hierarchy leafRelease Notes OpenProject 30
        • Expanded. Click to collapseCollapsed. Click to showRelease Notes OpenProject 30 - Overview
          • Hierarchy leafGlossary
          • Hierarchy leafRelease Notes - Accessibility
          • Hierarchy leafRelease Notes - Accessibility changes
          • Hierarchy leafRelease Notes - Add work package queries as menu items to sidebar
          • Hierarchy leafRelease Notes - Copy projects based on Templates
          • Hierarchy leafRelease Notes - Design changes
          • Hierarchy leafRelease Notes - Fixed Bugs
          • Hierarchy leafRelease Notes - Keyboard Shortcuts
          • Hierarchy leafRelease Notes - Project settings
          • Hierarchy leafRelease Notes - Ruby&Rails Update
          • Hierarchy leafRelease Notes - Security
          • Hierarchy leafRelease Notes - Timelines
          • Hierarchy leafRelease Notes - Work packages
      • Hierarchy leafHowto create animated gifs
      • Hierarchy leafMigration Squashing
      • Hierarchy leafMod security
      • Hierarchy leafNew work package page
      • Hierarchy leafOP3 to OP4 Debian upgrade
      • Hierarchy leafOP4 Ubuntu1404 Stable with MySQL in production
      • Hierarchy leafOpenProject 40 Development Setup
      • Expanded. Click to collapseCollapsed. Click to showOpenProject Foundation
        • Hierarchy leafBoards
        • Hierarchy leafMembers
        • Hierarchy leafOPF-Meetings
        • Hierarchy leafStatutes
      • Expanded. Click to collapseCollapsed. Click to showRelease Notes
        • Hierarchy leafOpenProject released on Bitnami
      • Expanded. Click to collapseCollapsed. Click to showRelease Notes OpenProject 40 - Overview
        • Hierarchy leafRelease Notes OpenProject 40 - Accessibility improvements
        • Hierarchy leafRelease Notes OpenProject 40 - Column header functions in work package table
        • Hierarchy leafRelease Notes OpenProject 40 - Improved Design
        • Hierarchy leafRelease Notes OpenProject 40 - Integrated query title on work package page
        • Hierarchy leafRelease Notes OpenProject 40 - Integrated toolbar on work package page
        • Hierarchy leafRelease Notes OpenProject 40 - OmniAuth integration for OpenProject
        • Hierarchy leafRelease Notes OpenProject 40 - Work package details pane
      • Expanded. Click to collapseCollapsed. Click to showSecurity and privacy
        • Hierarchy leafFAQ
      • Expanded. Click to collapseCollapsed. Click to showSupport
        • Expanded. Click to collapseCollapsed. Click to showDownload and Installation
          • Hierarchy leafInstallation MacOS
          • Expanded. Click to collapseCollapsed. Click to showInstallation OpenProject 3 0
            • Hierarchy leafDebian Stable with MySQL in production
            • Hierarchy leafInstallation Ubuntu
            • Hierarchy leafInstallation Windows
            • Hierarchy leafInstallation on Centos 65 x64 with Apache and PostgreSQL 93
          • Expanded. Click to collapseCollapsed. Click to showInstallation OpenProject 40
            • Hierarchy leafOP4 Debian Stable with MySQL in production
          • Expanded. Click to collapseCollapsed. Click to showMigration paths
            • Hierarchy leafFrom Chilliproject to OpenProject
            • Hierarchy leafMigration 15 to 30
            • Hierarchy leafMigration 24 to 30
            • Hierarchy leafMigration Redmine 2x › OpenProject 30
            • Hierarchy leafOpenProject 3 Migration
          • Hierarchy leafOpenProject 40
        • Expanded. Click to collapseCollapsed. Click to showNews
          • Hierarchy leafNew OpenProject Translations Plugin
          • Hierarchy leafNew Plugin on OpenProjectorg Local Avatars
          • Hierarchy leafNew design for OpenProject
          • Hierarchy leafNews Accessibility workshop for OpenProject
          • Hierarchy leafNews Glossary for OpenProject
          • Hierarchy leafNews Heartbleed fixed
          • Hierarchy leafNews Icon Fonts
          • Hierarchy leafNews OpenProject 30 Release
          • Hierarchy leafNews Release GitHub Integration Plugin
          • Hierarchy leafNews Success Story Deutsche Telekom
          • Hierarchy leafNews Timelines
          • Hierarchy leafOpenProject 3013 released
          • Hierarchy leafOpenProject 3017 released
          • Hierarchy leafOpenProject 40 released
          • Hierarchy leafOpenProject 40 will be coming soon
          • Hierarchy leafOpenProject 405 released
          • Hierarchy leafOpenProject and pkgrio
          • Hierarchy leafOpenProject news moved to a new blog
          • Hierarchy leafOpenProjectBitnami
          • Hierarchy leafPackager version with plugins released ("Community edition")
          • Hierarchy leafRegistration OpenProject-Foundation
          • Hierarchy leafRelease OpenProject AuthPlugins
          • Hierarchy leafUpdates on OpenProject
          • Hierarchy leafWe need your feedback for the the new fullscreen view for work packages
        • Hierarchy leafOpenProject Plug-Ins
      • Hierarchy leafWiki
You are here:
  • Forums
  • General discussion

Content

Options for easier membership management?

Added by Brad Smith almost 8 years ago

There are a lot of things I’m liking about OpenProject, but one behavior that keeps proving an obstacle to me is the fact that you can only assign work packages to people who have been designated members of a project. Moreover, it seems that if I add someone as a member of a project, and then create a subproject, they are not treated as members of the subproject. As a result, I have to manually add anyone to whom I might ever want to assign a task to each project. Groups make this a bit easier, but even that is tedious when I have to do it for every (sub(sub(etc)))project.

So, the purpose of this post is first, to check whether I’m missing some option that can make this easier, and if not, to request that such a feature be added or that at the very least that project membership be inheritable by subprojects by default.

Is project membership used for anything other than limiting to whom a task can be assigned? If so, I’d also be curious to know what that is. I can imagine something like an “email all members” feature, but I don’t see one. Even so, an “allow work package assignment to non-members” option would be really great, IMO.

Thoughts?


Replies (4)

RE: Options for easier membership management? - Added by Robin Wagner almost 8 years ago

Hello Brad,

thanks for your post.
You are right: It is only possible to assign work packages to project members.
The reason behind this is that you typically want to limit the number of users who are possible assignees - to make it easier to find the correct users (as well as for performance reasons).
For instance, when creating a work package all project members are shown as possible watchers (check boxes). If all members in the instance would be displayed, it would be quite difficult to find the correct users.

Aside from defining who can be set as work package assignee, responsible or watcher, a project membership - via the assigned role - defines which permissions a user has in the project. (You can find more information in the OpenProject user guide ).

As you mention you could use a group which includes all users in the instance and add this group to all projects (in which case however the users would have the same permissions across all projects).
An alternative may be to copy projects (e.g. via project settings) and select “Members” to be copied as well.

RE: Options for easier membership management? - Added by Brad Smith almost 8 years ago

Thanks for the tip about copying projects. Any chance there might be an option to make subprojects inherit membership from parents? For example, we have a superproject for the development of training content at work, with each course as a subproject. We have a small training team, and everyone should be a member of every project. It would be great if I could just create a group for the training team, make that group a member of the superproject, and have that membership inherit down rather than manually adding the same permission to every subproject or dealing with template projects to copy.

I also feel I must take issue with this statement:

For instance, when creating a work package all project members are shown as possible watchers (check boxes). If all members in the instance would be displayed, it would be quite difficult to find the correct users.

It seems to me that this is limiting functionality to serve an inadequate interface design. In other words, the problem here is not with having a large number of members in a project, but with using checkboxes for this task in the first place. There are many Javascript libraries out there that should make it relatively easy to replace the checkboxes with something more usable and scalable.

For example, here’s one way offered out of the box by jqueryui, or for something more visual, other projects like Moodle and Django use an elegant two-pane selection box like this, and I’m sure there’s a js library out there somewhere that would make something similar easy to implement without coding one from scratch.

Yeah yeah, “patches welcome”, I know, and if I can find the time I’d love to submit one, but in the mean-time I suspect that something like the examples above could be implemented pretty easily by someone familiar with the project, and would both improve the UI and remove an obstacle to better membership management options.

Thanks again for the reply, and sorry for the delayed response!

RE: Options for easier membership management? - Added by Jay Kay over 7 years ago

+1 to an “allow work package assignment to non-members” option.

This is essential for our use case:

- Anyone in our management team can assign a “problem ticket” (a type of work package) to any member of the organisation.
- If we created a group containing all members, and a role where they can view their own “problem tickets”, then that creates a big problem around email notifications. Everyone, by default, will receive everything because they’re now associated with the project.

There’s the possibility that this might also be a bug in the “Only for things I watch or am involved in” email configuration option, but since there is no documentation of that feature (i.e., what does “involved in” mean?), I don’t know whether that’s actually the case.

Either way: I don’t want users to be spammed, but I do want them all to be available for work packages to be assigned to them.

RE: Options for easier membership management? - Added by Catherine G about 5 years ago

Hello,

is there or will there be an option to send an email to all members of one project?
I don’t mean an email notification but an individual mail written by a project member?

Thank you!

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