Web: Build - Resurface Issue To the top when Expiration has been Extended

[PixelantDesign]

Description

As a user I want to see issues at the top If no one has started work and the expiration has been extended.

Definiton of Done

• [ ] Build in logic to make an issue refresh and display at the top of the issue explorer if the issue time frame has been extended.

Please review with @pixelantdesign @vs77bb

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

__This issue now has a funding of 0.17 ETH (33.48 USD @ $196.96/ETH) attached to it.__

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
  
  
  
  • Want to chip in? Add your own contribution here.
  
  
  • Questions? Checkout Gitcoin Help or the Gitcoin Slack
  
  
  • $31,025.34 more funded OSS Work available on the Gitcoin Issue Explorer
  
  

[PixelantDesign]

@mul1sh let us know if you have questions!

[PixelantDesign]

@willsputra this is related to what you're designing!

[mul1sh]

@PixelantDesign will do, 🙂 thanks

[mul1sh]

@PixelantDesign between newly created issues and issues where the expiration has been extended, which should take the highest precedent i.e. should newly created issues appear higher in the list than the extended expiration or vice versa?

[PixelantDesign]

@mul1sh Let's order it based on time.

Example:
If I create a new issue and then I extend an expiration on a different issue.
The extended expiration should go to the top.

It would be great if we could give the recently updated items a color overlay and fade it out after 5-10 seconds after the page loads using this color #ECF5FF. See below.

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

__The funding of this issue was increased to 0.4 ETH (82.62 USD @ $206.54/ETH) .__

• If you want to claim the bounty you can do so here
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $27,505.92 more funded OSS Work available on the Gitcoin Issue Explorer

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

__The funding of this issue was increased to 0.4 ETH (82.62 USD @ $206.54/ETH) .__

• If you want to claim the bounty you can do so here
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $27,505.92 more funded OSS Work available on the Gitcoin Issue Explorer

[mul1sh]

@PixelantDesign thanks for the feedback 🙂 , implementing it like this then

[vs77bb]

@mul1sh Excited to see what you come up with here!

[gitcoinbot]

@mul1sh Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] warning (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[mul1sh]

@gitcoinbot just finishing testing my changes and then I commit in less than 5 hours 😄

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

__Work for 0.4 ETH (83.32 USD @ $208.3/ETH) has been submitted by__:

1. @mul1sh

@PixelantDesign please take a look at the submitted work:

• PR by @mul1sh

---

• Learn more on the Gitcoin Issue Details page
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $23,064.02 more funded OSS Work available on the Gitcoin Issue Explorer

[rmshea]

Hey @PixelantDesign, looks like @mul1sh has submitted and is ready to be reviewed. :)

[PixelantDesign]

Thanks for the reminder @ryan-shea

@mbeacom good to pay this out?

[mul1sh]

@PixelantDesign sorry for closing but i've re-opened the PR here again https://github.com/gitcoinco/web/pull/2279

[PixelantDesign]

Hi @mul1sh how is this going?

[mul1sh]

@PixelantDesign also wrapping it up now, thanks

[PixelantDesign]

Thanks @mul1sh, would it be possible to try to get this merged in the next day or so?

cc @SaptakS for pr review when it's ready.

[mul1sh]

@PixelantDesign yes it is, I've made the required changes to the PR, so i'm basically re-basing it with master and fixing the merge conflicts and then I push it for review

[PixelantDesign]

Thanks!

[mbeacom]

Looks like the PR needs adjustments based on @pinkiebell's review comments and the merge conflicts resolved.

Then it should be ready for final review/merge.

[mul1sh]

@mbeacom yeah true 🙂, though i'm having a some issues sorting the conflicts after a rebase master, in fact thats the only thing holding me back now. So once i do a clean rebase i'll update this PR.

[PixelantDesign]

The PR was closed, is there a new PR we should track @mul1sh?

[mul1sh]

@PixelantDesign I re-opened the PR here #2279 sometime back, so i've been trying to sort out the merge conflicts and then i push it for review

[PixelantDesign]

Thanks for the update @mul1sh, would it be possible to get the conflicts resolved by early next week?
cc: @pinkiebell

[PixelantDesign]

Closing this since we're mostly working on the PR now.

[mul1sh]

@PixelantDesign sure I intend to actually get the conflicts fixed today

Closing this since we're mostly working on the PR now.

Ok cool, i'll alert you in the PR to test when its ready

[kuhnchris]

@PixelantDesign did this got reopend on purpose?

[thelostone-mc]

Ah @kuhnchris I guess this was opened on 21st July!
This has been fixed over at https://github.com/gitcoinco/web/pull/5012

This is duplicate issue https://github.com/gitcoinco/web/issues/4744 (well the other one is the duplicate but yeah )