Set Issue Defaults for a Project
You can set default values for issues for a project to help you and your collaborators select the right details when creating issues. All collaborators can override defaults on individual issues.
- The default recipient based on the issue type.
- The default number of days to respond to an issue or override the default based on priority.
- The default issue type for issues created by a collaborator.
You can also select the option to have issue numbers automatically generated from this page. See Automatically Number Issues for a Project.
- From the home page, under Projects, select the name of
the project you want to open.Alternatively, go to the main menu in the upper left-hand corner, select Projects, and then select the name of the project you want to open.The Dashboard for the project appears.
- From the upper right-hand corner of the page, click the settings icon , and then select Project Settings.
- Click on the Issues tab.
- In the Default Responsible Party: by Issue
Type area, select the default recipient or group for each issue
type.Note: Distribution groups are not available for this option.
- In the Standard Distribution Language section, you can add text to be added to all email notifications or generated PDFs when the issue is closed.
- In the Default State for Editors section, select a state that will be used as the default setting when a project editor role creates a new issue for the project. Note that you can still select other states when creating a new issue.
- Set the default days to respond to an issue.
- Select the Enable Default Days to Respond check box to have Viewpoint Team™ automatically calculate the due date.
- In the General Default field, enter the default number of days to respond to an issue.
- To override the general default based on priority, use the Low, Medium, or High priority fields to enter the default number of days to respond to an issue.
- In the Restrict Role: By Issue Type
section, you can restrict a project role to an Issue type and change the access
level for that role.Note: By restricting a role to an Issue type and setting the access level, you can you can both prevent that role from having access to any other Issue type, and also give that role greater permissions for that specific Issue type than the role would have by default.
In the following example, the Subcontractor role is configured to view and create Issues with the "Weather" type. This also means Subcontractors cannot view or create any other Issue type.
- Click the plus sign .
- From the drop-down menus, select a Role, Issue Type, and corresponding Access level.
- Click Save Changes.