# Issue name

* Related Issues: _#IssueNumber if necessary_

## Introduction

A short description of what the features or the bugs are. Try to keep it simple and within a
single-paragraph.

## Issue Description

Describe the bug found or the feature that you are proposing.

If it's completely new feature explain why this new functionality is necessary, and propose some advice for the development (or just open a Pull Request if you have already started to work on the feature on your own).

## Steps to reproduce issue

If the bug is complex to describe, show how developers can reproduce it (using code snippet, database data, etc...) and describe its drawbacks.

## Expected behaviour

Explain what is the expected behaviour of a program while using the code related to this issue.

## Actual behaviour

Explain what is the actual behaviour of a program and what are the actual errors while running the affected code.

* Related Issues: _#IssueNumber if necessary_

## Introduction

_A short description of what the features or the bugs are. Try to keep it simple and within a single-paragraph._

## Issue Description

_Describe the bug found or the feature that you are proposing._

_If it's completely new feature explain why this new functionality is necessary, and propose some advice for the
development, or just open a Pull Request if you have already started to work on the feature on your own._

## Steps to reproduce issue

_If the bug is complex to describe, show how developers can reproduce it using code snippet, database data, etc..._

## Expected behaviour

_What is the behaviour that you were expecting after following the steps outlined above?_

## Actual behaviour

_What behaviour did you get instead?_

Remove Name from issue template
Remove Name from issue template

- This isn't necessary since it's already in the title.

Also formats the various section tips with italic font to make it
easier to spot that it's not user written text.
