Skip to content
This repository was archived by the owner on Mar 13, 2025. It is now read-only.

Duplicate created when reopening #391

Closed
jmgasper opened this issue Apr 6, 2021 · 4 comments
Closed

Duplicate created when reopening #391

jmgasper opened this issue Apr 6, 2021 · 4 comments

Comments

@jmgasper
Copy link
Collaborator

jmgasper commented Apr 6, 2021

Interesting bug in TCX today:

  1. Created an issue with a title/price and added label OpenForPickup
  2. I added you as the assignee
  3. I closed the issue without adding Fix Accepted
  4. TCX said it wasn’t paid out because the Fix Accepted label wasn’t added
  5. I reopened it, Added the Fix Accepted Issue, and Closed it (pretty quickly)
  6. TCX created a new issue
  7. I reopened the issue, removed Fix Accepted, Re-added Fix Accepted, Closed it.
  8. It closed the 2nd issue. 1st issue is still in draft
@anonymousjaggu
Copy link
Collaborator

@jmgasper I have also faced this issue

reopen.issue.mp4

@jmgasper jmgasper added this to the Bug fixes - June 2021 milestone May 17, 2021
@afrisalyp
Copy link
Collaborator

@jmgasper

When we close an issue without tcx_FixAccepted, we'll update the challenge with Canceled status.
And we won't use the record again if we re-open the issue. So that's why topcoder-x will create a new challenge.
That's the current behaviour.

There are three conditions that lead to the cancellation process after closing an issue:

  1. The issue has no tcx_FixAccepted.
  2. No price or the price is 0.
  3. The issue has tcx_Canceled label.

What should we do to fix this issue?

@jmgasper
Copy link
Collaborator Author

jmgasper commented May 30, 2021

Can we remove condition 1? I think if we do that, that'll be enough.

@afrisalyp
Copy link
Collaborator

@jmgasper

Sure. Thanks.

@jmgasper jmgasper closed this as completed Jun 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants