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

Suggestion: Marge cases on the oldest and close the newest as duplicated #960

Closed
mgabriel-silva opened this issue Apr 24, 2019 · 2 comments · Fixed by #1798
Closed

Suggestion: Marge cases on the oldest and close the newest as duplicated #960

mgabriel-silva opened this issue Apr 24, 2019 · 2 comments · Fixed by #1798
Assignees
Milestone

Comments

@mgabriel-silva
Copy link

mgabriel-silva commented Apr 24, 2019

I don't know about the other users, but for my organization is very common to find duplicates and merge cases.
Creating a new one every time is:

  • taking away the accomplishment of the first one to treat that case, because the merged case owner is the one who merged, not the first to report it
  • unproductive for other reports and sistems that have case numbers
  • not inheriting custom fields from the original cases (this could be another issue by itself)
  • closing both as duplicates, when I believe only the second is a duplicate (generating questionable duplicate count)
  • when merging more than two cases, generating lots and confusing merged cases

Is there a reason not to just merge using the first case and adding the additional information?

@rriclet
Copy link
Contributor

rriclet commented Mar 4, 2021

#1264

@rriclet rriclet self-assigned this Mar 4, 2021
@rriclet rriclet linked a pull request Mar 18, 2021 that will close this issue
14 tasks
@rriclet rriclet added this to the 4.1.0 milestone Mar 18, 2021
@nadouani
Copy link
Contributor

This is part of the new case merge feature in 4.1

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

Successfully merging a pull request may close this issue.

3 participants