Workflow Details

StatusFlowPro is intuitive and easy to learn. In fact, your users are likely already familiar with the core workflow - Jira's native Linked Issue feature. Here's a typical workflow: 

1. A manager, project lead, user, or other team member creates a set of issues, some of which are dependent upon others.
2. The dependent issues are linked to their predecessor issues using the special sfp-is updated by linked issue type. Similarly, the predecessor issues will be linked as sfp-updates.
3. Users work through the issues as usual and update statuses as appropriate.
4. When a predecessor issue is completed, any issues linked with sfp-is updated by will be moved from their "Backlog" status to "To Do" (or other status as designated in the StatusFlowPro Admin page)

Many other workflows are supported as well.

1. A dependent issue can have multiple predecessor issues. StatusFlowPro will check to make sure all predecessor issues are complete before transitioning the dependent issue.
2. Dependencies are not hierarchical. Tasks or Subtasks can be predecessor issues for an Epic or Story, and the relationship can work in both directions.
3. Any user that has the necessary Jira permissions to link issues can also create dependencies in StatusFlowPro.
4. Dependencies can be created at any time prior to the predecessor issue transitioning to a resolved status.
5. Up to 50 dependencies can be created for a single issue.
6. Dependencies can span multiple epics, sprints, projects, etc., so long as they are within the same Jira instance and permissions are set appropriately.

Workflow Security

Security is fundamental to your business, and to ours. All StatusFlowPro processing is handled completely within your Jira instance. No data is transmitted to Alteris Edge or to any third party as a result of StatusFlowPro.