Track Issues List in Wrike

We have a process for tracking risk and issues. Everything is entered via a request form and then managed with owners of each risk or issue.

Suggest to define your process. Request forms help keep information standard and your process should take over once captured.

There are two really good use case templates that might fit your need as well:  

https://www.wrike.com/templates/project-risk-analysis/

and

https://www.wrike.com/templates/it-risk-assessment/

With some modification, tweaking - and a request form as Kevin mentions - this might be a good jump start for you!

We have a similar approach here, we have request forms for users to report issues for resolution.

We did start to use it for the UAT of the website. 
Users were reporting issues with the request form which was using blueprints to generate tickets and 'pre-triage' from the options selected in the form, and assign to an individual or team, set a priority, area, etc. Users didn't need to have access to Wrike, since we used the external link for external users.

Wrike has a library of templates that you can probably start from depending on your needs.
This one could be a good start Ticketing and Helpdesk 

I keep an issues list in Wrike. I created a new folder for "Interface Issues" which are basically personal task for myself and another employee. I do have a request form to keep it simple to enter. It creates a task under the folder and the form allows me to easily enter everything needed. Once the issue is marked completed, it automatically goes into the Archive folder under Interface Issues which allows for a look back if needed.

In some projects we do. As other tasks: if these are many small issues a list in a task. If these are big issues (so much work) an issue gets an own task. Decission is most times made by the project manager or the project team.

We sort of track issues using Workflow statuses. Employees have the ability to flag something as "Problem" - for example if this status is used in purchasing it sends an alert to the PM that this could jeopardize their project schedule.

We set up a large request form for all kind of issues and sort them by department. If a user wants to report something, or even needs help, he can use this ticket request form, which creates a task assigned to the responsible manager of the department. We use a custom workflow to track the status. After submission, a ticket hat the status "New", and ist has to be changed to "assigned" after the first review. If this doesn't happen within few days, automation will create an @mention to all followers. We ensure that minimum one responsible manager is auto-following all new tickets.

We created guest-accounts for everyone who doesn't need wrike for daily work, but only for the ticket-system, so that it's possible to communicate within wrike after rasing a ticket.

Our team would get a request about a particular issue and it'll become a project (then tracked by status updates).

I like Shelly Erickson's suggestion of an "Issues" folder!

Shelly Erickson
When you capture issue log on your form, does it replicate same information on the task created in the issue folder? i find mine only capturing the due date, status and name. even the name does tally with what is on the form, rather what is displayed is a log number and Form name... how can i go around this