Software Issue Manager
Enterprise Edition Documentation

An issue is anything that might affect the project meeting its goals such as bugs, tasks, and feature requests that occur during a project\'s life cycle.

Members are human resources who could be assigned to handle issues.

A project is a collection of related issues. Projects have a unique version number, specific start and end dates.

To create issue records in the admin area:

1. Log in to your Administration Panel.
2. Click the 'Issues' tab.
3. Click the 'Add New' sub-tab or the “Add New” button in the issue list page.
4. Start filling in your issue fields. You must fill all required fields. All required fields have red star after their labels.
5. As needed, set issue taxonomies and relationships. All required relationships or taxonomies must be set.
6. When you are ready, click Publish. If you do not have publish privileges, the "Submit for Review" button is displayed.
7. After the submission is completed, the issue status changes to "Published" or "Pending Review". Users must have "publish" right to publish issues. Users who do not have "publish" right can still create issues; however, these issues must be reviewed and approved by a user with issue "publish" right. Check Roles and Responsibilities section of this document to see which access groups have issue "publish" right.

Alternatively, you can create issue records using the issue entry form in the frontend by filling out the required fields.

Issue Documents file can be linked to Issues using the admin backend or using the "issue" entry form in the frontend when creating a new issue. You can upload unlimited number of Documents.

After the issue is created. Only the users who has "publish" right can upload Documents using the issue edit screen.

Issues can be modified by clicking on the "Edit" link under the issue title in the issue list page in the admin area. Make any necessary changes and then click Publish.

Issue revisions are stored when you save Issues as a draft or publish an update. The issue revisions allow you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision - what was added, what remained unchanged, and what was removed. Lines added or removed are highlighted, and individual character changes get additional highlighting. Click the 'Restore This Revision' button to restore a revision.

The revisions page also includes a 'compare any two revisions' mode that allows you to compare any two individual revisions. In this mode, the slider has two handles, one representing the revision you are comparing from and one representing the revision you are comparing to. Drag the handles to see what has changed between any two specific revisions. Note: the 'Restore This Revision' button always restores the revision you are comparing to.

To return top the issue edit screen without restoring a revision, click on the issue title at the top of the page.

Revision history box can be enabled/disabled using the screen option tab at the top of the edit screen. Revision history box details who made the change and when the revision was made.

In Software Issue Manager, users are only allowed to search issues they have access to. Users who have access to issues can search using the filter system in the issue admin areaor search forms in the frontend You can use drag-and-drop admin interface for sorting, creating/saving complex filters, and ordering columns in the entity list pages.

Administrators and users who have access to advanced Issue search page on the frontend can also utilize "Search operators" to drill down the result set without any limitations on access.

To schedule Issues for publication on a future time or date in the admin area:

1. Log in to your Administration Panel.
2. Click the 'Issues' tab.
3. Click the 'Add New' sub-tab or the “Add New” button in the issue list page.
4. Start filling in your issue fields. You must fill all required fields. All required fields have red star after their labels.
5. As needed, set issue taxonomies and relationships. All required relationships or taxonomies must be set.
6. When you are ready, click "Edit" in the Publish area next to the words "Publish immediately". You can also change the publish date to a date in the past to back-date Issues. Change the settings to the desired time and date. You must also hit the "Publish" button when you have completed the issue to publish at the desired time and date.
7. After the submission is completed, the issue status changes to "Published".

To create a password protected issue in the admin area:

1. Log in to your Administration Panel.
2. Click the 'Issues' tab.
3. Click the 'Add New' sub-tab or the “Add New” button in the issue list page.
4. Start filling in your issue fields. You must fill all required fields. All required fields have red star after their labels.
5. As needed, set issue taxonomies and relationships. All required relationships or taxonomies must be set.
6. Click the "Edit" link next to Visibility in the publish box and select "Password protected".
7. Enter a password that will be required to view that issue in the text field. The password is limited to 20 characters.
8. When you are ready, click the "Publish" button (or "Update" if the issue is already published.)
9. After the submission is completed, the issue status changes to "Published".

Only an Administrator and users with "publish" right can change the password set for your issue or modify visibility setting by clicking the "Visibility: Edit" link again.

When issue content is password protected, issue title displays the text "Protected: " before the issue Title and the content prints a password form with this text: "This content is password protected. To view it please enter your password below:".

If multiple issues have the same password, one will only have to enter the required password once. Only one password is tracked at a time so if you visit two different issues with two different password, you must re-enter the issue password to access content. WordPress saves passwords for maximum 10 days. After this period expires, one must reenter the password again to view the protected content.

Issues can be privately published to remove them from issue lists and feeds.

To create a private issue in the admin area:

1. Log in to your Administration Panel.
2. Click the 'Issues' tab.
3. Click the 'Add New' sub-tab or the “Add New” button in the issue list page.
4. Start filling in your issue fields. You must fill all required fields. All required fields have red star after their labels.
5. As needed, set issue taxonomies and relationships. All required relationships or taxonomies must be set.
6. Click the "Edit" link next to Visibility in the publish box and select "Private".
7. Once you change the visibility to private, the issue status changes to "Privately Published".
8. When you are ready, click the "UPDATE" button.

Only an Administrator and users with "publish" right for the issue can change visibility setting by clicking the "Visibility: Edit" link again.

To preview issue content press the "Preview" button - a button directly above the “publish” button - in the publish box before officially publishing or sending for review.

To create a draft issue in the admin area:

1. Log in to your Administration Panel.
2. Click the 'Issues' tab.
3. Click the 'Add New' sub-tab or the “Add New” button in the issue list page.
4. Start filling in your issue fields. You must fill all required fields. All required fields have red star after their labels.
5. As needed, set issue taxonomies and relationships. All required relationships or taxonomies must be set.
6. When you are ready, click "Save Draft" button in the publish box.
7. After the submission is completed, the issue status stays at "Draft".

Once the issue is published the user who created the issue is assigned as the issue author. Issue authors can view and edit the issue. One can change the issue author from the author box. The author box drop down is limited to the users who have issue "publish" right.

Issue Comments allow having a discussion related to the issue. Issue Comments are automatically enabled when the issue is created.

When you enable Issue Comments on a record, a comment form is displayed under "Issue Comments" section. Using the comment form here users can submit their comments.

Once a Issue Comment is submitted, approve, modify, reply or delete actions can be performed either in the Software Issue Manager dashboard or in the issue edit page. Once Issue Comment is approved, the comment appears under "Issue Comments" section of the issue page right above the comment form.

One can enable or disable Issue Comments in the admin area in two ways.

• Navigate to the editing screen for the issue, find the “Discussion” box and check or uncheck “Allow Comments.” If you do not see the “Discussion” box on the edit issue page, click “Screen Options” in the upper right corner of the browser window. Make sure the box next to “Discussion” is checked. Save your changes by clicking “Publish”, “Save Draft” or “Update."
• Alternatively, navigate to the issue list screen, find the one you want and hover your cursor over the title of the issue. You will see several links appear underneath the title. Click "Quick Edit" and check “Allow Comments.” Click “Update” to turn comments on for that issue.

You can create connections between Projects and Issues by clicking on "Create Connection" link in the "Affected Projects" box and then clicking on "Plus" sign adjacent to the record title you would like to connect. Optionally, you can create new record. If you create a new one, the record is created as a draft. You must publish all connected draft records to make the connections valid.

After the connection created, you can update or publish your issue. You can create as many connections as you need.

You can create connections between Members and Issues by clicking on "Create Connection" link in the "Assignee" box and then clicking on "Plus" sign adjacent to the record title you would like to connect. Optionally, you can create new record. If you create a new one, the record is created as a draft. You must publish all connected draft records to make the connections valid.

After the connection created, you can update or publish your issue. You can create at most one connection.

You can create connections between Projects and Issues by clicking on "Create Connection" link in the "Fix Projects" box and then clicking on "Plus" sign adjacent to the record title you would like to connect. Optionally, you can create new record. If you create a new one, the record is created as a draft. You must publish all connected draft records to make the connections valid.

After the connection created, you can update or publish your issue. You can create as many connections as you need.

You can create connections between Members and Issues by clicking on "Create Connection" link in the "Participants" box and then clicking on "Plus" sign adjacent to the record title you would like to connect. Optionally, you can create new record. If you create a new one, the record is created as a draft. You must publish all connected draft records to make the connections valid.

After the connection created, you can update or publish your issue. You can create as many connections as you need.

You can create connections between Issues and Issues by clicking on "Create Connection" link in the "Related Issues" box and then clicking on "Plus" sign adjacent to the record title you would like to connect. Optionally, you can create new record. If you create a new one, the record is created as a draft. You must publish all connected draft records to make the connections valid.

