Skip to main content (Press Enter).
Sign in or Join
Skip auxiliary navigation (Press Enter).
Start a Discussion
Post an Article
User Community
Skip main navigation (Press Enter).
Toggle navigation
Content types
Announcements
Blogs
Communities
Discussions
Events
Glossary
Site Content
Libraries
Date range
on this day
between these dates
Posted by
Home
Top Links
Supported Software
Release Notes
Jama 8.x Deployment Resources
Help Guide Online
Help Guide PDFs
Integrations
Announcements
Glossary
What's New
Support
Post a question or problem
Member-created Resource Library
Education
Get to know Jama Connect
Creating & Editing Items
Collaboration & Traceability
Office Reports
Review Center
Test Management
Administration
Release Management
Reuse & Sync
BIRT Advanced Reporting
Velocity Advanced Reporting
REST API
License Type
Risk Management Center
System Administration
All Topics
Services Practices
Product
User Research Group
Product Discussion
Ideation
Knowledge Base
View Only
Community Home
Library
3
Events
0
Members
260
Back to Blog List
Named Support Contacts Explained
By
Megan
posted
08-16-2019 09:02
Options Dropdown
Mark as Inappropriate
0
Like
Greetings Community,
As a part of your
Maintenance and Support
contract with Jama, Support issues raised via ticket need to be directed through your company’s Named Support Contacts (NSCs). There are several reasons why this is important:
Process: Many of our customers have an internal team that supports Jama; directing requests through this team ensures internal processes and expertise are honored.
Security: Often times Jama Support is engaged to request system changes (particularly in the case of our hosted environment) and we want to be sure we are dispensing this advice to the individuals responsible for the overall health of Jama. For this reason we do not allow distribution lists, list serves, or shared inboxes to be designated as NSCs.
Domain Expertise: Each customer uses Jama differently and routing questions through your company’s Named Support Contacts ensures that business process or unique use cases are considered and addressed.
Cloud customers require functional contacts: these are contacts who act as local Jama Connect experts, have Org Admin permissions, have received training on using the tool and understand company use cases.
Self-hosted customers should have sys admin contacts in additional to the functional contacts described above. Sys admins are necessary if there are performance or unavailability issues in Jama Connect. We expect a Linux admin with permissions to app server and a database admin with knowledge of the type in use locally. One contact must be available between 9 a.m. and 5 p.m. Pacific.
If a non-Named Support Contact reaches out to Support, we will kindly ask that them to direct their question through the Named Support Contact. Please note, it is possible for non-Named Support Contacts to participate in Support requests by being Cc’d on the ticket. Lastly, if for any reason you need to update the Named Support Contacts listed for your organization, please have a designed Support Contact request to update your NSCs via the form at the top of the
support.jamasoftware.com
portal. All customers may start discussions or submit questions on the Community, however.
Thank you for your understanding and please do let us know if you have any questions.
0 comments
1087 views
×
Reason for Moderation
Describe the reason this content should be moderated (required)
Permalink
© Jama Software
HEADQUARTERS
|
135 SW Taylor Suite 200, Portland, Oregon, 97204
Code of Conduct
Privacy
Security
Legal
Preferences
Contact Us
Powered by Higher Logic