Targetprocess is an enterprise agile planning (EAP) tool.
- For general information on Targetprocess visit the Technology Help service page.
- For more information on how to use Targetprocess, visit the Targetprocess Self-Help Guide.
Understanding the differences between Jira and Targetprocess
-
Projects vs. Views
-
Targetprocess is an integrated system: when an item is added on one view it will be available and updated on all applicable views. Rather than navigating to a specific project as you did in Jira, in Targetprocess, you will navigate to a view to find the type of content you want to work with, and then filter to see the Team, Portfolio, ART, etc.
-
Refer to Navigate Targetprocess and Save a View or Folder as a Favorite.
-
-
Features and Epics
-
In Jira, Features sometimes were referred to as Epics.
-
In Targetprocess, Epics are UMN Epics and Features are always referred to as Features.
-
-
Assigning Stories
-
Stories can be assigned to multiple individuals.
-
Refer to Assign Work to Team Members.
-
-
Starting or completing an Iteration
-
In Jira, Sprints had to be manually started or completed.
-
In Targetprocess, the Release Train Engineers will define Iteration start and end dates before PI Planning, and they do not need to be manually started or completed.
-
Refer to Move a Story to an Iteration and Create an Iteration Goal.
-
-
Labels and Tags
-
Labels in Jira are Tags in Targetprocess.
-
-
Targetprocess Integrations
-
PIPA will no longer be used for PI Planning, since Targetprocess has this functionality.
-
-
Notifications
-
Currently, Targetprocess does not send any email notifications to users except the initial new account notification. This comes from [email protected].
-