6ef87a2083
Having two states that essentially mean the same thing is very much like
having a boolean "true" and boolean "mostly-true": it's rather silly.
This commit merges the "reopened" state into the "opened" state while
taking care of system notes still showing messages along the lines of
"Alice reopened this issue".
A big benefit from having only two states (opened and closed) is that
indexing and querying becomes simpler and more performant. For example,
to get all the opened queries we no longer have to query both states:
SELECT *
FROM issues
WHERE project_id = 2
AND state IN ('opened', 'reopened');
Instead we can query a single state directly, which can be much faster:
SELECT *
FROM issues
WHERE project_id = 2
AND state = 'opened';
Further, only having two states makes indexing easier as we will only
ever filter (and thus scan an index) using a single value. Partial
indexes could help but aren't supported on MySQL, complicating the
development process and not being helpful for MySQL.
23 lines
628 B
Ruby
23 lines
628 B
Ruby
module Issues
|
|
class ReopenService < Issues::BaseService
|
|
def execute(issue)
|
|
return issue unless can?(current_user, :update_issue, issue)
|
|
|
|
if issue.reopen
|
|
event_service.reopen_issue(issue, current_user)
|
|
create_note(issue, 'reopened')
|
|
notification_service.reopen_issue(issue, current_user)
|
|
execute_hooks(issue, 'reopen')
|
|
invalidate_cache_counts(issue, users: issue.assignees)
|
|
end
|
|
|
|
issue
|
|
end
|
|
|
|
private
|
|
|
|
def create_note(issue, state = issue.state)
|
|
SystemNoteService.change_status(issue, issue.project, current_user, state, nil)
|
|
end
|
|
end
|
|
end
|