Projects
Create projects, add members, share personal projects with the organisation, and find your way around a project's tabs.
A project is the unit people and agents work in: one or more repositories, the people on it, its task boards, its memory, and its policy. Workbenches keep a project's id in the repository's .mojoup/project.json (it looks like prj_…), so every workbench that opens one of its repositories joins the same project by itself.
Personal and shared projects
| Kind | Who sees it |
|---|---|
| Personal | A project a workbench registers on its own. Only its owner, and administrators, see it. It has no other members. |
| Shared | A project of the organisation, with members and roles. Its task boards, memory and history are shared with them. |
The Projects view lists the shared projects and the personal ones you can see, with who works on them, which nodes they run on, and when a machine last reported each. A personal project nobody has touched in a month is marked as such.
Projects in a team are the team's projects. Business areas and the portfolio are part of self-hosted AIOE only.
Create a project
Find the project's id
Open the repository's .mojoup/project.json on a workbench that already uses it, and copy the id. Using the same id is what joins the repositories to the project.
Create it
Administrators open Projects, fill in New project (Name, Project id, Owners), and choose Create. In self-hosted AIOE, portfolio managers and area managers can also create an enterprise project in an area from Portfolio.
Add members
Open the project, then Members. Owners add people (and in self-hosted AIOE, groups from your directory), each with a role: Owner, Contributor or Viewer.
Share a personal project (self-hosted)
A personal project can be promoted into a business area without moving anything: tasks, memory, source and history are all kept by the project id, so they come with it.
- The owner opens the project's Overview and asks to share it with the organisation under Share with the organisation, choosing an area and adding a note.
- The area's managers, portfolio managers and administrators are told in their inbox. They accept or reject it under Portfolio, Waiting for a decision, with a reason when they reject.
- The owner may withdraw the request while it waits.
Accepting makes it an enterprise project in that area. The owner then adds members, and the boards are shared with them. Every step is recorded in the project's audit trail.
A project's tabs
| Tab | What is there |
|---|---|
| Overview | Members, repositories, compute and the policy that applies; what needs you; the project's budget (self-hosted); the teams that may run. |
| Inbox | Notices for the project: approvals, promotions, pull requests, budget changes and board changes. |
| Members | The people (and groups) on the project, with their roles. |
| Source | Where the code lives: the connection, organisation and repositories. See Source control. |
| Work | The risks and issues register, and open issues, pull requests and work items from the source. |
| Map | The project's roadmap, plans, architecture and tasks, drawn from what members' workbenches share. |
| Compute | Nodes assigned to the project. Assign more from a node's page. |
| Repositories | The repositories nodes have opened for the project; the owner marks the clone of record. |
| Memory | What the project's workbenches have extracted, its labelling rules, and what it shares with the organisation. See Memory. |
| Policy | Merge rules, settings for this project, tool rules, the project's secrets, and which policy applies. |
| Activity | Runs of agents' work, what happened on the project's roadmap, architecture and boards (each signed by the person it was for), and the project's audit trail. |
Teams in a project
The Teams panel on a project's Overview lists the teams granted to it, and owners choose whether members may also run their own teams and specialists. Workbenches load the granted teams read-only. In self-hosted AIOE, portfolio managers build enterprise teams under Portfolio, Teams, from catalogue roles and skills or people, and grant them to projects and to compute pools. See Catalogue.
Remove a personal project
A personal project's owner, or an administrator, can choose Remove on its page. Its boards, memory and records on the organisation go with it. A workbench that still carries the project id registers it again on its next start.