After the connection created, set the values to: Relation Type(dropdown). Take a look at the glossary section for dropdown values available. Now, you can update or publish your issue. You can create as many connections as you need.

You can create connections between Members and Issues by clicking on "Create Connection" link in the "Reporter" box and then clicking on "Plus" sign adjacent to the record title you would like to connect. Optionally, you can create new record. If you create a new one, the record is created as a draft. You must publish all connected draft records to make the connections valid.

After the connection created, you can update or publish your issue. You can create at most one connection.

You can create connections between Members and Issues by clicking on "Create Connection" link in the "Responsible Manager" box and then clicking on "Plus" sign adjacent to the record title you would like to connect. Optionally, you can create new record. If you create a new one, the record is created as a draft. You must publish all connected draft records to make the connections valid.

After the connection created, you can update or publish your issue. You can create at most one connection.

Software Issue Manager Enterprise supports creating of custom fields. Creating of custom fields provides a quick way to allow you to extend the content with key/value pairs also known as meta data. Custom fields store arbitrary extra information about issues.

To create a custom fields for your issues

1. Edit any issue or create a new one in the admin area. You will see the Custom Fields metabox. if you do not see it, enable it from Screen options.
2. Creating a custom field requires a key and a value. The key is constant, but the value can change for each issue. Click on Enter New link or select a key from the dropdown list.
3. Enter a value and click Add Custom Field button
4. Repeat the steps above for creating more fields

You can create as many custom fields as you need. If your custom field key may have multiple values, create a new field and use the same key with different values. You can use HTML code in the value box. Software Issue Manager concatenates each value separated with a space character. By default, WordPress shows 30 custom fields in the dropdown list.

Once you create issue custom fields, they are displayed in the frontend. The custom fields are available to be for your forms too. You can enable or disable them in the form layouts from SIM Enterprise menu > Settings page > Forms tab . By default all custom fields are disabled.

Browser can be set by typing the desired option in the empty text field and clicking "Add" button in "Browsers" box and updating/saving the issue. Setting a value for Browser is optional. Browser is also not organized hierarchically meaning there's no relationship from one Browser value to another.

Software Issue Manager comes with a preset Browsers defined in detail in Glossary section of this document. Administrators can always add/remove/modify the list based on your organizational needs. Some widgets created upon installation are based on predefined Browsers.

Category can be set by clicking on the desired option in "Categories" box and updating/saving the issue. Setting a value for Category is optional. Category is also not organized hierarchically meaning there's no relationship from one Category value to another.

Software Issue Manager comes with a preset Categories defined in detail in Glossary section of this document. Administrators can always add/remove/modify the list based on your organizational needs. Some widgets created upon installation are based on predefined Categories.

Component can be set by typing the desired option in the empty text field and clicking "Add" button in "Components" box and updating/saving the issue. Setting a value for Component is optional. Component is also not organized hierarchically meaning there's no relationship from one Component value to another.

Software Issue Manager comes with a preset Components defined in detail in Glossary section of this document. Administrators can always add/remove/modify the list based on your organizational needs. Some widgets created upon installation are based on predefined Components.

Operating System can be set by typing the desired option in the empty text field and clicking "Add" button in "Operating Systems" box and updating/saving the issue. Setting a value for Operating System is optional. Operating System is also not organized hierarchically meaning there's no relationship from one Operating System value to another.

Software Issue Manager comes with a preset Operating Systems defined in detail in Glossary section of this document. Administrators can always add/remove/modify the list based on your organizational needs. Some widgets created upon installation are based on predefined Operating Systems.

Priority can be set by clicking on the desired option in "Priorities" box and updating/saving the issue. Setting a value for Priority is optional. Priority is also not organized hierarchically meaning there's no relationship from one Priority value to another.

Software Issue Manager comes with a preset Priorities defined in detail in Glossary section of this document. Administrators can always add/remove/modify the list based on your organizational needs. Some widgets created upon installation are based on predefined Priorities.

Status can be set by clicking on the desired option in "Statuses" box and updating/saving the issue. Setting a value for Status is optional. Status is also not organized hierarchically meaning there's no relationship from one Status value to another.

Software Issue Manager comes with a preset Statuses defined in detail in Glossary section of this document. Administrators can always add/remove/modify the list based on your organizational needs. Some widgets created upon installation are based on predefined Statuses.

Tag can be set by typing the desired option in the empty text field and clicking "Add" button in "Tags" box and updating/saving the issue. Setting a value for Tag is optional. Tag is also not organized hierarchically meaning there's no relationship from one Tag value to another.

Tags do not have preset values.

Displaying Issue archives can be done by creating a link in the Appearance Menus Screen in the admin area.

Alternatively, if you'd like to display a specific Issue, you can select the link from Issue metabox and add it to your menu. If you don't see Issue metabox, check the Screen Options to ensure it is set to display.

To create a custom link for Issue archives:

1. Goto Appearance in the admin menu and click on Menus link
2. On the right hand side, pick the menu you’d like to include from Select a menu to edit dropdown
3. Under Links menu navigation item, type in /issues to the URL field
4. Type in Issues or another label describing the custom link URL in the Link Text field
5. Click “Add to menu” button to add the item to the menu
6. Pick “primary location” under “Menu Settings” below the menu
7. Save your menu
8. Go to the frontend and click on the link you created to access Issues. Issue archive page content is only displayed to the authorized users who have access permissions.

Issues can be created through emails by integrated WPAS incoming email extension. No purchase necessary . WPAS incoming mail extension allows to poll IMAP or POP3 servers, with or without SSL/TLS to receive emails. Polling frequency can be set to allow processing emails in specified intervals.

Using WPAS incoming email extension. You can define specific message processing rules per Issue:

• Deleting emails after creating Issues
• Setting maximum number of emails to post: a handy feature exp; if you want to accept specific number of Issues.
• Protection against spam or unauthorized Issue creation using email pins, authorized addresses, and banned file names.
• Allowing visitors(users who do not have publish capability) to create Issues via email
• Setting default subject for email without any subject line.

• Setting separate Issue post statuses for users and visitors.
• Using shortcodes to categorize emails or to set values.

Email processing activity history is recorded for processing errors or validations.

Incoming email settings can be configured by selecting SIM Enterprise menu in the admin area and clicking on Incoming email link.

In Software Issue Manager, Issues are locked during editing, preventing other users from accessing and modifying the Issue.

If a user clicks to edit one of the Issue records that's currently locked they are presented with three options in a pop-up dialog:

1. Go Back - Return to the Issues listing.
2. Preview - Preview the current state of the Issue that's being edited.
3. Take Over - Lock out the current editor of the Issues and begin editing. (The other user will receive a notification)

The user that has been locked out receives the following dialog, and is no longer able to edit the Issue. It can take up to 15 seconds for the current Issue editor to be notified that another user has taken over.

To create member records in the admin area:

1. Log in to your Administration Panel.
2. Click the 'Members' tab.
3. Click the 'Add New' sub-tab or the “Add New” button in the member list page.
4. Start filling in your member fields. You must fill all required fields. All required fields have red star after their labels.
5. As needed, set member taxonomies and relationships. All required relationships or taxonomies must be set.
6. When you are ready, click Publish. If you do not have publish privileges, the "Submit for Review" button is displayed.
7. After the submission is completed, the member status changes to "Published" or "Pending Review". Users must have "publish" right to publish members. Users who do not have "publish" right can still create members; however, these members must be reviewed and approved by a user with member "publish" right. Check Roles and Responsibilities section of this document to see which access groups have member "publish" right.

Alternatively, you can create member records using the member entry form in the frontend by filling out the required fields.

User Mapping

Members include user connection field. User connection field maps members to WordPress users and must be filled out to be able to create a valid record. You must first create a user or modify an existing user assigning her to either one of the following roles:

• Project Director
• Team Member
• Project Client
• Project Manager

User connection dropdown will be empty if you do not have any user assigned to the roles listed above.

WordPress users and Members have one-to-one relationship. In other words, every members must be linked to a user. This mapping can be done by Administrators by clicking on Operations button in the Members list screen and selecting Map Users tab. After mapping created and saved, existing WordPress users are mapped to members.

If Create members from existing users... checkbox on the same tab is checked, a corresponding member is automatically created based on the mapping when a new WordPress user with the supported role listed above is created. If you do not want to map a field or use a different value than used in the user registration, choose Do not map this field option from the corresponding mapping dropdown.

Member Photo image file can be linked to Members using the admin backend or using the "member" entry form in the frontend when creating a new member. You can upload at most 1 file.

