Type | 1. Click . 2. Expand the tree, and select Submission Issue. 3. Click Done. Choosing Submission Issue adds fields to the issue specific to submissions (the generic Issue form applies to any type of object). |
Description | Details about the problem. |
Reported Against | Shows the name of the context Submission and cannot be changed. If you started from the Issues page for all apps, click to select the needed Submission project. |
Escalation Required | Choose Yes or No. |
Estimated Start | The date on which resolution of the issue begins. |
Estimated Finish | The date on which the issue is expected to be resolved. |
Priority | Choose a priority level:- Low
- Pre-assigned
- Medium
- High
- Urgent
|
Co-owners | Click to choose people responsible for the issue. |
Problem Type | Choose an option:- Not Determined
- 3rd Party
- Defect
- Ease of Use
- Functionality
- Licensing
- Installation
- Mistake
- Performance
- Platform
- Training
- Usage Model
|
Resolution Recommendation | Enter the resolution for this issue, if known. |
Steps To Reproduce | Enter the steps needed to recreate this issue. |
Category/Classification | Click to choose from a pre-defined category; click Done. |
Reporting Organization | By default, shows your company name. If you need to change it, click to search for the needed organization; click Submit. |
Policy | Shows as Issue; you cannot change the policy unless your company has developed additional policies. |
Notes | Add additional information about the problem. |
Received Date | Click to enter the date the issue was reported. |
Response Due Date | Click to enter the date a response is scheduled to be sent. |
Response Sent Date | Click to enter the date a response to the issue was sent. |