Priority Number Configurable | Targetprocess - Enterprise Agility Solution

Priority Number Configurable

automation rule Prioritization

Description The solution sets a Priority Number for any entity type. This makes it easy to understand the priority of an item just by looking at the number. The higher the priority, the lower the number.   Prioritisation can be made

Trusted by Agile teams at show more

Description

The solution sets a Priority Number for any entity type. This makes it easy to understand the priority of an item just by looking at the number. The higher the priority, the lower the number.

 

Prioritisation can be made either inside Portfolio:

... or generally:

Also additional setting is available - prioritisation can be grouped by custom field values.

 

Solution requires pre-setup.

"PNC_1_of_8_Priority Solution Pre-Setup" Automation Rule has to be triggered once to prioritise existing items.

Rule is disabled by default, after configuring it (see below for the options) and launching once, the rule can be disabled.

 

Solution configuration

Entity type

By default the solution will set Priority Number values for Portfolio Epics. To change the target entity type, do the following:

Create a Custom Field for the desired entity type (label: "Priority Number", field type: Number)

Change the rules:

"PNG_1_of_3_Priority Solution Pre-Setup" - at the code line 4, replace the PortfolioEpic to the necessary value:

const commands = [], resourceType = "PortfolioEpic", pluralResourceType = "PortfolioEpics",

At other rules, replace the entity name in condition.

 

Select entities globally or group by Portfolio

Initially there is no filtering - all existing items will be prioritised.

If prioritisation needs to be performed within the portfolios, the following changes should be applied for all 9 rules:

  • Open the Rule - Click the "RAW JSON" button and scroll down - "Parameters" section appears.
  • For the "groupByProject" parameter, change 'false' to 'true'

Group entities for prioritisation by custom field values

In case priority numbers needs to be set separately for some custom field values (e.g. you have "Reporter" custom field with "Internal team" and "External" values and would like to keep priority numbers counted differently), the following setup should be performed:

  • Open the Rule - Click the "RAW JSON" button and scroll down - "Parameters" section appears.
  • Add the custom field name to the "cfGroup" parameter value.
  • Edit the custom field name at "PNC_4_of_9_Update Priority Number when entity CF value is updated" and "PNC_8_of_9_Update Priority Number when entity CF value is updated" rules.
  • Update parameters at all the other rules - change  "cfGroup" value to the custom field name.

Exclude items in certain states

Items in certain states may be not actual for prioritising. By default all the items in initial and final states are not considered, but this is also configurable - excludeInitialState and excludeFinalState properties are responsible for this.

The following changes should be applied for all 9 rules:

  • Open the Rule - Click the "RAW JSON" button and scroll down - "Parameters" section appears.
  • For the "excludeInitialState" and "excludeFinalState" parameters, change 'true' to 'false'.
  • To exclude items with some custom state, add the state name it to "excludeStates" array.

Integrations

See how Targetprocess aligns and empowers business and IT with the help of powerful integrations.

Targetprocess facilitates enterprise agility at all levels by enabling both Business and IT to work in one holistic solution. To help ensure value flow visibility and collaboration across the entire enterprise, Targetprocess allows a powerful set of integrations covering use cases for different levels and roles within organization.

For Transparency above the Team Level 
 
EXPAND 2 INTEGRATIONS

Azure DevOps
Azure DevOps
Add Targetprocess on top of the team level tool: get visibility on Product and Portfolio level.
Atlassian Jira Software
Atlassian Jira Software
Ensure free data flow from Jira to Targetprocess for greater visibility for all team members.

For Continuous Integration and Continuous Delivery 
 
EXPAND 6 INTEGRATIONS

Azure DevOps
Azure DevOps
Automatically associate branches and pull requests with Targetprocess entities
GitLab
GitLab
Automatically link branches and merge requests to Targetprocess entities.
GitHub
GitHub
Automatically associate branches and pull requests with Targetprocess entities.
Phabricator
Phabricator
Link code revisions with any Targetprocess entity.
Bitbucket
Bitbucket
Automatically associate branches and pull requests with Targetprocess entities.
Jenkins
Jenkins
Connect Targetprocess entities with work items, reflect issues back as Bugs or User Stories.

For Product Management, ITSM, Sales and Marketing to Stay on the Same Page 
 
EXPAND 5 INTEGRATIONS

Miro
Miro
Centralize unstructured communication on Miro’s online whiteboard inside Targetprocess.
Microsoft Project Server
Microsoft Project Server
Provide visibility into high-level goals and details about implementation for all teams.
Salesforce
Salesforce
Synchronize customer service, sales, the PM office, and development teams.
Zendesk
Zendesk
Allow all team members to collaborate on shared artifacts from customer service tickets.
ServiceNow
ServiceNow
Collaborate on shared work items, consolidate reporting across the entire organization.

Or contact
a sales representative

Get a live
product demo

Let one of our product specialists create your account
and shape Targetprocess for your company needs.