lightweight/right-tree
1
0
Fork 0
Code Issues 17 Pull requests Projects Releases Packages Wiki Activity Actions

[P1] Allow users to download the user/planting guide for a payment #41

New issue
Open
opened 2022-10-17 10:43:52 +13:00 by alistairmcintyre · 14 comments
alistairmcintyre commented 2022-10-17 10:43:52 +13:00 (Migrated from gitlab.catalyst.net.nz)
Copy link
No description provided.
alistairmcintyre commented 2022-10-17 10:46:30 +13:00 (Migrated from gitlab.catalyst.net.nz)
Copy link

changed title from [1] Allow users to download the user/planting guide for a payment to [{+P+}1] Allow users to download the user/planting guide for a payment

changed title from **[1] Allow users to download the user/planting guide for a payment** to **[{+P+}1] Allow users to download the user/planting guide for a payment**
alistairmcintyre commented 2022-10-17 11:15:35 +13:00 (Migrated from gitlab.catalyst.net.nz)
Copy link

We don't handle any Credit Card data. This ticket represents integration with an existing payment provider. Wilfred would need to set up an account and provide us the access to interface with it.

Would we also need a method to cache the result so that a customer has access to their planting guide in perpetuity?

We don't handle any Credit Card data. This ticket represents integration with an existing payment provider. Wilfred would need to set up an account and provide us the access to interface with it. Would we also need a method to cache the result so that a customer has access to their planting guide in perpetuity?
alistairmcintyre commented 2022-10-17 11:16:17 +13:00 (Migrated from gitlab.catalyst.net.nz)
Copy link

changed time estimate to 2d 4h

changed time estimate to 2d 4h
mattn commented 2022-10-19 10:47:13 +13:00 (Migrated from gitlab.catalyst.net.nz)
Copy link

Wilfred is heading away to decide on a payment service provider.

We've decided we'll use their API to secure the planting guide and distribute this via email so that we don't have to also define an access control system with users etc. which would blow out our time estimate.

Wilfred is heading away to decide on a payment service provider. We've decided we'll use their API to secure the planting guide and distribute this via email so that we don't have to also define an access control system with users etc. which would blow out our time estimate.
mattn commented 2023-03-01 13:19:35 +13:00 (Migrated from gitlab.catalyst.net.nz)
Copy link

assigned to @mattn

assigned to @mattn
mattn commented 2023-03-06 18:11:03 +13:00 (Migrated from gitlab.catalyst.net.nz)
Copy link

mentioned in commit 959c41c21d

mentioned in commit 959c41c21d83557ceae565da7ac07f52b1a20d11
mattn commented 2023-03-06 18:23:45 +13:00 (Migrated from gitlab.catalyst.net.nz)
Copy link

mentioned in merge request !47

mentioned in merge request !47
mattn commented 2023-03-06 18:26:05 +13:00 (Migrated from gitlab.catalyst.net.nz)
Copy link

mentioned in commit 49b502899ce0db1909805c9a2ddcf0fc62a839ec

mentioned in commit 49b502899ce0db1909805c9a2ddcf0fc62a839ec
mattn commented 2023-03-06 18:28:28 +13:00 (Migrated from gitlab.catalyst.net.nz)
Copy link

mentioned in merge request !48

mentioned in merge request !48
mattn commented 2023-03-09 17:00:54 +13:00 (Migrated from gitlab.catalyst.net.nz)
Copy link

mentioned in commit fe10cc8171

mentioned in commit fe10cc8171ce777c55196ac84affd40e0b03e695
mattn commented 2023-04-20 15:42:01 +12:00 (Migrated from gitlab.catalyst.net.nz)
Copy link

mentioned in commit 13c8436d98

mentioned in commit 13c8436d98b7063052537cbd8385e03440b4ecf6
mattn commented 2023-04-20 15:42:01 +12:00 (Migrated from gitlab.catalyst.net.nz)
Copy link

mentioned in commit d39e7da6f1

mentioned in commit d39e7da6f1bfd7ecc3fad6a26b821ffa8473cab9
mattn commented 2023-04-20 15:42:56 +12:00 (Migrated from gitlab.catalyst.net.nz)
Copy link

mentioned in merge request !56

mentioned in merge request !56
mattn commented 2024-10-17 11:36:31 +13:00 (Migrated from gitlab.catalyst.net.nz)
Copy link

unassigned @mattn

unassigned @mattn
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
v1.0.1
No results found.
Labels
Clear labels   
Bug

A software bug we've noticed. (These may not necessarily be show-stoppers)

  
Client: Biosphere Capital

   
Client: Central Hawkes Bay District Council

   
Client: Forward Works Viewer

   
Client: Kea/Kākā Databases

   
Client: Otorohanga District Council

   
Stage: Blocked

Something is causing us to be unable to currently fix this issue.

  
Stage: Doing

An issue that's assigned and being worked on

  
Stage: Peer review / Staging

An issue waiting to be given the all clear for production deployment.

  
Stage: Ready

For tickets that have been quanitifed, have acceptance criteria, and can be safely moved to the To Do column.

  
Stage: UAT AT

Work waiting to be deployed to production.

No labels
Bug
Client: Biosphere Capital
Client: Central Hawkes Bay District Council
Client: Forward Works Viewer
Client: Kea/Kākā Databases
Client: Otorohanga District Council
Stage: Blocked
Stage: Doing
Stage: Peer review / Staging
Stage: Ready
Stage: UAT AT
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: lightweight/right-tree#41
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?