After the member is created. Only the users who has "publish" right can upload Photo using the member edit screen.

Members can be modified by clicking on the "Edit" link under the member title in the member list page in the admin area. Make any necessary changes and then click Publish.

In Software Issue Manager, users are only allowed to search members they have access to. Users who have access to members can search using the filter system in the member admin areaor search forms in the frontend You can use drag-and-drop admin interface for sorting, creating/saving complex filters, and ordering columns in the entity list pages.

Administrators and users who have access to advanced Member search page on the frontend can also utilize "Search operators" to drill down the result set without any limitations on access.

To schedule Members for publication on a future time or date in the admin area:

1. Log in to your Administration Panel.
2. Click the 'Members' tab.
3. Click the 'Add New' sub-tab or the “Add New” button in the member list page.
4. Start filling in your member fields. You must fill all required fields. All required fields have red star after their labels.
5. As needed, set member taxonomies and relationships. All required relationships or taxonomies must be set.
6. When you are ready, click "Edit" in the Publish area next to the words "Publish immediately". You can also change the publish date to a date in the past to back-date Members. Change the settings to the desired time and date. You must also hit the "Publish" button when you have completed the member to publish at the desired time and date.
7. After the submission is completed, the member status changes to "Published".

To create a password protected member in the admin area:

1. Log in to your Administration Panel.
2. Click the 'Members' tab.
3. Click the 'Add New' sub-tab or the “Add New” button in the member list page.
4. Start filling in your member fields. You must fill all required fields. All required fields have red star after their labels.
5. As needed, set member taxonomies and relationships. All required relationships or taxonomies must be set.
6. Click the "Edit" link next to Visibility in the publish box and select "Password protected".
7. Enter a password that will be required to view that member in the text field. The password is limited to 20 characters.
8. When you are ready, click the "Publish" button (or "Update" if the member is already published.)
9. After the submission is completed, the member status changes to "Published".

Only an Administrator and users with "publish" right can change the password set for your member or modify visibility setting by clicking the "Visibility: Edit" link again.

When member content is password protected, member title displays the text "Protected: " before the member Title and the content prints a password form with this text: "This content is password protected. To view it please enter your password below:".

If multiple members have the same password, one will only have to enter the required password once. Only one password is tracked at a time so if you visit two different members with two different password, you must re-enter the member password to access content. WordPress saves passwords for maximum 10 days. After this period expires, one must reenter the password again to view the protected content.

Members can be privately published to remove them from member lists and feeds.

To create a private member in the admin area:

1. Log in to your Administration Panel.
2. Click the 'Members' tab.
3. Click the 'Add New' sub-tab or the “Add New” button in the member list page.
4. Start filling in your member fields. You must fill all required fields. All required fields have red star after their labels.
5. As needed, set member taxonomies and relationships. All required relationships or taxonomies must be set.
6. Click the "Edit" link next to Visibility in the publish box and select "Private".
7. Once you change the visibility to private, the member status changes to "Privately Published".
8. When you are ready, click the "UPDATE" button.

Only an Administrator and users with "publish" right for the member can change visibility setting by clicking the "Visibility: Edit" link again.

To preview member content press the "Preview" button - a button directly above the “publish” button - in the publish box before officially publishing or sending for review.

To create a draft member in the admin area:

1. Log in to your Administration Panel.
2. Click the 'Members' tab.
3. Click the 'Add New' sub-tab or the “Add New” button in the member list page.
4. Start filling in your member fields. You must fill all required fields. All required fields have red star after their labels.
5. As needed, set member taxonomies and relationships. All required relationships or taxonomies must be set.
6. When you are ready, click "Save Draft" button in the publish box.
7. After the submission is completed, the member status stays at "Draft".

Once the member is published the user who created the member is assigned as the member author. Member authors can view and edit the member. One can change the member author from the author box. The author box drop down is limited to the users who have member "publish" right.

Member Notes allow having a discussion related to the member. Member Notes are automatically enabled when the member is created.

When you enable Member Notes on a record, a comment form is displayed under "Member Notes" section. Using the comment form here users can submit their comments.

Once a Member Note is submitted, approve, modify, reply or delete actions can be performed either in the Software Issue Manager dashboard or in the member edit page. Once Member Note is approved, the comment appears under "Member Notes" section of the member page right above the comment form.

One can enable or disable Member Notes in the admin area in two ways.

• Navigate to the editing screen for the member, find the “Discussion” box and check or uncheck “Allow Comments.” If you do not see the “Discussion” box on the edit member page, click “Screen Options” in the upper right corner of the browser window. Make sure the box next to “Discussion” is checked. Save your changes by clicking “Publish”, “Save Draft” or “Update."
• Alternatively, navigate to the member list screen, find the one you want and hover your cursor over the title of the member. You will see several links appear underneath the title. Click "Quick Edit" and check “Allow Comments.” Click “Update” to turn comments on for that member.

You can create connections between Projects and Members by clicking on "Create Connection" link in the "Assigned Projects" box and then clicking on "Plus" sign adjacent to the record title you would like to connect. Optionally, you can create new record. If you create a new one, the record is created as a draft. You must publish all connected draft records to make the connections valid.

After the connection created, set the values to: Project Role(dropdown). Take a look at the glossary section for dropdown values available. Now, you can update or publish your member. You can create as many connections as you need.

You can create connections between Members and Issues by clicking on "Create Connection" link in the "Issues Participated" box and then clicking on "Plus" sign adjacent to the record title you would like to connect. Optionally, you can create new record. If you create a new one, the record is created as a draft. You must publish all connected draft records to make the connections valid.

After the connection created, you can update or publish your member. You can create as many connections as you need.

You can create connections between Members and Projects by clicking on "Create Connection" link in the "Projects Managed" box and then clicking on "Plus" sign adjacent to the record title you would like to connect. Optionally, you can create new record. If you create a new one, the record is created as a draft. You must publish all connected draft records to make the connections valid.

After the connection created, you can update or publish your member. You can create at most one connection.

Software Issue Manager Enterprise supports creating of custom fields. Creating of custom fields provides a quick way to allow you to extend the content with key/value pairs also known as meta data. Custom fields store arbitrary extra information about members.

To create a custom fields for your members

1. Edit any member or create a new one in the admin area. You will see the Custom Fields metabox. if you do not see it, enable it from Screen options.
2. Creating a custom field requires a key and a value. The key is constant, but the value can change for each member. Click on Enter New link or select a key from the dropdown list.
3. Enter a value and click Add Custom Field button
4. Repeat the steps above for creating more fields

You can create as many custom fields as you need. If your custom field key may have multiple values, create a new field and use the same key with different values. You can use HTML code in the value box. Software Issue Manager concatenates each value separated with a space character. By default, WordPress shows 30 custom fields in the dropdown list.

Once you create member custom fields, they are displayed in the frontend. The custom fields are available to be for your forms too. You can enable or disable them in the form layouts from SIM Enterprise menu > Settings page > Forms tab . By default all custom fields are disabled.

Country can be set by clicking on the desired option in "Countries" box and updating/saving the member. Setting a value for Country is optional. Country is also not organized hierarchically meaning there's no relationship from one Country value to another.

Software Issue Manager comes with a preset Countries defined in detail in Glossary section of this document. Administrators can always add/remove/modify the list based on your organizational needs. Some widgets created upon installation are based on predefined Countries.

State can be set by clicking on the desired option in "States" box and updating/saving the member. Setting a value for State is optional. State is also not organized hierarchically meaning there's no relationship from one State value to another.

Software Issue Manager comes with a preset States defined in detail in Glossary section of this document. Administrators can always add/remove/modify the list based on your organizational needs. Some widgets created upon installation are based on predefined States.

Tag can be set by typing the desired option in the empty text field and clicking "Add" button in "Tags" box and updating/saving the member. Setting a value for Tag is optional. Tag is also not organized hierarchically meaning there's no relationship from one Tag value to another.

Tags do not have preset values.

Type can be set by clicking on the desired option in "Types" box and updating/saving the member. Setting a value for Type is optional. Type is also not organized hierarchically meaning there's no relationship from one Type value to another.

Software Issue Manager comes with a preset Types defined in detail in Glossary section of this document. Administrators can always add/remove/modify the list based on your organizational needs. Some widgets created upon installation are based on predefined Types.

Displaying Member archives can be done by creating a link in the Appearance Menus Screen in the admin area.

Alternatively, if you'd like to display a specific Member, you can select the link from Member metabox and add it to your menu. If you don't see Member metabox, check the Screen Options to ensure it is set to display.

To create a custom link for Member archives:

1. Goto Appearance in the admin menu and click on Menus link
2. On the right hand side, pick the menu you’d like to include from Select a menu to edit dropdown
3. Under Links menu navigation item, type in /members to the URL field
4. Type in Members or another label describing the custom link URL in the Link Text field
5. Click “Add to menu” button to add the item to the menu
6. Pick “primary location” under “Menu Settings” below the menu
7. Save your menu
8. Go to the frontend and click on the link you created to access Members. Member archive page content is only displayed to the authorized users who have access permissions.

In Software Issue Manager, Members are locked during editing, preventing other users from accessing and modifying the Member.

If a user clicks to edit one of the Member records that's currently locked they are presented with three options in a pop-up dialog:

1. Go Back - Return to the Members listing.
2. Preview - Preview the current state of the Member that's being edited.
3. Take Over - Lock out the current editor of the Members and begin editing. (The other user will receive a notification)

The user that has been locked out receives the following dialog, and is no longer able to edit the Member. It can take up to 15 seconds for the current Member editor to be notified that another user has taken over.

To create project records in the admin area:

1. Log in to your Administration Panel.
2. Click the 'Projects' tab.
3. Click the 'Add New' sub-tab or the “Add New” button in the project list page.
4. Start filling in your project fields. You must fill all required fields. All required fields have red star after their labels.
5. As needed, set project taxonomies and relationships. All required relationships or taxonomies must be set.
6. When you are ready, click Publish. If you do not have publish privileges, the "Submit for Review" button is displayed.
7. After the submission is completed, the project status changes to "Published" or "Pending Review". Users must have "publish" right to publish projects. Users who do not have "publish" right can still create projects; however, these projects must be reviewed and approved by a user with project "publish" right. Check Roles and Responsibilities section of this document to see which access groups have project "publish" right.

Alternatively, you can create project records using the project entry form in the frontend by filling out the required fields.

Project Documents file can be linked to Projects using the admin backend or using the "project" entry form in the frontend when creating a new project. You can upload unlimited number of Documents.

After the project is created. Only the users who has "publish" right can upload Documents using the project edit screen.

Projects can be modified by clicking on the "Edit" link under the project title in the project list page in the admin area. Make any necessary changes and then click Publish.

In Software Issue Manager, users are only allowed to search projects they have access to. Users who have access to projects can search using the filter system in the project admin areaor search forms in the frontend You can use drag-and-drop admin interface for sorting, creating/saving complex filters, and ordering columns in the entity list pages.

Administrators and users who have access to advanced Project search page on the frontend can also utilize "Search operators" to drill down the result set without any limitations on access.

To schedule Projects for publication on a future time or date in the admin area:

1. Log in to your Administration Panel.
2. Click the 'Projects' tab.
3. Click the 'Add New' sub-tab or the “Add New” button in the project list page.
4. Start filling in your project fields. You must fill all required fields. All required fields have red star after their labels.
5. As needed, set project taxonomies and relationships. All required relationships or taxonomies must be set.
6. When you are ready, click "Edit" in the Publish area next to the words "Publish immediately". You can also change the publish date to a date in the past to back-date Projects. Change the settings to the desired time and date. You must also hit the "Publish" button when you have completed the project to publish at the desired time and date.
7. After the submission is completed, the project status changes to "Published".

To create a password protected project in the admin area:

1. Log in to your Administration Panel.
2. Click the 'Projects' tab.
3. Click the 'Add New' sub-tab or the “Add New” button in the project list page.
4. Start filling in your project fields. You must fill all required fields. All required fields have red star after their labels.
5. As needed, set project taxonomies and relationships. All required relationships or taxonomies must be set.
6. Click the "Edit" link next to Visibility in the publish box and select "Password protected".
7. Enter a password that will be required to view that project in the text field. The password is limited to 20 characters.
8. When you are ready, click the "Publish" button (or "Update" if the project is already published.)
9. After the submission is completed, the project status changes to "Published".

Only an Administrator and users with "publish" right can change the password set for your project or modify visibility setting by clicking the "Visibility: Edit" link again.

When project content is password protected, project title displays the text "Protected: " before the project Title and the content prints a password form with this text: "This content is password protected. To view it please enter your password below:".

If multiple projects have the same password, one will only have to enter the required password once. Only one password is tracked at a time so if you visit two different projects with two different password, you must re-enter the project password to access content. WordPress saves passwords for maximum 10 days. After this period expires, one must reenter the password again to view the protected content.

Projects can be privately published to remove them from project lists and feeds.

To create a private project in the admin area:

1. Log in to your Administration Panel.
2. Click the 'Projects' tab.
3. Click the 'Add New' sub-tab or the “Add New” button in the project list page.
4. Start filling in your project fields. You must fill all required fields. All required fields have red star after their labels.
5. As needed, set project taxonomies and relationships. All required relationships or taxonomies must be set.
6. Click the "Edit" link next to Visibility in the publish box and select "Private".
7. Once you change the visibility to private, the project status changes to "Privately Published".
8. When you are ready, click the "UPDATE" button.

Only an Administrator and users with "publish" right for the project can change visibility setting by clicking the "Visibility: Edit" link again.

To preview project content press the "Preview" button - a button directly above the “publish” button - in the publish box before officially publishing or sending for review.

To create a draft project in the admin area:

1. Log in to your Administration Panel.
2. Click the 'Projects' tab.
3. Click the 'Add New' sub-tab or the “Add New” button in the project list page.
4. Start filling in your project fields. You must fill all required fields. All required fields have red star after their labels.
5. As needed, set project taxonomies and relationships. All required relationships or taxonomies must be set.
6. When you are ready, click "Save Draft" button in the publish box.
7. After the submission is completed, the project status stays at "Draft".

Once the project is published the user who created the project is assigned as the project author. Project authors can view and edit the project. One can change the project author from the author box. The author box drop down is limited to the users who have project "publish" right.

Project Notes allow having a discussion related to the project. Project Notes are automatically enabled when the project is created.

When you enable Project Notes on a record, a comment form is displayed under "Project Notes" section. Using the comment form here users can submit their comments.

Once a Project Note is submitted, approve, modify, reply or delete actions can be performed either in the Software Issue Manager dashboard or in the project edit page. Once Project Note is approved, the comment appears under "Project Notes" section of the project page right above the comment form.

One can enable or disable Project Notes in the admin area in two ways.

• Navigate to the editing screen for the project, find the “Discussion” box and check or uncheck “Allow Comments.” If you do not see the “Discussion” box on the edit project page, click “Screen Options” in the upper right corner of the browser window. Make sure the box next to “Discussion” is checked. Save your changes by clicking “Publish”, “Save Draft” or “Update."
• Alternatively, navigate to the project list screen, find the one you want and hover your cursor over the title of the project. You will see several links appear underneath the title. Click "Quick Edit" and check “Allow Comments.” Click “Update” to turn comments on for that project.

You can create connections between Projects and Members by clicking on "Create Connection" link in the "Members" box and then clicking on "Plus" sign adjacent to the record title you would like to connect. Optionally, you can create new record. If you create a new one, the record is created as a draft. You must publish all connected draft records to make the connections valid.

After the connection created, set the values to: Project Role(dropdown). Take a look at the glossary section for dropdown values available. Now, you can update or publish your project. You can create as many connections as you need.

Software Issue Manager Enterprise supports creating of custom fields. Creating of custom fields provides a quick way to allow you to extend the content with key/value pairs also known as meta data. Custom fields store arbitrary extra information about projects.

To create a custom fields for your projects

1. Edit any project or create a new one in the admin area. You will see the Custom Fields metabox. if you do not see it, enable it from Screen options.
2. Creating a custom field requires a key and a value. The key is constant, but the value can change for each project. Click on Enter New link or select a key from the dropdown list.
3. Enter a value and click Add Custom Field button
4. Repeat the steps above for creating more fields

You can create as many custom fields as you need. If your custom field key may have multiple values, create a new field and use the same key with different values. You can use HTML code in the value box. Software Issue Manager concatenates each value separated with a space character. By default, WordPress shows 30 custom fields in the dropdown list.

Once you create project custom fields, they are displayed in the frontend. The custom fields are available to be for your forms too. You can enable or disable them in the form layouts from SIM Enterprise menu > Settings page > Forms tab . By default all custom fields are disabled.

Component can be set by typing the desired option in the empty text field and clicking "Add" button in "Components" box and updating/saving the project. Setting a value for Component is optional. Component is also not organized hierarchically meaning there's no relationship from one Component value to another.

