Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reopened Tickets Still Showing Resolver #1819

Open
televandalist opened this issue Sep 2, 2023 · 3 comments
Open

Reopened Tickets Still Showing Resolver #1819

televandalist opened this issue Sep 2, 2023 · 3 comments
Labels

Comments

@televandalist
Copy link
Member

Describe the bug
If a ticket is reopened, it will still show the resolver.

To Reproduce
https://retroachievements.org/ticketmanager.php?i=39049

Expected behavior
Resolver should be blank

Screenshots
a

Additional context
I guess in a way, it would be useful to see who had been working on a ticket, kind of like "participants" on a GitHub issue, but I doubt this is intended behavior.

@MSGoodman
Copy link
Contributor

Looking at the code, I'm surprised this happened. In ticket.php's updateTicket there is this code, which should explicitly set the ResolvedByUserID to null if the ticket is moving out of the Resolved or Closed states:

    if ($ticketVal == TicketState::Resolved || $ticketVal == TicketState::Closed) {
        $resolvedFields = ", ResolvedAt=NOW(), ResolvedByUserID=$userID ";
    } elseif ($ticketData['ReportState'] == TicketState::Resolved || $ticketData['ReportState'] == TicketState::Closed) {
        $resolvedFields = ", ResolvedAt=NULL, ResolvedByUserID=NULL ";
    }

    $query = "UPDATE Ticket
              SET ReportState=$ticketVal $resolvedFields
              WHERE ID=$ticketID";

Do we have a newer example where someone hasn't already resolved the ticket?

@wescopeland
Copy link
Member

@Jamiras With the latest round of tickets changes, might this be resolved?

@Jamiras
Copy link
Member

Jamiras commented May 11, 2024

I don't think anything in the latest round of ticket changes affected this behavior.

The audit log for the affected ticket shows a reopen happening in 2021, so I think this was actually fixed by #1258 (which happened after 2021, but before this issue was opened).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants