StatusFlowPro^™ provides an easy way for project and program managers to automate task dependencies without having to hardcode Jira automations. Dependencies can be set as needed, and when the predecessor task is completed, the specified dependent tasks will be evaluated and transitioned from the backlog status to an active status. The automation takes place entirely within your Jira instance - no data is transmitted to Alteris Edge or any third party.

‍

Reduce Friction and Risk

StatusFlowPro helps keep your projects flowing forward, reducing the risk of unnecessary delays and missed deadlines.

• Determine and create dependencies during project creation
• Automate moving dependent issues out of the backlog and into the working queue
• Reduce the daily clutter for your project managers and stakeholders
• Build dynamic and flexible projects without consuming valuable resources building and re-building rigid automations

‍

Workflow Overview (see the Workflow section below for a more detailed discussion of the StatusFlowPro process)

1. Program  managers, project managers, users, etc. designate the dependent tasks for a specific task by creating Linked Issues of the types sfp-updates or sfp-is updated by. This linked issue type is unique to StatusFlowPro, and is required for the app automation to function correctly.
2. Teammates work on the predecessor task as usual. Once complete, they transition the predecessor issue to any resolved status.
3. StatusFlowPro evaluates each linked issue for various criteria (see Evaluation and Automation below) and updates the status of the linked issues as appropriate.

‍

Evaluation and Automation

When an issue is transitioned to the trigger status (usually "Done"), StatusFlowPro performs the following checks:

1. Identify Linked Issues: The app reviews all linked issues and checks if any are of the type sfp-updates.
2. Evaluate Predecessor Issues: For each linked issue of type sfp-updates, the app verifies if there are other related issues that must also be in a resolved status.
3. Transition the Dependent Issue: If all related predecessor issues are resolved, the linked issue is automatically moved from its current status (e.g., "Backlog") to the status specified in the StatusFlowPro Admin Page (e.g., "To Do").

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.

Setting up StatusFlowPro takes only a few minutes. You must launch the StatusFlowPro configuration page at least once before using the app, which will load default settings so it works immediately without further changes. If you’d like, you can also customize these settings to align with your workflows and processes. The configuration page will show a warning if your StatusFlowPro license expires or if any settings are misconfigured.

NOTE: All updates made on the configuration page are saved automatically. You can change any setting at any time, making the configuration simple and flexible.

Configuration Page

In your Jira instance, navigate to Settings -> Apps and click on StatusFlowPro to load the configuration page.

Issue Linking & Issue Link Types (see 1 below)

For StatusFlowPro to function properly, Jira’s issue linking feature must be enabled and a special link type called SFP-Update must exist. If issue linking is disabled, StatusFlowPro will display a notification and include a link to the Jira settings page. Once you enable issue linking, refresh the configuration page and StatusFlowPro will create the SFP-Update link type automatically.

‍Statuses

Use this section to choose which status dependent issues will transition to (assuming all predecessor issue requirements are met). There are two sections:

1. Status Ranking Table (see 2 below): This table gathers all statuses in the To Do category from valid workflows across your Jira instance. Click and drag statuses to reorder them in priority (highest first). When StatusFlowPro transitions a dependent issue, it will pick the highest-priority status that exists in that issue’s specific workflow.
2. Exceptions (see 3 below): If StatusFlowPro finds an exception that matches the issue’s workflow, the dependent issue will be transitioned as defined by that exception. If no exception applies, StatusFlowPro falls back to the status ranking table. To create an exception, select the workflow, pick the status, and click Add. Use Delete to remove an exception from the table.

That’s It!

Setup is a one-time process, or whenever your requirements change. However, be sure to revisit the admin page if you encounter any important messages or warnings indicating that your StatusFlowPro instance needs attention.

‍

Click 'Contact Us' above, or email us at support@alterisedge.com.

‍