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

Expired Status == Open Status? #637

Closed
e-n-l opened this issue Mar 17, 2018 · 6 comments

Comments

Projects
None yet
4 participants
@e-n-l
Copy link

commented Mar 17, 2018

Description

I noticed that this issue is showing up in the Issue Explorer when the Open status filter is on, but it's actually expired:

image

@thelostone-mc

This comment has been minimized.

Copy link
Member

commented Mar 17, 2018

Not sure why this is happening -.-

Duplicate one : https://gitcoin.co/issue/codesponsor/web/10?gc2
Expired one : https://gitcoin.co/issue/codesponsor/web/10

screenshot_20180317-113709

@thelostone-mc

This comment has been minimized.

Copy link
Member

commented Mar 17, 2018

Could it be because the bounty was republished for a higher amount ?

@e-n-l

This comment has been minimized.

Copy link
Author

commented Mar 17, 2018

Interesting... the duplicate still shows as expired, at least for me:
image

I'm using FireFox 59.0.1, although I see the same thing in Chrome 65.0.3325.162.

@thelostone-mc

This comment has been minimized.

Copy link
Member

commented Mar 18, 2018

@mbeacom any idea why this might be happening ?

@mbeacom

This comment has been minimized.

Copy link
Contributor

commented Mar 19, 2018

The dockerize bounty is indeed a recreated bounty. The original was cancelled. @e-n-l Thanks for reporting this. The bounties are technically two unique bounties. Something odd occurred when @coderberry created the first bounty, so he had to cancel and recreate it.

@owocki

This comment has been minimized.

Copy link
Member

commented Mar 19, 2018

just went in and set the old bounty as current_bounty=False so hopefully thatll stop it from showing up twice in the future...

not sure if we need a fix it twice here or not. if not, ok to close this issue?

@e-n-l e-n-l closed this Aug 9, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.