-
Notifications
You must be signed in to change notification settings - Fork 48
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
Spiff bounties process - Submission #979
Comments
We may want to use the onboarding process that @MarD0607 is developing, piggyback off this. TBD. |
@harmeet-status does this process model fall under one of the current Status process groups? If so, which one? If not, where should it be placed? |
@harmeet-status is this what you had in mind: |
@harmeet-status couple of questions:
|
|
@harmeet-status can we handle ETH address validation by just asking the user to confirm their address or something for the time being? i don't think we are going to have access to the client-side validation library when the process is running. |
Yes that is a good idea to save dev time. |
|
|
|
|
This is ok, run past security. I'm actually considering just sending 1 message, with the secret in the URL. All websites when they get you to confirm the email belongs to you, send you just 1 link to verify. We can follow the same practise, since we no longer allow the user to retrieve an already filled out request, the need to have 2 separate messages, 1 including the link and the other including the password is no longer required. @calexh-sar could you pls update the model to just use the GUID and not required a password |
@harmeet-status we are using the GitHub REST API to check if the requestr is a current collaborator. |
I am following what I understand is the process @MarD0607 established with Status Security Team approval that it is acceptable to send both to the same place, but they should be in two different Discord messages. If you hover over each, you can determine that each is a separate message. The time very well may be the same since they were sent sequentially, but they are distinct. |
@madhurrya or @dinithihj I added some text to display after the initial submission and it is not showing up. I suspect that this feature is not working on the interstitial page when transitioning between Guest User Forms, but not sure. If you haven't already, would you please set up a test process to confirm/refute that this is the issue and if it is, write up an issue for it. |
I am not getting this error. Pls retest and if still getting the error, provide more detail on the steps to reproduce. |
@madhurrya I suspect this issue here is we shouldn't take a Guest user to the Home page since they don't have the rights to do anything there. If @burnettk and/or @jasquat concur, please write up an issue so we can address this. |
@harmeet-status unless you indicate otherwise, I will assume you will be addressing the text related issues 18-22 above. |
Alex, today I got the same error when using the link sent in Discord. Please try with these info |
I added an issue for this #1740 |
Added an Issue for this #1741 |
Done |
@madhurrya regarding #24, the primary reason you were getting this error is because #1320 is a PR, not an issue. In production this should have been caught by the label check since I don't know of any reason a PR would be assigned one of the Bounty labels. But to be safe and thorough, I added a check to make sure the issue requested was a PR with an incorrectly placed bounty label. |
Hi EVERYONE, this thread is getting really busy so if any bugs or improvement are raised and they have been fixed/implemented, then pls go back and |
@harmeet-status is it OK if we create a new ticket for any new issues we find? |
New issues will be added in this ticket #1752 |
We are wanting to do bounties for SpiffWorkflow, using SpiffWorkflow.
Process model: https://cawemo.com/share/29b8873a-8332-42ca-bd75-864bddea8bc4
Process model details: https://www.notion.so/Spiff-Bounties-22a7e2e23ee843c7bffd261ab15d1c9b
The text was updated successfully, but these errors were encountered: