When adding or editing an issue type, you will be presented with a range of settings.
Note that if you are creating a new issue type, it will not be associated with any projects until you create one or more status and manually select the starting status for each project!
Issue Type Key - this is simply a unique identifier for the type that is used internally. It will not be exposed anywhere directly. It may only include letters, numbers, and underscores.
Display Order - sort order for the issue types. Lower numbers will be displayed first.
Filename for Icon - you may enter the path to an image to use as an icon for this type. This path should be relative to your status icon directory, which defaults to images/statusicon. Three issue type icons are included with the Project Tools:
pt_type_bug.png,
pt_type_feature.png, and
pt_type_task.png.
Base Permissions off of Existing Type - you can choose to copy the permissions from an existing issue type to ease setup. This option will only be available when creating an issue type. If you do not select a type, no users will be able to access this type until you manually setup its permissions.
You can also select the wording for a number of different areas, based on the issue type. Examples are provided for the "Bug" issue type.
Singular Form - issue type name in singular form.
Example: Bug.
Plural Form - issue type name in plural form.
Example: Bugs.
Vote Question - question to ask users who are voting on an issue of this type.
Example: Can you reproduce this bug?
Positive Vote Count - description for people who voted "yes".
Example: Users able to reproduce bug.
Negative Vote Count - description for people who voted "no".
Example: Users unable to reproduce bug.
Applicable Version - description for the version that this issue applies to. You can really make this mean anything you want, but be aware that issue submitters will always be able to choose a value.
Example: Affected Version.
Addressed Version - description of the version this issue is addressed in. Again, you can make this anything you want, but only users with permission to change the status of an issue will be able to set this.
Example: Fixed Version.
Post New Issue - text for the issue type-specific version of the "Post New Issue" link.
Example: Post New Bug.
Mark as read in PT vs Mark as read in main forum - confusion?
Hi, using vBulletin 4.2.5 on PHP 5.6 here, together with PT 2.3.0 from the svn (rev #914). I updated my forum recently from VB 4.2.4 and PT 2.2.2, everything worked OK here. Now, after the...
01-27-2018, 12:48 PM by dunc