Closed tickets continue appearing as opened

"sysadmin.caos" <[email protected]>
Newsgroups gmane.comp.otrs.user
Message-ID <[email protected]>
Hello,

I manage a OTRS-5 (5.0.11-01) server that, I don't know why, when I 
close a ticket, it continues appearing as a "open ticket" in "Tickets -> 
Status". However, in a fresh installation of OTRS-6 (6.0.1-02), doing 
the same process with a received ticket, it appears as "Closed" in 
"Tickets -> Status".

In my OTRS-5, some month ago I created some new status "progeso-25%, 
progeso-50%, progeso-75% and progeso-90%". A member of this mailing list 
told me maybe the problem was that my new status contained "%" and "%%" 
is the separator character between history steps in each ticket, so I 
decided to disable that status and create new ones as "progreso-25, 
progreso-50, progreso-75 and progreso-90". However, closed tickets 
continue appearing as opened tickets in my OTRS-5.

Now, for preparing this mail, I have installed a OTRS-6 system. There, I 
have created a new status called "Medias". I have created a new ticket; 
then, I have changed its status from "New" to "Media" and, then, from 
"Media" to "Closed". In this case, ticket appears as closed.
This same scenario has been copied in my OTRS-5 running system. I have 
created another new status "Medias", I have created a new ticket, 
changed its status from "New" to "Media" and, then, from "Media" to 
"Closed". In this others case, ticket continues appearing as OPEN.

I don't know where is the problem... My screenshots are located at 
https://aomail.uab.es/~druiz/ (I would like to attach them, but message 
size limit is too small). I have not found any possible reason...

I need help, a lot of help...

Thanks!

---------------------------------------------------------------------
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/mailman/listinfo/otrs
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.