Software Issue Manager comes with a preset Components defined in detail in Glossary section of this document. Administrators can always add/remove/modify the list based on your organizational needs. Some widgets created upon installation are based on predefined Components.

Priority can be set by clicking on the desired option in "Priorities" box and updating/saving the project. Setting a value for Priority is optional. Priority is also not organized hierarchically meaning there's no relationship from one Priority value to another.

Software Issue Manager comes with a preset Priorities defined in detail in Glossary section of this document. Administrators can always add/remove/modify the list based on your organizational needs. Some widgets created upon installation are based on predefined Priorities.

Program can be set by clicking on the desired option in "Programs" box and updating/saving the project. Setting a value for Program is optional. Program is also not organized hierarchically meaning there's no relationship from one Program value to another.

Programs do not have preset values.

Status can be set by clicking on the desired option in "Statuses" box and updating/saving the project. Setting a value for Status is optional. Status is also not organized hierarchically meaning there's no relationship from one Status value to another.

Software Issue Manager comes with a preset Statuses defined in detail in Glossary section of this document. Administrators can always add/remove/modify the list based on your organizational needs. Some widgets created upon installation are based on predefined Statuses.

Displaying Project archives can be done by creating a link in the Appearance Menus Screen in the admin area.

Alternatively, if you'd like to display a specific Project, you can select the link from Project metabox and add it to your menu. If you don't see Project metabox, check the Screen Options to ensure it is set to display.

To create a custom link for Project archives:

1. Goto Appearance in the admin menu and click on Menus link
2. On the right hand side, pick the menu you’d like to include from Select a menu to edit dropdown
3. Under Links menu navigation item, type in /projects to the URL field
4. Type in Projects or another label describing the custom link URL in the Link Text field
5. Click “Add to menu” button to add the item to the menu
6. Pick “primary location” under “Menu Settings” below the menu
7. Save your menu
8. Go to the frontend and click on the link you created to access Projects. Project archive page content is only displayed to the authorized users who have access permissions.

In Software Issue Manager, Projects are locked during editing, preventing other users from accessing and modifying the Project.

If a user clicks to edit one of the Project records that's currently locked they are presented with three options in a pop-up dialog:

1. Go Back - Return to the Projects listing.
2. Preview - Preview the current state of the Project that's being edited.
3. Take Over - Lock out the current editor of the Projects and begin editing. (The other user will receive a notification)

The user that has been locked out receives the following dialog, and is no longer able to edit the Project. It can take up to 15 seconds for the current Project editor to be notified that another user has taken over.

Issue Comments is a comment dashboard widget which is available in Software Issue Manager Dashboard. It shows latest 3 approved comment records without any page navigation links.

Issue Comments is a comment sidebar widget. It shows latest 5 approved comment records without any page navigation links.

Project News is an admin dashboard widget which is available in WordPress Dashboard. It shows latest published messages to the users.

Recent Issues is an entity sidebar widget. It shows latest 10 published issue records without any page navigation links.

Recent Members is an entity sidebar widget. It shows latest 10 published member records without any page navigation links.

Recent Project Notes is a comment dashboard widget which is available in Software Issue Manager Dashboard. It shows oldest 2 approved comment records without any page navigation links.

Recent Projects is an entity sidebar widget. It shows latest 10 published project records without any page navigation links.

"Project Issues" is a standard view which displays -1 Issue records per page with a post status of publish in descending order by date. Page navigation is disabled. If you choose to install setup pages during plugin activation, a WordPress page is created with a title of "Project Issues". You can visit this page to access the view. To display it in another page or post, use [project_issues] shortcode or select the view name from the WPAS component list after clicking on the WPAS toolbar button.

"Issue Counts By Assignee" is a pie chart. It is available in Software Issue Manager dashboard with a title of "Issue Counts By Assignee". If you choose to install setup pages during plugin activation, a WordPress page is created with a title of "Issue Counts By Assignee". You can visit this page to view the chart. To display the chart in another page or post, use [issues_counts_by_member] shortcode or select the view name from the WPAS component list after clicking on the WPAS toolbar button. This chart comes with a full width container. All charts adjust to the browser window size changes.

"Issue Counts By Category" is a pie chart. It is available in Software Issue Manager dashboard with a title of "Issue Counts By Category". If you choose to install setup pages during plugin activation, a WordPress page is created with a title of "Issue Counts By Category". You can visit this page to view the chart. To display the chart in another page or post, use [issue_counts_by_category] shortcode or select the view name from the WPAS component list after clicking on the WPAS toolbar button. This chart comes with a full width container. All charts adjust to the browser window size changes.

"Issue Counts By Category By Project" is a column chart. It is available in Software Issue Manager dashboard with a title of "Issue Counts By Category By Project". If you choose to install setup pages during plugin activation, a WordPress page is created with a title of "Issue Counts By Category By Project". You can visit this page to view the chart. To display the chart in another page or post, use [issue_counts_by_cat_project] shortcode or select the view name from the WPAS component list after clicking on the WPAS toolbar button. This chart comes with a full width container. All charts adjust to the browser window size changes.

"Issue Counts By Identified Date By Due Date Last 4 Weeks" is a column chart. It is available in Software Issue Manager dashboard with a title of "Issue Counts By Identified Date By Due Date Last 4 Weeks". If you choose to install setup pages during plugin activation, a WordPress page is created with a title of "Issue Counts By Identified Date By Due Date Last 4 Weeks". You can visit this page to view the chart. To display the chart in another page or post, use [issue_counts_byiddatebyduedate] shortcode or select the view name from the WPAS component list after clicking on the WPAS toolbar button. This chart comes with a full width container. All charts adjust to the browser window size changes.

"Issue Counts By Priority" is a pie chart. It is available in Software Issue Manager dashboard with a title of "Issue Counts By Priority". If you choose to install setup pages during plugin activation, a WordPress page is created with a title of "Issue Counts By Priority". You can visit this page to view the chart. To display the chart in another page or post, use [issue_counts_by_prio] shortcode or select the view name from the WPAS component list after clicking on the WPAS toolbar button. This chart comes with a full width container. All charts adjust to the browser window size changes.

"Issue Counts By Project" is a pie chart. It is available in Software Issue Manager dashboard with a title of "Issue Counts By Project". If you choose to install setup pages during plugin activation, a WordPress page is created with a title of "Issue Counts By Project". You can visit this page to view the chart. To display the chart in another page or post, use [issue_counts_by_project] shortcode or select the view name from the WPAS component list after clicking on the WPAS toolbar button. This chart comes with a full width container. All charts adjust to the browser window size changes.

"Issue Counts By Project Component" is a pie-donut chart. It is available in Software Issue Manager dashboard with a title of "Issue Counts By Project Component". If you choose to install setup pages during plugin activation, a WordPress page is created with a title of "Issue Counts By Project Component". You can visit this page to view the chart. To display the chart in another page or post, use [issue_counts_by_component] shortcode or select the view name from the WPAS component list after clicking on the WPAS toolbar button. This chart comes with a full width container. All charts adjust to the browser window size changes.

"Issue Counts By Status" is a pie-donut chart. It is available in Software Issue Manager dashboard with a title of "Issue Counts By Status". If you choose to install setup pages during plugin activation, a WordPress page is created with a title of "Issue Counts By Status". You can visit this page to view the chart. To display the chart in another page or post, use [issue_counts_by_status] shortcode or select the view name from the WPAS component list after clicking on the WPAS toolbar button. This chart comes with a full width container. All charts adjust to the browser window size changes.

"Issue Counts By Status By Identified Date Last 4 Weeks" is a column chart. It is available in Software Issue Manager dashboard with a title of "Issue Counts By Status By Identified Date Last 4 Weeks". To display the chart in another page or post, use [status_counts_by_iddate_4weeks] shortcode or select the view name from the WPAS component list after clicking on the WPAS toolbar button. This chart comes with a full width container. All charts adjust to the browser window size changes.

"Issue Counts By Status By Priority" is a column chart. It is available in Software Issue Manager dashboard with a title of "Issue Counts By Status By Priority". To display the chart in another page or post, use [issue_counts_status_priority] shortcode or select the view name from the WPAS component list after clicking on the WPAS toolbar button. This chart comes with a full width container. All charts adjust to the browser window size changes.

"Issue Time Spent By Project" is a pie chart. It is available in Software Issue Manager dashboard with a title of "Issue Time Spent By Project". If you choose to install setup pages during plugin activation, a WordPress page is created with a title of "Issue Time Spent By Project". You can visit this page to view the chart. To display the chart in another page or post, use [time_spent_per_project] shortcode or select the view name from the WPAS component list after clicking on the WPAS toolbar button. This chart comes with a full width container. All charts adjust to the browser window size changes.

