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

[P4] Prepare for use of future landcare APIs #36

New issue
Open
opened 2022-10-17 10:39:50 +13:00 by alistairmcintyre · 1 comment
alistairmcintyre commented 2022-10-17 10:39:50 +13:00 (Migrated from gitlab.catalyst.net.nz)
Copy link

Landcare APIs provide different soil data, Wilfred would like to eventually use those

Landcare APIs provide different soil data, Wilfred would like to eventually use those
alistairmcintyre commented 2022-10-17 10:47:24 +13:00 (Migrated from gitlab.catalyst.net.nz)
Copy link

changed title from [4] Prepare for use of future landcare APIs to [{+P+}4] Prepare for use of future landcare APIs

changed title from **[4] Prepare for use of future landcare APIs** to **[{+P+}4] Prepare for use of future landcare APIs**
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#36
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?