title: Entity Relationship Diagram: Can someone verify my ERD?
body: <p>I have made an ERD diagram (well kind of as it doesn't adhere to all the principles of an ERD diagram).</p>
  <p>Following are the requirements:</p>
  <ol>
  <li>Manager/user can have many projects</li>
  <li>The user can enter many bugs</li>
  <li>A bug has a creator(user)</li>
  <li>A bug has a developer who'll solve the bug(user)</li>
  <li>A bug belongs to a project</li>
  <li>A project can have many users</li>
  <li>A project can have many bugs too.</li>
  <li>The bug has a descriptive title and deadline and a screenshot, type, and status</li>
  <li>Screen shot should be an image either .png or .gif no other type of image is allowed.</li>
  <li>Description and the screenshot is not compulsory but title and status and type are compulsory.</li>
  <li>The title of a bug should be unique throughout the project</li>
  <li>Type can have two values (feature, bug)</li>
  <li>Status is a drop down having values (new, started, completed) if it's a feature or (new, started and resolved) if it's a bug.</li>
  </ol>
  <p><a href="https://i.stack.imgur.com/4dYhH.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/4dYhH.png" alt="ERD Diagram" /></a></p>
  <p>Here is my understanding.</p>
  <ol>
  <li><p>There is a User table that will contain the (unique) ID (I may use UUID for that), Username, Email, UserType (Enum: Manager, Developer, QA), and encrypted User password.</p>
  </li>
  <li><p>A User can have multiple projects so that's why it has 1:Many relationships with the table Project. This table will have a unique Project ID, Manager ID (The creator of the project), and a project title.</p>
  </li>
  <li><p>I'm thinking of creating a 3rd table i.e. Working On, which will keep track of which user is currently present under the project (Requirement 5). Project ID and User Id, both will be FKs from respective tables and their combination will make a Primary Key. Is this approach feasible?</p>
  </li>
  <li><p>Each project can have multiple Bugs, so 1:Many relationships will be defined between Project and Bug. Bug ID will be the primary key.</p>
  </li>
  <li><p>Each bug can have an optional set of screenshot(s) (Max 10), which I'm thinking of storing in another table Screenshots. Its primary key will be composed of BugId and ImageID.</p>
  </li>
  </ol>
  <p>Can anyone please go through this logic and help me in identifying any errors in this approach? It is very important that I correctly categorize my databases so that implementation in Ruby on Rails becomes easier.</p>