Submitting Issues

Only users with Submit permission for a particular issue type can create new issues of that type. To submit an issue, follow these steps:

1. Click New on the navigation bar.
2. A drop down menu will open. Select an issue type.
3. Enter information into the fields as needed.
   • Fields with an asterisk are required; you will not be able to submit the issue without completing them.
   • If you have permission to add values to a lookup list, you may type a new value into that field's box instead of selecting a pre-existing value.
4. Select a user or group to assign the issue to. Groups must be set up by Project Administrators.
5. The information in the Description field can be formatted using formatting tags.
   • Any issues you link in a comment will be displayed as a related issue at the top of the issue details page.
   • Click the preview link if you would like to view how the description will look when submitted. Click back in the Description field to turn off the preview.
6. Set the Confidential field to Yes if the field is being used for that issue type and if you would like to limit access to the issue to members who's roles have developer and/or manager permissions and yourself.
7. If you would like to add one or more attachments, click Browse next to the Attachments field, browse to the item you would like to attach, double click the file name and then click Attach. Continue until you have added all of your attachments.
   • If you add an attachment and decided that you do not want it, click the Remove link next to the attachment name.
8. Check the Add This Issue To My Watch List check box, if desired.
9. If you would like to send out email notifications when the issue is submitted, click the Notifications button at the top of the page, enter the names of other Squish users you would like to notify and then click Save.  If any users are set to be notified when new issues are submitted on the Project Settings screen, they cannot be deselected.
10. Click Submit Issue. A success message will appear beneath the project navigation bar. The project manager may receive notification of the new issue by e-mail, depending on project settings.
    • If another user has updated the issue while you have the issue page open, submitting your changes will display a message and link to reload the issue.

If you attempt to leave a page with unsaved changes on it, a warning message will be displayed, asking if you are sure you want to leave the page. After an issue has been submitted, it can be updated as necessary to provide new information or to report on the progress being made.

Note: If you have selected a value for the Comment Format on the My Account page, you can enter and edit your comments using that selection. Use the Preview and Write buttons to toggle back and forth between the comment preview and the source code.

Submitting issues

To submit a Squish issue via email, first login to Squish and click New on the project navigation menu. Select the issue type which you will be submitting via email. At the bottom of the page, there will be a link to the correct email address. When you select that link, a new email will open with the correct Issue Type prepopulated in the subject line.

When you send an email to Squish to create a new issue, a number of things happen:

1. To determine which user to submit the issue as, Squish checks the senders email address against all active company users.
• If an email address is associated with more than one user, the last user to log into Squish is used.
• If no user is found with the sender's address, then a verification email is sent to the submitting email. In order for the submitting email address to receive issue update notifications, the email must be verified.
2. The subject line is checked for the name of an issue type in square brackets.
• For instance, to submit an issue of type "Feature Request" via email, the subject should include "[Feature Request]" in it. A subject of "[Feature Request] New feature name" will result in a new Feature Request issue with a subject of "New feature name".
• If no issue type is included in the subject line, but a default issue type is specified, then that issue type will be used. If only one issue type in the project is marked as accepting email submissions, it will be used regardless of whether the name is included in the email subject line.
3. The user is checked against the project role permissions for that issue type to make sure they have permission to submit issues.
4. The entire contents of the email are submitted as the description of the issue.

A few notes

1. Emailed attachments will be included in the Squish issues/comments.
2. If an email fails to generate an issue or comment for some reason, the sender will receive an email notification detailing why.
3. Issue notifications and webhooks will be processed as normal for emailed issues and comments.

Commenting on issues

The same user and permission checking happens when emailing a comment to a Squish issue, to determine which user to post the comment as. The only difference is that, instead of posting the entire contents of the email into the comment, only the last reply is included. For instance, emailing the following into a Squish issue:

I think that's a great idea!

On 2/11/2015, Joe Smith wrote:
> What about a way to email comments into Squish?
> I think that would be the tops!

Would result in a comment containing only "I think that's a great idea!". Comments submitted via email are indicated by a small envelope icon next to the posters name: