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

Resources != people with email

Added by Frantisek Skuta almost 4 years ago

Hello everyone,

i tried Project Plan and I can't see  away to add a resource that does not have email! (not a person), We have floating departments of "Quality Assurance" for each project but I never know months ahead who those people will be! They can be anyone! + I do not want to collaborate with anyone on this, ...yes I want to share the project online, but I can do it all by myself or on conf calls. Please help! How do I achieve the same freedom of resources adding as in MS Project or teamgantt.com?


Replies (6)

RE: Resources != people with email - Added by Robin Wagner almost 4 years ago

Hello Frantisek,

one of the main benefits of OpenProject compared to MS Project is the ability to work collaboratively very easily. Therefore, you would generally assign users who have an email address.

You can however also create groups (which do not have to be associated with users) and simply assign work packages to those groups. In your example, you could create a group "Quality Assurance" in the administration, assign it to the projects and assign your work packages to the group instead of users. If - at a later point - other users should be working with you (e.g. as part of the QA team), you can simply create an account for them and assign them as members to the group. They will then automatically be notified about any changes made to the work packages assigned to the group "Quality Assurance".

You find instructions on how to create groups here.

Alternatively, you could create a work package custom field to track resources.

RE: Resources != people with email - Added by Frantisek Skuta almost 4 years ago

Hello Robin,

I do not share that opinion. to me, It is limitation. As I stated there GANTT project software (teamgantt) that understands reasons why someone wouldnt want a person with email address to be the only resource. I tried the groups, but that is not a solution as my groups would be empty and I seem to be unable to assign task to empty group.

The alternative path you suggest wouldn't let me make nice reports when more teams are involved, would it?

PS: I am working as sw delivery manager in rather large company with their customs, it is not within my power to force everyone to collaborate on this just because the software wants me to, and it is not my intention to use such software that way. I need MS Project freedom with online sharing capability - nice, responsive public urls :)

RE: RE: Resources != people with email - Added by Frantisek Skuta almost 4 years ago

Hi Robin, sorry i forgot to assin it to project ^^ omg

RE: Resources != people with email - Added by Robin Wagner almost 4 years ago

Hello Frantisek,

ah, ok :)

Does the assignment to groups work for you? I see your point regarding ressources - but maybe empty groups would be sufficient for your use case.

RE: Resources != people with email - Added by Frantisek Skuta almost 4 years ago

Yes, now I am lpoking for some way to share such project plan with public link... :O

RE: Resources != people with email - Added by Robin Wagner almost 4 years ago

Do you want everyone to be able to see the project plan? It is not possible to allow only certain users without an account to access information.

You could make your OpenProject environment publicly accessible - in which case everyone who knows the URL can see the project information. If you would like to enable this, you can go to "Administration" > "System settings" > "Authentication" and uncheck "Authentication required". Next, you can go to the project, go to the "Project settings" and check the "Public" checkbox. Now, everyone who knows the URL can see the public project(s).

Of course there is a risk that anyone can see the information (which is possibly not what you want).

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