Redmine

*h1. Wiki

*h2. Structure*

*h3. Categories/Top Level Projects*

* All top level projects are currently used as categories to more easily sort and manage them with inheriting members and finding projects that fall under said category would be sub projects.

h3. Issues/Tasks/Tickets

* Issues vary based on department and what each has access to. 

** Some departments will have a pool of tickets that Individual Contributors can pull from and assign themselves to and work on the ticket through completion/rejection.

** Some departments will have tickets directly assigned to users from the Director, Project Manager or Manager level based on a person's specialties or time availability

** IT specifically will also have a ticket system managed by @msessions@labattleship.com where tickets are submitted through an online portal then assigned based on which IT member has the permissions/tools/time necessary to resolve the issue. These may be reassigned as things change.

h2. Roles and Permissions

h3. Executive:

* Able to view basically everything

* No permissions to interact 

h3. Director:

* Can create top level "projects" that we currently use as categories

* Can do almost anything within a project other than delete issues, notes, and the project itself to maintain integrity

* Can manage users with a role below them (Managers, Individual Contributor, Project Unassignable User)

* Can do anything with workflow (how the status of a ticket can change from one status to another, most users will have a specific order the ticket status can change so Directors will be able to override if there are issues)

h3. Project Manager:

* Same permissions as a Director but cannot create top level projects/categories

* Multiple managers may be in a project but the long term goal will be to have only 1-2 PM's per project as we clean things up on each existing project and create new projects as they will be the head/main contact and would likely be given the more training in regards to redmine to ensure they can help /direct users as need be

* Can manage users with a role below them (Managers, Individual Contributor, Project Unassignable User)  

h3. Manager:

* Can create subprojects and configure them

* Can manage members

* Has full permissions with tickets/issues other than deleting them to keep record and integrity

* First role with restrictions on ticket/issue status flow so you cannot go straight from a new ticket to closed. (the ticket must be assigned then closed so we know who worked on/completed the ticket and situations of that nature.) 

!clipboard-202411131407-5yzsy.png!

h3. Individual Contributor:

* Primarily made for the average user of redmine to work on tickets/issues

* Can only see projects they are assigned to

* Can claim tickets/issues to work on as well as reject/close them as necessary

* Ticket status flow is more restricted to avoid issues with a ticket being closed early or re-opening a ticket without manager approval and things of that nature

!clipboard-202411131407-lqtti.png!