| |
Change Management - Project Tracker |
|
|
|
|
|
| |
Active/inactive |
|
|
|
Parameter that determines if an item is available for use. |
|
| |
| |
Assign |
|
|
|
Associating a user with an artifact through the "assign" user attribute. |
|
| |
| |
Attachment |
|
|
|
Files can be attached directly to artifacts. |
|
| |
| |
Attribute |
|
|
|
Attributes are associated with artifact types within projects and are used to define artifacts. |
|
| |
| |
Attribute group |
|
|
|
Attributes associated with an artifact are organized within attribute groups. |
|
| |
| |
Comparative analysis report |
|
|
|
A report that provides a snap shot of a single point in time. |
|
| |
| |
Defect |
|
|
|
Artifacts identified within existing feature/functionality. |
|
| |
| |
Comparative analysis report |
|
|
|
A report that provides a snap shot of a single point in time. |
|
| |
| |
Feature |
|
|
|
New functionality to be incorporated into the project. |
|
| |
| |
Global attributes |
|
|
|
A set of predefined attributes available for association with all projects. |
|
| |
| |
Artifact type |
|
|
|
All project tracker processes are performed within the realm of an artifact type. Artifact types are comprised of a unique set of attributes, attribute options, artifacts, templates, queries and reports. |
|
| |
| |
Rate of change report |
|
|
|
A report that tracks changes to artifacts over a period of time. |
|
| |
| |
Report |
|
|
|
To track the progress of your project. |
|
| |
| |
Query |
|
|
|
Allows you to search for artifacts within the database. |
|
| |
| |
Template |
|
|
|
A set of values for quick access and use while creating artifacts. |
|
| |
| |
User attributes |
|
|
|
User attributes are used to associate users with artifacts |
|
| |
| |
Use as identifier |
|
|
|
A text field used as an artifact identifier. This is displayed alongwith the Artifact ID in the Project Tracker page and as the subject line in all communication generated due to changes or comments in the artifact. This attribute value is used as the link to view the artifact contents and in email notifications that are sent when the associated artifact is edited. |
|
| |
Project Management |
|
|
|
|
|
| |
Reporting |
|
| |
| |
Chart format |
|
|
|
Display format for a Point in time chart. Formats available: Vertical bar - side by side, Vertical bar-stacked |
|
| |
| |
Filters |
|
|
|
Attributes corresponding to the selected artifact type(s). If you selected multiple artifact types, the common attributes are displayed. Filters available: State attribute filter and Attribute filter |
|
| |
| |
Grouping |
|
|
|
Grouping attributes for a Point in time report |
|
| |
| |
Point in time report |
|
|
|
Shows status at a particular moment. For Project Tracker, each stack or cluster represents an artifact type or an attribute option. For Subversion, each stack or cluster represents a Subversion operation or filedownloads count or users or projects in a domain. |
|
| |
| |
Time frame |
|
|
|
Reporting time span for a Trend report |
|
| |
| |
Trend report |
|
|
|
Displays activity over a period of time. For Project Tracker, each trend line represents an artifact type. For Subversion, each trend line represents a Subversion activity like commit, download, checkout and so on. |
|
| |
| |
Project Dashboard |
|
| |
| |
Actual date |
|
|
|
Task actual date provided by the project members assigned to individual tasks. |
|
| |
| |
Actual effort |
|
|
|
Actual view provides the manager the ability to explore the data that has been entered by the resources. |
|
| |
| |
Historical variance |
|
|
|
Indicates the variances between planned and actual dates through the life of the project plan. |
|
| |
| |
Milestone performance |
|
|
|
Shows the planned and actual dates of milestones and the difference in workdays within the project plan |
|
| |
| |
Planned date |
|
|
|
Task planned date defined by the project plan |
|
| |
| |
Planned effort |
|
|
|
Planned view contains only the plan efforts for all the tasks in the table with the chosen time scale across all resources for that project |
|
| |
| |
Project performance |
|
|
|
Shows three meter bars representing the variances between planned and actual Effort, Schedule, and Progress %. |
|
| |
| |
Report timeframe |
|
|
|
Allows you (using Date pickers) to select the start and end dates of your report. Selecting this will help you delineate the temporal periphery of the project effort report that you wish to see. |
|
| |
| |
Status reminders |
|
|
|
Status reminders are sent to all the members of a project at the end of the reporting period. |
|
| |
| |
Watch list |
|
|
|
Provides a console for you to watch the status and progress of the projects you choose to oversee. |
|
| |
Application Lifecycle Management |
|
|
|
|
|
| |
ALM Template |
|
|
|
A starting point for new project workspaces. Using a project template significantly reduces setup time by providing a standard baseline that can be adapted for specific needs. |
|
| |
| |
Project Content Editor |
|
| |
| |
Page |
|
|
|
A top-level screen that you can add to your project |
|
| |
| |
Subpage |
|
|
|
A secondary level screen you can add as a subdivision to a page based on how you have organized your activity |
|
| |
| |
Freeform page |
|
|
|
A secondary or tertiary level screen you can add as a subdivision to a page or a subpage where you can organize information and tasks pertaining to the particular page that represents an activity in your project |
|
| |
| |
Activity table |
|
|
|
A component of your page, subpage or freeform page that allows you to add a pre-defined panel and displays a set of standard links within this panel that you can customize to meet the needs of your project. You can customize these links to allow you to view active and historical work items in a project |
|
| |
| |
HTML component |
|
|
|
The HTML component allows you to add HTML content directly to a page. You can edit the HTML source on the screen by adding, modifying or deleting tags using the wysiwyg editor |
|
| |
| |
Documents component |
|
|
|
The Documents component allows you to upload any document that you may require for monitoring the progress of the project. You can provide links to various files. |
|
| |
| |
Metrics Report |
|
|
|
the Metrics Report component types allow you to display graphs of Project Tracker reports generated using the Tracker Metrics tool. You can define two types of reports: Trend, Point in time |
|
| |
| |
Milestones table |
|
|
|
The Milestones table displays the milestones in a project plan that you have uploaded into Project Dashboard. To be able to see this table, your project has to have Project Dashboard enabled and a valid Microsoft Project plan file with proper allocation of tasks to resources, uploaded into your project. |
|
| |
| |
Project Tracker query |
|
|
|
This Project tracker query component contains links to project tracker queries and allows you to view the query results from within the project pages. The component uses the existing queries you have already setup in Project tracker. |
|
| |
| |
Subprojects |
|
|
|
If your project has subprojects, then they are displayed on the project home page. |
|
| |
Collaboration Tools |
|
|
|
|
|
| |
Announcements |
|
| |
| |
Headline |
|
|
|
A title or headline for your announcement |
|
| |
| |
Original article URL |
|
|
|
A URL link to the original article |
|
| |
| |
RSS feeds |
|
|
|
You can send announcements to an Really Simple Syndication (RSS) reader |
|
| |
| |
Discussion Services |
|
| |
| |
Content in Email |
|
|
|
A choice that lets your decided whether subscribers will receive messages with the entire content of the text displayed in the email body or just a link to the message within the discussion |
|
| |
| |
Discussion |
|
|
|
An electronic meeting place where users may carry on asynchronous discussions on topics of interest to the community. Discussions may be unmoderated, trusted or moderated; providing project owners with the right level of oversight for each discussion's mission. |
|
| |
| |
Footer |
|
|
|
Text to be displayed at the bottom of every message posted to the discussion. For example, consider adding instructions on how to subscribe or unsubscribe here. |
|
| |
| |
Guest posting |
|
|
|
Allows anyone to post a message to the discussion, even if they do not hold an account in the domain. |
|
| |
| |
Message |
|
|
|
Messages are either topic-defining messages having a unique subject, or replies to a pre-existing discussion topic. Messages may be posted to a discussion via the web user interface and also by email. |
|
| |
| |
Moderation |
|
|
|
The process whereby designated moderators decide whether to allow or reject a given message posting. Moderation may be done via the web interface and also by email. Only Moderated and Trusted Discussions utilize moderation. Moderators may post to moderated and trusted discussions without moderation. |
|
| |
| |
Notification |
|
|
|
Email messages that are sent to subscribers as a result of new messages being posted to a discussion. Subscribers may select message-by-message notification, daily digest notification and also start-page-only notification. |
|
| |
| |
Subscriber |
|
|
|
A user who has expressed interest in a particular project discussion by subscribing to it. Subscription requires that the user have view permission for the discussion. Guest users may subscribe anonymously to discussions to which they have this permission. |
|
| |
| |
Subscription -Anonymous |
|
|
|
Permits guests who do not have an account on the domain to subscribe to discussions. |
|
| |
| |
Topic |
|
|
|
The first message in a collection of messages about a given topic of discussion. The subject of the topic should clearly state the intended scope of the ensuing discussion. |
|
| |
| |
Trusted |
|
|
|
A new type of discussion that somewhat parallels the 'discuss' form of mailing list. Trusted discussions are moderated discussions where certain individuals may be designated as being 'trusted' to post without moderation. As with other access rights, the 'trusted' designation comes in the form of a trusted permission in the project permissions system. |
|
| |
| |
User |
|
|
|
A registered user in the domain of a CollabNet Enterprise Edition site. Users have various permissions that allow them to perform actions on a project's tools and artifacts. Guest users are unregistered users that may be given limited access by domain administrators. |
|
| |
| |
Wikis |
|
| |
| |
Wiki |
|
|
|
A Wiki is a collection of pages that can be collaboratively edited using a web browser |
|
| |
| |
Template |
|
|
|
A page created using a wiki template will have a structure similar to others of the same type. |
|
| |
| |
InterWiki link |
|
|
|
Links to something outside your wiki, as with HTML tags |
|
| |
| |
SlideShowHandOutTemplate |
|
|
|
Creates slides and runs your presentation |
|
| |
| |
Macros |
|
|
|
Macros allow the insertion of system features into normal wiki pages |
|
| |
| |
Orphaned pages |
|
|
|
A list of pages no other page links to |
|
| |
| |
Parsers |
|
|
|
Parsers go through the contents of a page to create a sequence of formatter calls which in sequence create some readable output. |
|
| |
| |
Category |
|
|
|
A category is a WikiName that uses reverse linking: if you click on the title of a category page, you'll get a list of pages belonging to that category |
|
| |
| |
Access Control Lists |
|
|
|
When Access Control Lists, or ACLs for short, are turned on, you will be able to control who may do what on or with a wiki page. Using ACLs in wiki includes a control line at the top of the page you want to control |
|
| |
| |
Actions |
|
|
|
Actions are tools that work on a page or the whole wiki, but unlike macros do not add ''to'' the page content when viewing a page, but work ''on'' that page content. They either produce some output based on page contents (navigational actions like searching) or implement functions that are not related to viewing a page (like deleting or renaming a page) |
|