25 Matching Annotations
  1. Last 7 days
  2. Sep 2026
    1. A work package is the unit of work. Epics, tasks, subtasks, milestones and risks are all work packages with a different type. The table, the Gantt chart, boards, the calendar and the team planner are views on the same records. The type controls which fields you see and which statuses are available. The ID (for example SPIA-14) is permanent and is the safest way to refer to an item in a chat message or a meeting.

      Bug and story are not mentioned what should the reader think abt these? Ignore?

    2. Finding your way in the project list Projects in the global sidebar gives you every project you have access to, with filters for Active, My projects and Favorites. Filter by status: On track, Off track, At risk, Not started. Project status is set by the project lead, not derived automatically. Every project has a short identifier such as IPP, IEME or ERP_LOG. That identifier is what you filter on and what prefixes the work package IDs. Star the projects you use frequently. Favourites appear on Home and on My page, which saves you the navigation every morning.

      I think this should be first part in How our instance is structured Bc its a higher level view than previously mentioned topics.

    3. The consequence for you is simple and it is the one thing worth remembering from this training: an item that is not current in OpenProject is invisible at programme level, no matter how much progress was actually made.

      comments like this maybe could be in bold or even highlighted. Again, would stand out as a key takeaway for the reader.

    4. the number is always a few days old, and whoever assembles it has to interpret what someone else meant

      Add with bullet points or numbered list it would stick out better for the reader

    5. It is not the source of truth for master data, stock or part numbers - that is the ERP system.

      the following points transition into What we track and isnt smooth for the reader