Issues

Follow these conventions when creating a new issue:

A) Regular Issue:

1. This the story SHORT title.

2. This the story ID.

3. The story description and should be 'h1' tagged.

4. 'Success Scenario' in 'h2' tag and the scenario points MUST be tagged as a list.

5. The same as the success scenario.

6. Labels: the initial labels are: Component-'Number'. Points-'Number' Priority-'High, Medium, Low' Status-new When you start working change the 'Status-new' to 'Status-inProgress' and comment that you have changed it.

7. Sprint: choose the story's sprint.

8. Assignee: your name

If you do not want to write the tags, you can go to the above issue and click 'Edit' in the red box, copy and paste to your issue and then modify the content to match your story.

B) Database Issue:

This issue is created whenever something related to the database is needed. To create a database issue, follow these steps:

1. 'Database - [Option]' Should be the title.

2. Option can be one of the following: Add, Modify, Delete, Question Add: When you need to add a table or a relation. Modify: When you need to change some table or attribute. Delete: If you think a certain attribute is not needed. Question: If you can not understand what a certain attribute is for.

3. 'Database' should be the label.

4. Choose the current sprint you are working on.

5. Assign Our DB admin Ahmed Magdi 'ahmed93' to the issue.

6. Tag the DB admin.

7. Whatever you need, separated as points.

C) Class Diagram Issue:

This issue is created whenever something related to the class diagram is needed. To create a class diagram issue, follow these steps:

1. 'Class Diagram - [Option]' Should be the title.

2. Option can be one of the following: Add, Modify, Delete, Question Add: When you need to add a new method, variable and so on to the class diagram. Modify: When you need to make any modification to something already existing to the class diagram. Delete: When you need to delete something that is no longer needed. Question: If you have any inquiry in the class diagram.

3. 'ClassDiagram' should be the label.

4. Choose the current sprint you are working on.

5. Assign our Class Diagram owner Ahmed Elassuty 'AhmedElassuty' to the issue.

6. Tag the class diagram owner.

7. Whatever you need, separated as points.

D) Reopened "Fixing" Issues:

This is how to fix an old closed issue. Create a new issue with the following conventions and work on the same old branch but this time reference the new created issue in the commits.

1. Title: Fix: 'Brief description of the fix' |
2. Old Story: 'Name' - Story 'No.'
3. Labels: Those are the labels corresponding to the new fixing story added to the sprint backlog.
4. Original issue number in bold.
5. Briefly describe the steps you did in the fixing process.