Separate Requests and Issues as different objects

[#1]

Description - I would love for requests and objects to be separate objects. We currently use a request queue for projects, but I am exploring issues and how this could work to track unplanned work while working on a project. We report on how many requests we receive a month, it would not make sense for issues to be included in this. 

Why is this feature important to you - To show the different types of unplanned work. I think it would be helpful to show issues that come up on projects in reporting to better allocate resources and help with future planning.

How would you like the feature to work - I would like them to be separate objects.

Current Behaviour - Requests and issues are considered the same object.