Feature Tracking: Stakwork Common Workflow Plumbing

[humansinstitute]

Context

Hive Process will integrate Stakwork Workflows and automation into the Hive Development Process. This will reduce workload on Product Managers by streamlining creative tasks and automating the drafting of product artefacts and audit tasks.

Feature: Common End Point for Stakwork Calls

Feature Brief:

Through the Hive Process we will be integrating Stakwork Workflows with the Bounties Program. The first instances of this were the User Story generation, but the implementation is specific. To speed up deployment of new features we will build a generic endpoint on Sphinx Tribe Server to process and submit all of these requests and track their progress.

This will include queuing and processing for both sending and requests, via common flexible objects to

User Stories:

As a product manager, I want to simply integrate a new stakwork workflow into the Hive Process quickly and easily. As a senior engineer, I want to ensure I have clean, simple to maintain code, with reusable functions where possible.

Features:

All queries from the Front End app that require a Stakwork Workflow will utilise a common endpoint All queries from the Front End app that require a Stakwork Workflow will utilise a common request object to the end point to avoid changes. All requests will be logged in a tracking table in the DB All responses from Stakwork to the Tribes server will be received by a common end point Responses should be queued and then processed to make the required updates.

[humansinstitute]

Feature Tracking: issues won't be assigned as work.