"Issue Time Spent By Project Component" is a column chart. It is available in Software Issue Manager dashboard with a title of "Issue Time Spent By Project Component". If you choose to install setup pages during plugin activation, a WordPress page is created with a title of "Issue Time Spent By Project Component". You can visit this page to view the chart. To display the chart in another page or post, use [tspent_per_component] shortcode or select the view name from the WPAS component list after clicking on the WPAS toolbar button. This chart comes with a full width container. All charts adjust to the browser window size changes.

"Time Spent Per Issue By Assignee" is a pie chart. It is available in Software Issue Manager dashboard with a title of "Time Spent Per Issue By Assignee". If you choose to install setup pages during plugin activation, a WordPress page is created with a title of "Time Spent Per Issue By Assignee". You can visit this page to view the chart. To display the chart in another page or post, use [issue_time_spent_by_member] shortcode or select the view name from the WPAS component list after clicking on the WPAS toolbar button. This chart comes with a full width container. All charts adjust to the browser window size changes.

"Bugs By Current Week" is a crosstab report. It is available in Software Issue Manager dashboard with a title of "Bugs By Current Week". If you choose to install setup pages during plugin activation, a WordPress page is created with a title of "Bugs By Current Week". You can visit this page to access the view. To display it in another page or post, use [ct_bugs_by_current_week] shortcode or select the view name from the WPAS component list after clicking on the WPAS toolbar button.

"Feature Requests By Current Week" is a crosstab report. It is available in Software Issue Manager dashboard with a title of "Feature Requests By Current Week". If you choose to install setup pages during plugin activation, a WordPress page is created with a title of "Feature Requests By Current Week". You can visit this page to access the view. To display it in another page or post, use [ct_frequest_by_current_week] shortcode or select the view name from the WPAS component list after clicking on the WPAS toolbar button.

Displays issues counts of feature requests, bugs, and tasks at the following levels; today, yesterday, this week, last week, this month, last month, and total."Issue Infobox" is a infobox report. It is available in Software Issue Manager dashboard with a title of "Issue Infobox". If you choose to install setup pages during plugin activation, a WordPress page is created with a title of "Issue Infobox". You can visit this page to access the view. To display it in another page or post, use [ib_issue_infoboxes] shortcode or select the view name from the WPAS component list after clicking on the WPAS toolbar button.

"Tasks By Current Week" is a crosstab report. It is available in Software Issue Manager dashboard with a title of "Tasks By Current Week". If you choose to install setup pages during plugin activation, a WordPress page is created with a title of "Tasks By Current Week". You can visit this page to access the view. To display it in another page or post, use [ct_tasks_by_current_week] shortcode or select the view name from the WPAS component list after clicking on the WPAS toolbar button.

"Issue entry" form is used for entering issue records from the frontend. You can use [issue_entry] shortcode to display it in a page or post of your choise as well.

The following are the fields used in the form:

• Priorities (select-only single selection allowed)
• Statuses (select-only single selection allowed)
• Categories (select-only single selection allowed)
• Tags (select-multiple selection allowed)
• Browsers (select-multiple selection allowed)
• Operating Systems (select-multiple selection allowed)
• ID (hidden_func)
• Identified DateTime (datetime)
• Original Estimate (text)
• Due Date (date)
• Documents (file)
• Title (text)
• Content (wysiwyg)
• Form Name (hidden)
• Form Submitted By (hidden_func)
• Form Submitted IP (hidden_func)
• Affected Projects (select-multiple selection allowed)
• Reporter (select-only single selection allowed)
• Responsible Manager (select-only single selection allowed)

"Issue entry public" form is used for entering issue records from the frontend. You can use [issue_entry_public] shortcode to display it in a page or post of your choise as well.

The following are the fields used in the form:

• Priorities (select-only single selection allowed)
• Statuses (select-only single selection allowed)
• Categories (select-only single selection allowed)
• Tags (select-multiple selection allowed)
• Browsers (select-multiple selection allowed)
• Operating Systems (select-multiple selection allowed)
• ID (hidden_func)
• Identified DateTime (datetime)
• Original Estimate (text)
• Due Date (date)
• Documents (file)
• Title (text)
• Content (wysiwyg)
• Form Name (hidden)
• Form Submitted By (hidden_func)
• Form Submitted IP (hidden_func)
• Affected Projects (select-multiple selection allowed)

"Issue search" form is used for searching issue records from the frontend. You can use [issue_search] shortcode to display it in a page or post of your choise as well.

The following are the fields used in the form:

• Priorities (select-only single selection allowed)
• Statuses (select-only single selection allowed)
• Categories (select-only single selection allowed)
• Tags (select-multiple selection allowed)
• ID (hidden_func)
• Identified DateTime (datetime)
• Due Date (date)
• Resolution DateTime (datetime)
• Title (text)
• Affected Projects (select-multiple selection allowed)
• Assignee (select-only single selection allowed)
• Reporter (select-only single selection allowed)
• Participants (select-multiple selection allowed)
• Responsible Manager (select-only single selection allowed)

"Issue search public" form is used for searching issue records from the frontend. You can use [issue_search_public] shortcode to display it in a page or post of your choise as well.

The following are the fields used in the form:

• Priorities (select-only single selection allowed)
• Statuses (select-only single selection allowed)
• Categories (select-only single selection allowed)
• Tags (select-multiple selection allowed)
• ID (hidden_func)
• Identified DateTime (datetime)
• Due Date (date)
• Resolution DateTime (datetime)
• Title (text)
• Affected Projects (select-multiple selection allowed)

"Member entry" form is used for entering member records from the frontend. You can use [member_entry] shortcode to display it in a page or post of your choise as well.

The following are the fields used in the form:

• Types (select-only single selection allowed)
• States (select-only single selection allowed)
• Countries (select-only single selection allowed)
• Tags (select-multiple selection allowed)
• Photo (file)
• Salutation (select)
• First Name (text)
• Last Name (text)
• Job Title (text)
• User Name (selectadv)
• Email (text)
• Office Phone (text)
• Mobile (text)
• Fax (text)
• Primary Address (textarea)
• City (text)
• Zip Code (text)
• Form Name (hidden)
• Form Submitted By (hidden_func)
• Form Submitted IP (hidden_func)
• Assigned Projects (select-multiple selection allowed)
• Projects Managed (select-only single selection allowed)

"Member search" form is used for searching member records from the frontend. You can use [member_search] shortcode to display it in a page or post of your choise as well.

The following are the fields used in the form:

• Types (select-only single selection allowed)
• States (select-only single selection allowed)
• Countries (select-only single selection allowed)
• Tags (select-multiple selection allowed)
• First Name (text)
• Last Name (text)
• Job Title (text)
• User Name (selectadv)
• Email (text)
• City (text)
• Zip Code (text)
• Assigned Projects (select-multiple selection allowed)
• Projects Managed (select-only single selection allowed)
• Issues Assigned (select-only single selection allowed)
• Reported Issues (select-only single selection allowed)
• Issues Participated (select-multiple selection allowed)

"Project entry" form is used for entering project records from the frontend. You can use [project_entry] shortcode to display it in a page or post of your choise as well.

The following are the fields used in the form:

• Statuses (select-only single selection allowed)
• Priorities (select-only single selection allowed)
• Components (select-multiple selection allowed)
• Programs (select-only single selection allowed)
• Name (text)
• Version (text)
• Start Date (date)
• Target End Date (date)
• Documents (file)
• Content (wysiwyg)
• Form Name (hidden)
• Form Submitted By (hidden_func)
• Form Submitted IP (hidden_func)
• Members (select-multiple selection allowed)

"Project entry public" form is used for entering project records from the frontend. You can use [project_entry_public] shortcode to display it in a page or post of your choise as well.

The following are the fields used in the form:

• Statuses (select-only single selection allowed)
• Priorities (select-only single selection allowed)
• Components (select-multiple selection allowed)
• Programs (select-only single selection allowed)
• Name (text)
• Version (text)
• Start Date (date)
• Target End Date (date)
• Documents (file)
• Content (wysiwyg)
• Form Name (hidden)
• Form Submitted By (hidden_func)
• Form Submitted IP (hidden_func)

"Search projects" form is used for searching project records from the frontend. You can use [search_projects] shortcode to display it in a page or post of your choise as well.

The following are the fields used in the form:

• Statuses (select-only single selection allowed)
• Priorities (select-only single selection allowed)
• Components (select-multiple selection allowed)
• Programs (select-only single selection allowed)
• Name (text)
• Version (text)
• Start Date (date)
• Target End Date (date)
• Actual End Date (date)
• Content (wysiwyg)
• Members (select-multiple selection allowed)
• Project Manager (select-only single selection allowed)

"Search projects public" form is used for searching project records from the frontend. You can use [search_projects_public] shortcode to display it in a page or post of your choise as well.

The following are the fields used in the form:

• Statuses (select-only single selection allowed)
• Priorities (select-only single selection allowed)
• Components (select-multiple selection allowed)
• Programs (select-only single selection allowed)
• Name (text)
• Version (text)
• Start Date (date)
• Target End Date (date)
• Actual End Date (date)
• Content (wysiwyg)

When any Assignee of Issues to:

• added

The following get notified:

• Assignee
• Reporter
• Participants

When any Issue Comment:

• added
• changed

The following get notified:

• Comment Author Email
• Assignee
• Reporter
• Participants

When Priority value of any Issue is set to the value of:

The following get notified:

• Assignee
• Reporter
• Participants

When any Issue record:

• put in trash

The following get notified:

• Assignee
• Reporter
• Participants

When Status value of any Issue is set to the value of:

The following get notified:

• Assignee
• Reporter
• Participants

When any Issue record:

• changed

The following get notified:

• Assignee
• Reporter
• Participants

When any Issue record:

• added from frontend
• added from backend

The following get notified:

• Assignee
• Reporter
• Participants

When any Participants of Issues to:

• added

The following get notified:

• Assignee
• Reporter
• Participants

When Documents of any Project is set to the value of:

The following get notified:

• Members
• Project Manager

When any Assigned Projects of Members to:

• added

The following get notified:

• Members
• Project Manager

When any Project Note:

• added
• changed

The following get notified:

• Comment Author Email
• Members
• Project Manager

To install your Software Issue Manager Plugin using the built-in plugin installer:

1. Download Software Issue Manager Plugin to your desktop.
2. Go to Plugins "Add New".
3. Under Upload, click "Browse".
4. Find the Software Issue Manager.zip file.
5. Click Install Now to install the Software Issue Manager Plugin.
6. A popup window will ask you to confirm your wish to install the Plugin.
7. Click Proceed to continue with the installation. The resulting installation screen will list the installation as successful or note any problems during the install.
8. If successful, click Activate Plugin to activate it, or Return to Plugin Installer for further actions.

After the activation, the Software Issue Manager plugin setup may display notification asking if you if you'd like to install setup pages or skip setup page installation, click the appropriate button.

To uninstall your Software Issue Manager Plugin using the built-in plugin installer:

1. Go to Plugins screen.
2. Find the Software Issue Manager Plugin you wish to deactivate and uninstall.
3. Click Deactivate.

WordPress auto-update system displays notification in the Admin Bar and also on the plugins page when new version of the Software Issue Manager is available.

To install the new version, simply hit the "Update automatically" button. WordPress will automatically download the new package, extract it and replace the old files. No FTP, removing old files, and uploading is required.

Upgrading your plugin

We offer different plugin editions to better match your needs. If you purchased a different edition of Software Issue Manager, follow the steps below to upgrade your plugin:

1. Go WordPress plugins page and deactivate and optionally delete the current Software Issue Manager Enterprise edition.
2. Install the new edition based on the instructions in WordPress Codex
3. Activate the new edition
4. Go to Plugin Settings page and save settings

Upgrading Software Issue Manager Enterprise edition does not have any impact on your existing data but it is always a good idea to back up your WordPress database as a rule of thumb before any changes.

Using Plugin Extensions

Software Issue Manager Enterprise edition is configured to work with many plugin extensions. Most plugin extensions work regardless of the edition unless specified specifically in the plugin page.

if you purchased a plugin extension, follow the instructions instructions in WordPress Codex to install and activate your plugin extension like any other WordPress plugin.

If your extension comes with a license key, you must save and activate your license key to get software updates and support.

Maintaining your plugin

Keeping your plugin up-to-date is very important. At emdplugins.com, we regularly update our products to offer plugin or WordPress related bug fixes, product enhancements, patches for security vulnerabilities and more. Ability to receive these updates is critical to maintaining your software and site in working condition.

To be able to see the update notifications and receive updates, you must have a valid, activated license at all times. If your existing license is expired, you must renew it manually if you opted out of automatic renewals.

Please also note that you must have a valid license to get support for your plugin.

To activate your license:

1. Go to SIM Enterprise > Licenses page
2. Enter the license key you receive in your purchase receipt
3. Click "Save Changes" button
4. Now, you will see, "Activate License" button and "INACTIVE" right next to your license key
5. Click "Activate License" button to activate your license
6. If you see "VALID" message in place of "INACTIVE", you should be able to get your plugin updates.

If you followed the steps above and still are not able to get the plugin updates, there could be additional configuration needed for your site.

Administrators can import or export content to/from Software Issue Manager entities using CSV files by clicking on Operations button in entity list pages.

Operations page is divided into Import, Export, and Reset tabs. Import tab is used to visually import existing records into an entity. Export tab is used to export the content of an entity as a CSV file. Reset tab deletes the content of an entity. In reset tab, you can also choose to delete all entity content, relationships, or taxonomies.

Pick the operation you'd like to do and follow the instructions on the screen.

Administrators can show, hide, and resize form elements by clicking on the Settings page under SIM Enterprise menu. In addition, form captcha element can be set to "Visitors Only","Always Show", or "Never Show".

Required fields can not be disabled however you can change the column size. The optional fields can be enabled, disabled, or modified to occupy more or less space in the form layout.

Make sure to save your changes after any modification otherwise your changes will not take effect.

Software Issue Manager Enterprise comes with Visual Shortcode Builder(VSB) module which allows creating advanced custom shortcodes without manually writing code. To use Visual Shortcode Builder:

1. Create a new page
2. Click on WPAS button right next to Add Media button
3. Find and select the view or form you'd like to use a base from the drowdown list
4. Modify the shortcode by adding filters from taxonomy, attribute, relationship or misc categories
   • Don't forget to click + icon every time you add a filter
   • You can create as many filters as you need in the same shortcode
5. When you finished, click Insert Shortcode button. The shortcode will be inserted to the page
6. Update or publish the page to see the shortcode result
7. Repeat the same process for all your shortcodes

An issue is anything that might affect the project meeting its goals such as bugs, tasks, and feature requests that occur during a project\'s life cycle.

ID

Sets a unique identifier for an issue. Being a unique identifier, it uniquely distinguishes each instance of Issue entity. ID is filterable in the admin area. ID does not have a default value.

Sequence

Sets the priority sequence of an issue. Sequence is filterable in the admin area. Sequence does not have a default value.

Identified DateTime

Sets the date and time that an issue was identified. Identified DateTime is a required field. Identified DateTime is filterable in the admin area. Identified DateTime does not have a default value.

Original Estimate

Sets the original estimate of the total amount of time in hours it would take to complete an issue. Original Estimate is filterable in the admin area. Original Estimate does not have a default value.

Estimated Time Remaining

Sets the current estimate of the remaining amount of time in hours it would take to complete an issue. Estimated Time Remaining is filterable in the admin area. Estimated Time Remaining does not have a default value.

Time Spent

Sets the amount of time spent on an issue in hours. This is the total amount of time which has been logged against an issue. Time Spent is filterable in the admin area. Time Spent does not have a default value.

Due Date

Sets the targeted resolution date for an issue. Due Date is filterable in the admin area. Due Date does not have a default value.

Resolution DateTime

Set the actual time and date on which an issue was resolved. Resolution DateTime is filterable in the admin area. Resolution DateTime does not have a default value.

Resolution Summary

Sets a brief summary of the resolution of an issue. Resolution Summary does not have a default value.

Documents

Allows to upload files related to an issue. Documents does not have a default value.

Title

Title is a required field. Title does not have a default value.

Content

Content does not have a default value.

Form Name

Form Name is filterable in the admin area. Form Name has a default value of "admin".

Form Submitted By

Form Submitted By is filterable in the admin area. Form Submitted By does not have a default value.

Form Submitted IP

Form Submitted IP is filterable in the admin area. Form Submitted IP does not have a default value.

Browser

Sets the browser version that an issue may be reproduced in. Browser accepts multiple values like tags. Browser does not have a default value.

Category

Sets the category that an issue belongs to. Category accepts multiple values like tags. Category has a default value of: 'bug'.

Priority

Sets the priority level assigned to an issue. Priority accepts multiple values like tags. Priority has a default value of: 'normal'.

Status

Set the current status of an issue. Status accepts multiple values like tags. Status has a default value of: 'open'.

Tag

Allows to tag issues to further classify or group related issues. Tag accepts multiple values like tags. Tag does not have a default value.

Operating System

Sets the operating system(s) that an issue may be reproduced in. Operating System accepts multiple values like tags. Operating System does not have a default value.

Component

Sets the project component(s) that is related to an issue or the components that a project may touch. It is another way to logically group issues within a project. Component accepts multiple values like tags. Component does not have a default value.

Affected Projects

Allows to display and create connections with Projects. One instance of Issues can associated with many instances of Projects, and vice versa. The relationship can be set up in the edit area of Issues using Affected Projects relationship box. This relationship is required when publishing new Issues.

Assignee

Allows to display and create connections with Members. One instance of Issues can associated with only one instance of Members. The relationship can be set up in the edit area of Issues using Assignee relationship box. After a relationship is setup by pressing the plus icon, you may fill out relationship fields to complete connection creation.

Reporter

Allows to display and create connections with Members. One instance of Issues can associated with only one instance of Members. The relationship can be set up in the edit area of Issues using Reporter relationship box.

Related Issues

Allows to display and create connections with Issues. One instance of Issues can associated with many instances of Issues, and vice versa. The relationship can be set up in the edit area of Issues using Related Issues relationship box. After a relationship is setup by pressing the plus icon, you may fill out relationship fields to complete connection creation.

Fix Projects

Allows to display and create connections with Projects. One instance of Issues can associated with many instances of Projects, and vice versa. The relationship can be set up in the edit area of Issues using Fix Projects relationship box.

Participants

Allows to display and create connections with Members. One instance of Issues can associated with many instances of Members, and vice versa. The relationship can be set up in the edit area of Members using Issues Participated or in the edit area of Issues using Participants relationship boxes.

Responsible Manager

Allows to display and create connections with Members. One instance of Issues can associated with only one instance of Members. The relationship can be set up in the edit area of Issues using Responsible Manager relationship box.

Relation Type

The type of relation of one issue to another. Relation Type is an attribute of Related Issues relationship and can be set after the connection created. Supported values are;

• Child
• Parent
• Dependent
• Duplicate
• Refers to

Relation Type does not have a default value.

Members are human resources who could be assigned to handle issues.

Photo

Allows to upload a member photo. Photo does not have a default value.

Salutation

Sets the salutation used for a member. Salutation does not have a default value. Salutation is displayed as a dropdown and has predefined values of: Mr, Mrs, Ms, Dr, Prof.

First Name

Sets the member\'s first name. First Name is a required field. Being a unique identifier, it uniquely distinguishes each instance of Member entity. First Name is filterable in the admin area. First Name does not have a default value.

Last Name

Sets the member\'s last name. Last Name is a required field. Being a unique identifier, it uniquely distinguishes each instance of Member entity. Last Name is filterable in the admin area. Last Name does not have a default value.

Job Title

Sets the job title of a member. Job Title does not have a default value.

User Name

Sets the system user corresponding to a member. User Name is a required field. Being a unique identifier, it uniquely distinguishes each instance of Member entity. User Name is filterable in the admin area. User Name does not have a default value. Only users who have the following access roles are listed as allowable value;

• project director
• team member
• project client
• project manager

Email

Sets the email address which belongs to a member. Email is a required field. Email does not have a default value.

Office Phone

Sets the office phone number which belongs to a member. Office Phone is filterable in the admin area. Office Phone does not have a default value.

Mobile

Sets the mobile phone number which belongs to a member. Mobile is filterable in the admin area. Mobile does not have a default value.

Fax

Sets the fax number which belongs to a member. Fax does not have a default value.

Primary Address

Sets the primary address of a member. Primary Address does not have a default value.

City

Sets the city of a member\'s address. City is filterable in the admin area. City does not have a default value.

Zip Code

Sets the zip code of a member\'s address. Zip Code is filterable in the admin area. Zip Code does not have a default value.

Form Name

Form Name is filterable in the admin area. Form Name has a default value of "admin".

Form Submitted By

Form Submitted By is filterable in the admin area. Form Submitted By does not have a default value.

Form Submitted IP

Form Submitted IP is filterable in the admin area. Form Submitted IP does not have a default value.

Country

Sets the country of a member's address. Country accepts multiple values like tags. Country does not have a default value.

Tag

Allows to tag members based on their associations in an organization. Tag accepts multiple values like tags. Tag does not have a default value.

Type

Defines the association of a member to an organization. Type accepts multiple values like tags. Type has a default value of: 'internal'.

State

Sets the state that of a member's address. State accepts multiple values like tags. State does not have a default value.

Assigned Projects

Allows to display and create connections with Projects. One instance of Members can associated with many instances of Projects, and vice versa. The relationship can be set up in the edit area of Projects using Members or in the edit area of Members using Assigned Projects relationship boxes. After a relationship is setup by pressing the plus icon, you may fill out relationship fields to complete connection creation.

Issues Assigned

Allows to display and create connections with Issues. One instance of Members can associated with many instances of Issues. The relationship can be set up in the edit area of Issues using Assignee relationship box. After a relationship is setup by pressing the plus icon, you may fill out relationship fields to complete connection creation.

Reported Issues

Allows to display and create connections with Issues. One instance of Members can associated with many instances of Issues. The relationship can be set up in the edit area of Issues using Reporter relationship box.

Issues Participated

Allows to display and create connections with Issues. One instance of Members can associated with many instances of Issues, and vice versa. The relationship can be set up in the edit area of Members using Issues Participated or in the edit area of Issues using Participants relationship boxes.

Projects Managed

Allows to display and create connections with Projects. One instance of Members can associated with many instances of Projects. The relationship can be set up in the edit area of Members using Projects Managed relationship box.

Issues Owned

Allows to display and create connections with Issues. One instance of Members can associated with many instances of Issues. The relationship can be set up in the edit area of Issues using Responsible Manager relationship box.

A project is a collection of related issues. Projects have a unique version number, specific start and end dates.

Name

Sets the name of a project. Name is a required field. Being a unique identifier, it uniquely distinguishes each instance of Project entity. Name is filterable in the admin area. Name does not have a default value.

Version

Sets the version number of a project. Version is a required field. Being a unique identifier, it uniquely distinguishes each instance of Project entity. Version is filterable in the admin area. Version has a default value of "V1.0.0".

Start Date

Sets the start date of a project. Start Date is a required field. Start Date is filterable in the admin area. Start Date does not have a default value.

Target End Date

Sets the targeted end date of a project. Target End Date is filterable in the admin area. Target End Date does not have a default value.

Actual End Date

Sets the actual end date of a project. Actual End Date is filterable in the admin area. Actual End Date does not have a default value.

Documents

Allows to upload project related files. Documents does not have a default value.

Content

Content does not have a default value.

Form Name

Form Name is filterable in the admin area. Form Name has a default value of "admin".

Form Submitted By

Form Submitted By is filterable in the admin area. Form Submitted By does not have a default value.

Form Submitted IP

Form Submitted IP is filterable in the admin area. Form Submitted IP does not have a default value.

Program

Set the program a project may be part of. A program is a collection of related projects. Program accepts multiple values like tags. Program does not have a default value.

Component

Sets the project component(s) that is related to an issue or the components that a project may touch. It is another way to logically group issues within a project. Component accepts multiple values like tags. Component does not have a default value.

Priority

Sets the current priority of a project. Priority accepts multiple values like tags. Priority has a default value of: 'medium'.

Status

Sets the current status of a project. Status accepts multiple values like tags. Status has a default value of: 'draft'.

Project Manager

Allows to display and create connections with Members. One instance of Projects can associated with only one instance of Members. The relationship can be set up in the edit area of Members using Projects Managed relationship box.

Project Issues

Allows to display and create connections with Issues. One instance of Projects can associated with many instances of Issues, and vice versa. The relationship can be set up in the edit area of Issues using Affected Projects relationship box. This relationship is required when publishing new Projects.

Members

Allows to display and create connections with Members. One instance of Projects can associated with many instances of Members, and vice versa. The relationship can be set up in the edit area of Projects using Members or in the edit area of Members using Assigned Projects relationship boxes. After a relationship is setup by pressing the plus icon, you may fill out relationship fields to complete connection creation.

Fixed Issues

Allows to display and create connections with Issues. One instance of Projects can associated with many instances of Issues, and vice versa. The relationship can be set up in the edit area of Issues using Fix Projects relationship box.

Project Role

Role that a participating member plays in this project. Project Role is an attribute of Assigned Projects relationship and can be set after the connection created. Supported values are;

• Lead
• Sponsor
• Developer
• Analyst
• QA
• Architect

Project Role does not have a default value.