We can say with confidence that issue tracking is useless without the use of issue statuses. Moreover, the more detailed the issue statuses, the more accurate the workflow. On the other hand, too many details can make the working process annoying. Therefore, I believe that choosing the right issue statuses for your processes is extremely important in order for your users to have a good experience with Redmine. In fact, this should be one of the first things that you configure after having deployed Redmine in your organization.
Issue statuses can be managed using the Issue statuses page of the Administration menu. This page is shown here:
Generally, an issue can be open or closed. Therefore, each issue status has a property that determines whether this status makes an issue closed. In the list that is shown in the preceding screenshot, such issue statuses are marked with a check mark 
under the Issue closed column. Also, as you can see, Redmine can have several statuses...