-
Notifications
You must be signed in to change notification settings - Fork 4
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
Audits: Owed Payments (Unpaid But Permitted) #4
Comments
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as off-topic.
This comment was marked as off-topic.
Permits on hold? i guess we can close this or too outdated |
It just means generated but not claimed. It's still relevant I think. Unless that was already implemented then yes we can close as unplanned. @FernandVEYRIER rfc |
As of today, we should be seeing these permits as well. I they are not claimed, we should not have any link to the transaction but see the issue. However I don't think there would be any UI difference with the ones not claimed, or if there is no permit at all with the issue. |
You can close as not planned @FernandVEYRIER if you think this is not necessary. |
# Issue was not closed as completed. Skipping. |
A particularly useful feature now that we sort of have permits on hold: the ability to check if a permit was generated but the payout was not claimed yet.
Update Jan 2024:
We have a new column in the database that is meant to store the claim transaction link.
Whenever the user claims using this UI, the UI should write the claim transaction link to the database.
If the value in the database is null then it implies that the permit was not claimed.
The text was updated successfully, but these errors were encountered: