ambacti
Explore workflows

ISSUE RECORD LIFECYCLE · Workflow idea

Keep project records current without losing human oversight.

When a project issue is created, changed, or removed, prepare the corresponding knowledge-record change for review. Keep issue titles, statuses, and subsequent discussion organized with the matching record, and treat archival as a consequential action that needs explicit approval.

Make it yours See how it works ↓
A Roman aqueduct taking shape from architectural sketch to marble.
A little structure. A clearer outcome.
Starts with
Issue created, updated, deleted, or commented on
Produces
A review item showing the issue details and proposed record action, with creation, updates, and archival awaiting approval.
Category
Reviews & approvals

01 / The starting point

A clear request.
A useful direction.

A new or changed project issue, a later comment, or a request to remove an issue

“Prepare a linked record for a new issue, propose title or status changes, organize subsequent comments, and hold any archive request for human approval.”
An example request · Make it specific to your team.

02 / The work

5 tasks.
One useful outcome.

Helps a project team keep a structured reference to issues and their follow-up while controlling changes to the shared record.

  1. Prepare a record for a new issue

    Gather the issue title, status, link, and stable reference and propose a matching entry for review.

  2. Review title and status changes

    Compare the changed issue with its existing entry and propose updates to the appropriate fields.

  3. Keep subsequent comments with the issue context

    Organize later discussion for the matching issue record and flag comments that may not be suitable for the record’s audience.

  4. Check completion and removal requests

    Show whether the issue is marked done or has been removed, and prepare an archive proposal without treating either event as approval.

  5. Approve each record change

    Have an authorized project owner verify the matching issue and approve creation, updates, or archival before the shared record changes.

03 / The result

Something useful.
Something to build on.

A review item showing the issue details and proposed record action, with creation, updates, and archival awaiting approval.

AmbactiWorkflow folio · 5 steps

Review issue records and comment updates

Reviews & approvals · Example outcome

The handoff

A review item showing the issue details and proposed record action, with creation, updates, and archival awaiting approval.

Keep in mind

Issue details or comments may contain sensitive information, and an issue marked complete is not necessarily ready to archive. Verify the issue key, title, status, links, and comment audience; require an authorized person to approve every cross-system change and archive action.

04 / Make it yours

Set the brief.
Set the standard.

A few choices shape the work around your team.

Prepare the issue reference database

Create fields for completion status, title, status, link, issue ID, and issue key, plus any other reviewed fields the team needs.

Choose issue events and status meanings

Select which issue changes are in scope and agree on how statuses such as To Do, In Progress, and Done are represented.

Set comment, access, and archive rules

Define which comments are appropriate to retain, who can see the database, and who may approve archival.

Test create, update, comment, and removal cases

Use safe examples to confirm the correct record is proposed and that no update or archive action happens before a person approves it.

Put your next idea to work.

Start with your brief. Make the process your own.

Explore more workflows ↗