Access to Sitecore Support is offered through the Sitecore Support Portal available at https://support.sitecore.net. To log in, you should use the same e-mail and password as used for http://sdn.sitecore.net.
To be granted access to Support Portal, the following prerequisites must be met:
- A user must have passed one of the following Sitecore certification exams:
- Sitecore Experience Solution Developer
- Sitecore Website .NET Developer
- A user must be representing an active Sitecore Partner or Sitecore Customer.
- A user must have a valid Sitecore License ID available when opening a support ticket. More information can be found here: https://kb.sitecore.net/articles/073804
A few legacy certification types that are no longer provided to new users are also valid for getting support access.
For users without the valid Sitecore certification but who wish to track status of their colleagues' support tickets, read-only access can be granted.
For all related questions, you should contact your regional Sitecore representative. Find contact information about your local Sitecore office at http://www.sitecore.net/About/Contact.aspx.
Important: You must not let other people use your personal Sitecore account. Accessing the Sitecore Support Portal with another person's account is a violation of Sitecore security policy.
On Sitecore Support Portal, every support ticket is linked to a company that the user is associated with at the time of opening such a ticket.
This means the following aspects in regards to access to support tickets:
- All users from the same company are able to both see and modify all tickets associated with this company.
- When a user gets associated with a new company, he also loses access to old support tickets. Related tickets remain accessible only to the users associated with the original company.
When having problems with ownership of or access to support tickets, please contact your regional Sitecore office.
After you log in to the Sitecore Support Portal, you are presented with the list of the existing support tickets for your company. This list includes tickets that have been reported by your colleagues.
The list typically contains the following columns:
Issue Id: The Sitecore ID of the issue. The smaller the number — the older the issue.
Issue Subject: The subject of the issue.
Last Modified Date: The date and time of the last action that was taken on this issue. If a solution or question has been added to the issue this action will change the date and time displayed in the issue.
Customer Contact: The name of the employee who created/edited the issue.
State: The status of the issue. An issue can be in one of the following states:
- The initial state of the issue.
- Waiting for Sitecore:
- A dedicated Sitecore Support engineer has been assigned to the issue and you can expect to receive a response. An email notification is sent to the originator of the issue every time the issue is updated.
- Waiting for Customer:
- Sitecore Support has updated the issue with additional information or some follow-up questions. Please see the issue description field for details.
- We may have requested a more detailed reproduction scenario.
- A possible solution to your issue may have been provided and you are asked to attempt to implement that solution and tell us about the results.
- Issues in the 'Waiting for Customer' state will be moved automatically to the 'Closed' state in 3 weeks of inactivity. Do not worry though, we will always send you an email reminder to give you a chance to prevent the issue from being closed automatically if you need additional time to respond to us.
- If you edit an issue in this state, the issue is moved automatically to the 'Waiting for Sitecore' state within a couple minutes.
- Pending Closed:
- Issues in the 'Pending Closed' state will be moved automatically to the 'Closed' state after one week of inactivity.
- Issues in the 'Pending Closed' state can be reopened/edited.
- If you edit an issue in this state, the issue is moved automatically to the 'Waiting for Sitecore' state within a couple of minutes.
- Issues in the 'Closed' state cannot be edited.
- If an issue has been closed and you want reopen it, you must create a new issue and include the ID to the old issue for reference purposes and provide any additional information you might have. Sitecore engineer will continue working on your problem using the newly created issue.
State Details: Indicates the details of the issue, such as the results of the Sitecore product related root cause analysis. The available state details are:
- No details are available.
- Bug Reported:
- A bug report for one of Sitecore products was created in relation to the current issue.
- Wish/Feature Requested:
- A wish or feature request was created in relation to the current issue.
To create a new support issue for Sitecore Support:
Click the “Add” button.
Fill out the fields with appropriate data, click Save or Save & Close.
Purpose of each of the fields is described below:
- Issue Subject: A name that describes the nature of the issue. Issue subject must be informative and correspond to the issue description.
- Impacted User Group, Impact Level: This information will be used to help prioritizing your support ticket. More details about ticket prioritization can be found at https://kb.sitecore.net/articles/583182
- Preferred Support Team Location: This gives us an indication for where the person reporting the issue is located, and allow us to assign the ticket to the corresponding support team to allow faster communication.
- License ID: Sitecore License ID associated with the current project. More details can be found at https://kb.sitecore.net/articles/073804
- Description: Click the "Stamp” button to add a date-time stamp. Then add a detailed description below on how to reproduce the problem, what symptoms are observed, etc.
- Product, Product Version: Select the name and version of the impacted Sitecore product.
- Module, Module Version: Select the name and version of the impacted Sitecore module. If your request is not related to any Sitecore modules, select the “No Related Module” point in the Module field.
- Web Server OS: OS of your web server machine.
- Browser: Internet browser used on the client machine.
- Environment: Gives us an indication of the severity of the issue.
Important! Always follow Support Portal Best Practices documented at https://kb.sitecore.net/articles/004553
There are two ways to edit a support ticket:
The editing window will allow you write access to the same fields that you used when creating the support ticket.
Important! Communication with Sitecore Support happens through the Description field. To maintain the top down order of comments that is required for clarity, you should use the "Stamp" button before writing a comment for the current issue.
Finally, when you have finished: use one of the "Save" buttons.
There are two ways to add attachments.
Using the right sidebar on the multiple tickets view:
- If the "Details" sidebar is hidden, click the arrows on the right.
- Click on an issue in the table.
- Click on the word "Attachments" in order to make the upload UI appear.
- If you do not see the "Attachments" tab, make sure that it is enabled.
- Click the "Add" button to add the attachments.
Using the "Attachments" tab in a single ticket view:
- Select an issue in the table and click the "View" button. This issue will be opened in the new window.
- Click the "Add" button on the "Attachments" tab that is located at the bottom of the ticket view.
Important note: 1 month after the support ticket is closed, associated attachments are automatically cleaned up. This excludes assembly files and code samples provided by Sitecore Support representatives.
Problem: My username and password is not accepted by the Sitecore Support Portal.
Solution: Consider the following situations:
If you are a certified Sitecore Developer representing a Sitecore Partner or a Sitecore Customer:
Check your login at https://profile.sitecore.net.
If it does not work, use the Forgot Password functionality.
If you are still not able to log in to the Sitecore Support Portal, please contact your regional office with the following info:
Your e-mail, your Sitecore Certification, the name of your current employer.
If you represent a Sitecore Partner or a Sitecore Customer, but not yet a certified Website .NET Developer for Sitecore:
Contact your regional office to pass a certification as Website .NET Developer for Sitecore.
If you are a project leader without Sitecore certification, but want to administer tickets opened by your company:
We are able to offer you a read-only access. Contact your regional Sitecore office and request a project leader read-only access.
Problem: I can access the portal, but I cannot see all my issues.
Solution: Check the values of the filter setting and search box in the portal. Set the filter to “All Issues”, clear the search box and press "Enter" (see the screenshot below).
Problem: My web browser does not work very well with your support portal.
Solution: There is a list of the currently supported browsers:
- Internet Explorer 7(limited support)/8/9/10/11
Problem: My web browser is in the list of the supported browsers, but it does not work all the same.
Solution: Clear the browser cache, cookies and temporary internet files. After that, restart the browser. If the problem persists, contact your regional Sitecore office.
For additional important resources related to interacting with Sitecore Support, please refer to this page: