Project template, established to serve as a pattern for reference, can help you make the best use of the knowledge base, standardize the business management and enhance the work efficiency.
Dynamsoft Issue Tracking Anywhere provides two different project templates:
These two project templates both contain Bug, Feature and Task as the default issue types, but based on different workflows with different philosophical approaches to software development. When you create a new project, by default you can choose between the two different project templates. The Project Template for small teams is optimally designed for small projects on a rapid delivery schedule, while the Project Template for larger teams is designed for large software development teams that have long software development cycles.These templates shape how the project is set up.
The following figures or tables will show you some features in the Project Template for small teams:
Project Template for small teams Features
| Users/Groups | Permission |
| Administrators (Group) | Delete Issues Edit Issues Manage ProjectManage Public Queries View Issues |
| Everyone (Group) | Delete Issues Edit IssuesManage Public Queries View Issues |
Bug/Feature/Task
| Name | Description | Type | Field Rules |
| Assigned To | This field identifies the person that the issue is currently assigned to. | User | AllowedValues: all members in the current project |
| Attached File Count | This field identifies the count of the attachment files to an issue. | Integer | None |
| Changed By | This field identifies the person who changed a created issue. | User | None |
| Changed Date | This field identifies the time when an issue was changed. | DateTime | None |
| Comment | This field provides a comment of an issue. | HTML | None |
| Created By | This field identifies the person who created an issue. | User | None |
| Created Date | This field identifies the time when an issue was created. | DateTime | None |
| Description | The description provides an area to describe the problem and the steps to reproduce it. | PlainText | None |
| ID | The ID provides a unique indicate of an issue in ITA. | Integer | None |
| Issue Type | This field identifies the type of the issue. | String | None |
| Priority | The priority is a subjective importance rating. | String | AllowedValues: High, Low, Medium,
Unknown, Urgent Default Value: Urgent |
| Project | The Project is the one which the issue belongs to. | String | None |
| Rev | This field identifies the version of an issue. | Integer | None |
| State | This field identifies the state of the issue. | String | None |
| Title | The title provides a concise overview of the issue to be completed. The title should be descriptive enough to allow the team to understand what area of the product is affected and how. | String | Required |
| Name | Value |
| State | Active, Resolved, Closed |
| Transition | No defined transitions. |
The following figures or tables will show you some features in the Project Template for larger teams:
Project Template for larger teams Features
| Users/Groups | Permission |
| Administrators (Group) | Delete Issues Edit Issues Manage ProjectManage Public Queries View Issues |
| Everyone (Group) | Delete Issues Edit IssuesManage Public Queries View Issues |
Bug/Feature/Task
| Name | Description | Type | Field Rules |
| Activated By | This field identifies the person who activated an issue. | User | None |
| Activated Date | This field identifies the time when an issue was activated. | DateTime | None |
| Assigned To | This field identifies the person that the issue is currently assigned to. | User | AllowedValues: None |
| Attached File Count | This field identifies the count of the attachment files to an issue. | Integer | None |
| Changed By | This field identifies the person who changed a created issue. | User | None |
| Changed Date | This field identifies the time when an issue was changed. | DateTime | None |
| Closed By | This field identifies the person who closed an issue. | User | None |
| Closed Date | This field identifies the time when an issue was closed. | DateTime | None |
| Comment | This field provides a comment of an issue. | HTML | None |
| Created By | This field identifies the person who created an issue. | User | None |
| Created Date | This field identifies the time when an issue was created. | DateTime | None |
| Description | The description provides an area to describe the problem and the steps to reproduce it. | PlainText | None |
| ID | The ID provides a unique indicate of an issue in ITA. | Integer | None |
| Issue Type | This field identifies the type of the issue. | String | None |
| Priority | The priority is a subjective importance rating. | String | AllowedValues: High, Low, Medium,
Unknown, Urgent Default Value: Urgent |
| Project | The Project is the one which the issue belongs to. | String | None |
| Reason | The reason an issue is in the current state. For example, an issue can be in the Active state because it needs to be fixed. | String | None |
| Resolved By | This field identifies the person who resolved an issue. | User | None |
| Resolved Date | This field identifies the time when an issue was resolved. | DateTime | None |
| Rev | This field identifies the version of an issue. | Integer | None |
| State | This field identifies the state of the issue. | String | None |
| Title | The title provides a concise overview of the issue to be completed. The title should be descriptive enough to allow the team to understand what area of the product is affected and how. | String | Required |
| Name | Value | Field Rules |
| State | Proposed, Active, Resolved, Closed | None |
| Transition | ->Proposed |
|
| Active->Closed |
|
|
| Active->Resolved |
|
|
| Closed->Active |
|
|
| Proposed->Active |
|
|
| Proposed->Closed |
|
|
| Resolved->Active |
|
|
| Resolved->Closed |
|
Using Dynamsoft Issue Tracking Anywhere > Projects (Project Templates) Management > Project Template Overview