A B C D E F G H I K M N O P R S T U V W
API, also REST API
Service that allows you to view and modify data in your account using a programming interface. Targetprocess has a public REST API available for your needs.
More information: REST API overview
Assignable, entity type
Base entity type for User Story, Task, Bug, Feature, Epic, Request, Test Plan, and Test Plan Run. Every Assignable entity can be assigned to people with different roles, and has a workflow with multiple states.
You can assign User Stories, Tasks, Bugs and other Assignable entities to Project and Team members. Users can see entities assigned to them in their ToDo list views. Assignments can be made under different roles.
More information: Assignments
Audit History, also History audit
Log that contains all information about changed entities (additions, edits and deletions), so you can see who modified what and when.
More information: How to view historical records
A prioritized list of work items, containing short descriptions of all functionality desired in the product.
More information: Backlog overview
Backlog, column in Release Plan and Iteration Plan views
Entities not assigned to any Release or Sprint (Iteration).
Backlog, column in Timeline views
Entities that are neither started nor have planned start and end dates assigned.
Batch Action, also Batch update, Bulk edit
A feature that helps you to perform similar modifications on multiple entities at once.
More information: Batch Actions
Bug or defect (error, flaw, mistake, typo, failure or fault) in a computer program or product. Can be related to a User Story, Feature, Release, and Sprint (Iteration).
More information: Bugs
Helps you to track what has been included in a specific software build. Use relations to link User Stories, Features, Bugs, etc. to a Build.
Burndown Chart, also Burn Down Chart
A graphical representation of how work progresses over time. In Targetprocess Burndown charts, time remaining is shown on the vertical axis of the chart, while the timeline is shown on the horizontal axis.
More information: Burndown Chart for Release and Sprint
Business Value, also Priority
Business Value indicates the importance of work items from the customer’s point of view. All most valuable tasks should be implemented first if possible. Examples: Must Have, Average, Nice to Have.
More information: Business Value
Capacity, also People Capacity view
A view that shows project members and the work items assigned to them. It calculates each user's total effort to-do vs. available allocated work hours.
More information: People Capacity in Release / Sprint / Team Iteration
Capacity, limit in Sprints (Iterations) and Team Iterations
Cloud, also Hosted in the cloud, formerly known as On-Demand
Targetprocess can be hosted in cloud. Team and Company pricing plans allow you to use shared cloud hosting, whereas an Enterprise plan allows you to order a private cloud environment.
A short piece of text that can be posted by any user to almost any entity. Comments allow users to communicate with each other and discuss work on the project. You can @mention other users to quickly notify them about important things.
Company, entity type in Data Model
Entity that allows private communication with your clients within a common Service Desk or Help Desk Portal. Requesters (clients) from Company A cannot see Requests (tickets) from Company B.
More information: How to manage Requests by Companies
Extra fields that can be added to your entities to help gather, store, and organize data. Examples: Text, Rich Text, Drop Down List, Multiple Selection List, Number, URL. You can create Custom Fields for almost any entity. Most Custom Fields are configured per process. There are static fields that you set manually and calculated ones that are automatically updated by Targetprocess.
More information: Custom Fields
Metric that measures how long it takes to complete a task from the time that actual work on it begins.
More information: Lead Time and Cycle Time
A set of widgets, views, and reports grouped on a single page. Provides a brief overview of the current state of progress at various levels.
More information: Dashboards
A structure that describes what types of entities exist in the Targetprocess system. It also defines properties that entities have, and hierarchical relations between them.
More information: Data model and hierarchy
Remove something from your system. Instead of deleting Projects and Users, we recommend making them inactive so that they can be activated back when needed.
A value that shows how long a task is going to take. Effort is measured in Ideal hours or abstract Points. This value is entered manually when the entity is estimated, and can be updated later.
More information: Effort
A widget that allows you to bind content from external pages and documents to Targetprocess entities.
More information: Embedded Pages
Entity, also General entity type in the Data Model
An object that represents an item in the Targetprocess database. Work items (User Stories, Tasks, Bugs, Features, Epics etc.), planning items (Projects and Teams, Releases, Sprints), and Users are all entities.
A high-level scope of work which may contain Features. An Epic is always a part of some single Project. In most cases, Epics are required for large and medium Projects. In small Projects, Epics are optional. Epics can be assigned to a Release.
More information: Epics
How long will it most likely take to complete a task. Giving an estimation to a work item in Targetprocess means updating its Effort field manually. Planning poker is one of the recommended methods for collaborative estimation.
Extracting data from Targetprocess. It is possible to export reports to CSV files, and use API to retrieve data in JSON or XML format.
More information: How to export data into a .CSV file
A Feature is a high-level requirement. Features are always a part of some single Project. In most cases, Features are required for large and medium Projects; in small projects, features are optional. A Feature is larger than a User Story, and one Feature may contain several User Stories. Features can be assigned to a Release.
More information: Features
A rule that shows, hides, or highlights data, such as specific entities, cards, and lanes in views and reports.
A feature that allows a user to subscribe to a specific entity and receive digests about changes and updates related to it by email.
More information: Follow / Watch entities
A chart heavily used in traditional project management. There are no Gantt charts in Targetprocess, but Timeline views serve a similar purpose and can help you plan your work over time.
More information: How and when to use a Timeline view (and not a Gantt chart)
Help Desk Portal
Old standalone application that was used for communication with external requesters (clients) within requests (tickets) and integrated into Targetprocess. Replaced with Service Desk.
More information: Help Desk Portal vs Service Desk: what is the difference?
Standalone entity that represents an issue, obstacle, or force majeure circumstances. Can be related to other Targetprocess entities.
More information: Blockers and Impediments
Feature that allows you to quickly create or migrate large amounts of data into your Targetprocess account. Imports can be done within CSV files, Quick Add Several Work Items Mashup and REST API queries.
More information: How to migrate or import data to Targetprocess from other project management system
Inbound Email Integration plugin, also POP email integration, IMAP email integration
A scheduled automatic service that retrieves emails from your inbox on a regular basis and creates Requests, Requesters, and Comments in Targetprocess based on the emails.
More information: How to set up Inbound Email Integration
A helpful feature that allows a Project Manager to assign users to a Project or Team membership list and send them an emailed invitation at the same time.
More information: Invite Users
Iteration, an entity type in the Data Model
A method for work management which balances demands for work with the available capacity for new work. In Targetprocess, work items are visualized as cards. All members of project teams can have a transparent overview of flow and progress, from task definition to customer delivery. Team members "pull" work as capacity permits, rather than work being "pushed".
A board view that displays the current workflow of any (or all) of your team's projects. States of the workflow are shown as columns, and work items are distributed by them in the form of cards. Kanban board views in Targetprocess also support drag and drop actions, classes of services, and WIP (Work-In-Progress) limits.
Mashups are custom add-ins and extensions for Targetprocess. They help to tweak built-in features, add new controls, widgets and reports, hide redundant fields, and slightly modify existing actions and workflows. Many Mashups can be installed from the Mashups Library.
More information: Mashups Overview
Milestone, entity type in Data Model
Milestones are used to represent some important event for your team, project or company. For example, it could be an important demo for a client, or a company deadline. Milestones are managed on Timeline views and can be displayed in Dashboard widget as well.
More information: Milestones
A module that sends messages and alerts to the responsible people when some important events and changes with data in the system happen. In Targetprocess, there are email notifications of multiple sources: the ones configured in Process Workflow settings, Following (subscription), and @mention notifications. Push notifications sent into mobile client apps are also supported.
More information: Notifications
Owner, field of entities in the Data Model
A user who created an entity. Administrators and users with roles having special permissions can change owners of entities.
More information: Owners of entities
Owner, of a view, report or dashboard
A user who created it and who can manage its settings. Administrators can manage objects and change owners for them.
Data and views showing people and their project allocations on a timeline view. It allows you to see and manage how many projects a person is allocated to, when they are allocated, and what availability they have both currently and in the future.
More information: People Allocations Management
Restriction on add, edit and delete actions. Permissions are specified per Role and Entity type. For example, you may prohibit QA engineers from deleting Bugs and Time records. View permissions inside a Project are provided to all project members.
More information: Roles and Permissions
Project Portfolio management (PPM) provides program and project managers in large organizations with the capabilities needed to manage the time, people, tasks and budgets necessary to meet company objectives. Targetprocess solutions cover many different aspects of Portfolio Management.
Prioritization, also Prioritize
A common task for a Project Manager or Product Owner. It helps set execution order in which the team should implement stories and fix bugs. When you reorder entities using drag and drop, the order of tasks in ToDo list views of team members follows your changes. The saved order (aka Rank, aka Numeric Priority) is global within the whole system.
More information: How to prioritize entities
Priority, field of entities in the Data Model
See Business value.
Process, entity type in Data Model
In Targetprocess it is a set of rules used to model your actual process. It includes terminology, workflows, practices and custom fields. Different departments in the company may follow different processes. Each project is binded to a single process.
More information: Processes and Workflows
A group of projects with something in common or a large product divided into smaller sub-projects. This could be a set of product components, projects for specific customers, or any other grouping. Helps to organize the work and track progress better.
More information: Projects and Programs
Represent a set of work that needs to be completed. Think of it as a product or a project within your company. Usually created as a high level idea first and managed as a portfolio item later. Every work item should be added into some single project. Project members are people assigned to it. They can view all entities inside a project.
Relation, entity type in Data Model
Dependencies between any entities in Targetprocess. They provide additional visibility in terms of requirements, or implementation and delivery order. In the meantime they do not support strict constraints, limits and progress calculations. The relations can be identified as Dependency, Relation, Link, Duplicate or Blocker at your discretion. Relations have directions and can be Inbound or Outbound.
More information: Relations
Release, entity type in Data Model
Represent a phase of a project. Releases help to organize functions that should be shipped into meaningful groups, plan ranges of delivery dates for them and track the progress of implementation. In Targetprocess there are cross-project Releases and the ones that are related to the single project. Latter ones can be splitted into smaller Sprints (Iterations).
A view that extracts your data and present it in the scrutinized form. Reports are used for keeping track of information and participate in decision-making process. There are Visual reports and Tabular reports in Targetprocess. Most of them are view-only and do not allow to modify data. Reports can be printed and exported.
Request represents requirement or feedback from external users or stakeholders (Requesters). Example: Issue, Idea, Question. Used for issue management, idea tracking and requirements traceability. Requests may be added from different sources: registered manually, created by Inbound Email Integration plugin or submitted within Service Desk and Help Desk portal.
More information: Requests, Requesters and Votes Count
Person who sends a Request or votes for it. Requesters can be registered from different sources: added in Targetprocess, within self-signup form in Service Desk, and automatically created from sender email address by Inbound Email Integration plugin. Unlike the number of active users, number of requesters is not limited by count of purchased licenses.
More information: Requests, Requesters and Votes Count
Permissions for users to add, edit, and delete entities in Targetprocess are managed on a per-role basis. Each user has a default (system) role, plus a specific role for each particular projects and teams he or she is a member of. Example: Developer, QA Engineer, Project Manager, Product Owner.
More information: Roles and Permissions
A process framework for running Agile software development projects at scale. Targetprocess, as a visual and flexible software tool, can provide you with the technical platform needed to implement and support SAFe® in order to scale Agile at all levels of your company.
A framework within which people can effectively deliver products. Contains different roles, artifacts, events and interaction rules. Targetprocess solutions support many different aspects of Scrum process. Iterative development is a key one: incremental product improvements such as user stories and bug fixes are delivered within regularly repeating cycle of Sprints (Iterations) or Team Iterations.
A feature that helps to find an entity by keyword, combination of words, or ID number quickly. The Search box can be found in the top menu. For advanced queries over your data create and use filtered views instead of Search.
More information: Search
Module that provides the complete feedback loop between project development team and external users such as customers or stakeholders. It displays Requests (Service Desk tickets) and related backlog items. Service Desk serves as a replacement for Help Desk Portal.
More information: Service Desk overview
Defines how serious an impact of a bug is and how badly it affects the functionality. For example, Blocking, Critical, Small.
More information: How to customize Severity values for bugs
Split, an action on entities
A manual action that allows to split a large work item (such as user story or feature) into two smaller ones.
More information: Split Entities
Split, an option in Finish action
Semi-automatic splitting of partially done user stories can be done when your Sprint (Iteration) or a Team Iteration is near its finish. It allows you to keep complete tasks in the current Sprint and carry incomplete work into the next one.
More information: Finish Action for Iterations and Team Iterations
Sprint, also Iteration, entity type in Data Model
Short period of time (typically 1-4 weeks of developer time) during which planned work should be developed, tested, and demonstrated. It results in an increments of product functionality. A Sprint (Iteration) is part of a project Release and can contain work only from one project. Within regularly repeating cycle it is recommended to create Sprints of equal duration.
More information: Iterations (Sprints) and Team Iterations
Tabular Report, formerly known as Custom Report
Table form report. Reports engine allows building your own custom reports based on almost any entity type. You can select columns, apply filtering conditions, sort and group records, set sorting and grouping of results, add summary columns, export and print your data.
More information: Tabular Reports
Tags can be attached to entities. It helps to introduce custom categories and organize your data better.
A small chunk of work, typically less than 16 hours. Tasks are technical steps that are taken to complete and deliver the user story. The smallest increments of work. In Targetprocess tasks cannot exist outside user stories. It is recommended to split a user story into several tasks when the story is quite large and should be implemented by two or more people.
Group of people that work together. Functional teams organize people working on the same area of the application (Backend, Frontend, Mobile etc.). Cross-functional teams group people who work on a part of larger project or work on multiple projects in the same time. Team entity helps to grant users with access permissions only to the information that is relevant to them. Also it helps to track overall progress of a team as a single business unit.
More information: Teams
Team Iteration, also Team Sprint, entity type in Data Model
Time-based scope of work that is similar to Sprint (Iteration), but is not related to a project or a release directly. A team iteration is related to a single team and can contain work items from many different projects and releases.
More information: Iterations (Sprints) and Team Iterations
See Team Iteration.
A feature that helps to map states of workflow of a specific team to the ones in a global project workflow. It becomes useful when teams prefer their own way to work on items. This allows teams to follow their real life workflows, and help project managers easily digest the progress across all the teams not being confused about each team’s specific workflow.
More information: Project and Team Workflows overview
Template, of a View or a Report
Predefined setup of a view or a report. May include selection of cards (data source), lanes (rows, columns, axes), filters, visual encoding rules and other pre-configured options.
More information: Creating Views from Templates
Template, list of entities
Predefined list of entities (such as Tasks or Test Cases) that can be created with single click whenever needed. Helps to save time, for example in the case when all your user stories always contain same set of similar tasks or tests.
More information: How to prepopulate a User Story with Tasks based on a template?
Name of an entity type in Targetprocess such as User Story, Bug, Feature, etc. These predefined types can be manually renamed in the settings of the Process your Project follows. It provides additional flexibility with customization of terminology used in your system.
More information: How to customize the terminology for entities
An entity that contains detailed description how to test some specific functionality and verify that it works the way it was designed. May contain list of steps and expected results. In Targetprocess test cases are organized into test plans.
Test Plan, also Test Suite
An entity that groups test cases. Tests in test plans can be reused: each test case may be included in as many test plans as required. Test plans in Targetprocess are hierarchical. Every entity can have associated test plan. To track quality changes over time you may run the same test plan multiple times and have historical run results stored.
Time, entity type in Data Model
Record about spent and remaining hours and (optionally) short text description what part of task was exactly done that is submitted by users who work on entities. Helps to gather accurate statistics on the added time and export the data. Requires Time Tracking practice to be enabled.
More information: Adding and tracking Time spent
Time Sheet, also Timesheet
Interactive view that allows to see all entities you or other user worked on recently and amount of time spent submitted per each task daily. New Time entities can also be registered in this view.
More information: Time Sheet
Timeline, also Timeline view
A view that displays cards on a time scale. It helps to plan and track work in matter of time. Timeline is powerful for portfolio management, roadmapping, release and iteration planning, tracking allocations of teams and people.
More information: Timeline view mode
Anybody who needs access data in Targetprocess. Every user has first and last name, email, password. Users are assigned to projects, teams and work items under different roles. Besides the roles, the permissions of the users are also granted with global access level settings that can be one of the following options: regular Users, Observers, Contributors, Administrators.
A piece of work that helps to implement some business requirement and deliver value. It should try to capture a single functionality, enhancement, use case, scenario or role. Can be split to smaller Tasks, and can be part of some larger Feature.
More information: User Story
Velocity, also Capacity of Sprints (Iterations) and Team Iterations
Total story effort - the number of points or ideal hours - you can complete in a Sprint (Iteration) or Team Iteration is your team's velocity. Velocity reached in previous sprint or iteration can be set as capacity limit for the next one. Average velocity is a useful long-term predictor rather than a predictor of what a team may complete in exactly the next iteration.
More information: Iteration Velocity
An interactive page that displays entities and allows you to open and modify them. In Targetprocess, there are Board, List, One-by-one, Timeline views. On every view it is possible to configure and customize cards (data source), lanes (rows, columns, axes), filters, visual encoding rules and other options. Views can be organized into folders. List views can be added to dashboards. List of views is shown on the left side in Targetprocess main screen.
More information: Board, List and Timeline View modes
A feature that allows you to quickly recognize items by their visual attributes, such as color, size, shape, and so on. In Targetprocess, you can configure multiple filtering rules in order to highlight entities with different colors.
More information: Visual Encoding
Reports that display data in a visual way, such as charts and trendlines. Reporting in Targetprocess is now done via built-in integration with Vizydrop, our free data visualization software. There is a comfortable drag-n-drop interface for reports creation, a powerful formulas editor for custom calculations, the ability to aggregate fields, add annotations and milestones, compare and explore data, and dig down for low level details. Visual Reports serve as a replacement for Custom Graphical Reports.
More information: How to use the Visual Reports Editor
A script that allows you to subscribe for events when data in Targetprocess changes and send remote calls to external applications or back to Targetprocess itself. Helpful for creating various integrations.
More information: Webhooks
A sequence of states and transitions an entity needs to pass through before it is done. States may vary depending on entity types, e.g. you might want a “Design” state for a User Story but not for a Bug. Each process can have a custom workflow. To modify states of entities in a Project, edit the workflow of the process this Project follows. Functional teams can have their own Team Workflows.
More information: Project and Team Workflows overview