Skip to content

applicability for software engineering #1

Description

@gregorynicholas

curious if the current iteration/ roadmap takes into account typical use case for software engineering services.. ok, theres some transactional construct to change a field in some datastore, where one can't proceed on subsequent line items until certain conditions are met.. is there a big step i'm missing?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions