<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Jivespace Community Blog</title>
    <link>http://www.jivesoftware.com/jivespace/blogs/jivespace</link>
    <description>Jivespace Developer Community Blog</description>
    <pubDate>Fri, 12 Sep 2008 15:35:56 GMT</pubDate>
    <generator>Clearspace 2.5.3 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2008-09-12T15:35:56Z</dc:date>
    <item>
      <title>Jive Support changes up Severity Levels  on cases</title>
      <link>http://www.jivesoftware.com/jivespace/blogs/jivespace/2008/09/12/jive-support-changes-up-severity-levels-on-cases</link>
      <description>&lt;!-- [DocumentBodyStart:e85144a9-97f8-4571-9f30-a3f574562f81] --&gt;&lt;div class='jive-rendered-content'&gt;&lt;p&gt;Over the past months we have come to the realization that when it comes to severity of your cases it really comes down to 3 levels:&lt;/p&gt;&lt;h3&gt;1. &lt;span&gt;Critical&lt;/span&gt;&lt;/h3&gt;&lt;p&gt;Either your &lt;strong&gt;production &lt;/strong&gt;site is down (cannot be accessed) or there is a problem affecting the users in such a way that the site is &lt;strong&gt;unusable&lt;/strong&gt;. This includes (but is not limited to) events like: Cannot post a discussion, cannot add a comment to a blog post, cannot login, etc.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;When events like this happen, please reach out to Support as soon as possible to quickly get things assesed and corrected. The easiest way to do that is to create a case in your support community, and choose the severity '&lt;strong&gt;Critical&lt;/strong&gt;.'&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h3&gt;2. &lt;span&gt;Medium&lt;span style="font-weight: normal;"&gt; &lt;/span&gt;&lt;/span&gt;&lt;/h3&gt;&lt;p&gt;While a Medium Severity issue may still be happening on your production site, it only has minor business impact, resulting in some functionality loss.&amp;nbsp; This can include (again, not limited to) things such as formatting errors, page layout issues, webservices bugs, etc. We know there is sometimes a fine line between &lt;strong&gt;medium &lt;/strong&gt;and &lt;strong&gt;critical&lt;/strong&gt; issues, but we trust you to use your best judgement. If we perceive an issue as mis-categorized, we may change the severity level and explain to you why we have done so.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h3&gt;3. &lt;span&gt;Low&lt;/span&gt;&lt;/h3&gt;&lt;p&gt;This is the last severity level. This is intended to bucket all remaining issues that are happening on your staging, UAT, or development site, problems with a widget you are writing, questions on a feature, best practices, &lt;strong&gt;feature requests&lt;/strong&gt;, etc. All issues relating to a &lt;strong&gt;non-production&lt;/strong&gt; site will be re-assigned to &lt;strong&gt;low&lt;/strong&gt; by Jive Support if initially categorized as medium or critical.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;When choosing a severity level please keep in mind that there are exceptions to every rule; each company has their own priorities and criteria for defining what is 'mission critical' to their Clearspace instance and business success. We want to accurately understand the impact of each issue you submit, and we feel that moving to &lt;strong&gt;3 severity levels&lt;/strong&gt; will help us accomplish this to a higher extent.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Your feedback is welcome.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Thanks,&lt;/p&gt;&lt;p&gt;Jive Support&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:e85144a9-97f8-4571-9f30-a3f574562f81] --&gt;</description>
      <category domain="http://www.jivesoftware.com/jivespace/blogs/jivespace/tags">support</category>
      <category domain="http://www.jivesoftware.com/jivespace/blogs/jivespace/tags">severity</category>
      <pubDate>Fri, 12 Sep 2008 15:35:56 GMT</pubDate>
      <author>Will</author>
      <guid>http://www.jivesoftware.com/jivespace/blogs/jivespace/2008/09/12/jive-support-changes-up-severity-levels-on-cases</guid>
      <dc:date>2008-09-12T15:35:56Z</dc:date>
      <clearspace:dateToText>2 months, 1 week ago</clearspace:dateToText>
      <wfw:comment>http://www.jivesoftware.com/jivespace/blogs/jivespace/comment/jive-support-changes-up-severity-levels-on-cases</wfw:comment>
      <wfw:commentRss>http://www.jivesoftware.com/jivespace/blogs/jivespace/feeds/comments?blogPost=1595</wfw:commentRss>
    </item>
    <item>
      <title>Improved Support Process!</title>
      <link>http://www.jivesoftware.com/jivespace/blogs/jivespace/2008/05/19/improved-support-process</link>
      <description>&lt;!-- [DocumentBodyStart:34381b42-6710-4ec7-bb31-a9e87594e05d] --&gt;&lt;div class='jive-rendered-content'&gt;&lt;h3&gt;&lt;span&gt;Customer Portal Launching!&lt;/span&gt;&lt;/h3&gt;&lt;p&gt;On Monday, May 19th, we launched a new support solution to provide our customers with a better support experience.&amp;nbsp; We are moving from our old email based system, to leveraging our Jive Communities ClearspaceX instance to provide discussion based support via cases.&amp;nbsp; What does this mean for you?&amp;nbsp; Well there are a lot of high level benefits:&lt;/p&gt;&lt;ul&gt;&lt;li level="1" type="ul"&gt;&lt;p&gt;No more losing emails in the internet--attachments are particularly bad at causing this&lt;/p&gt;&lt;/li&gt;&lt;li level="1" type="ul"&gt;&lt;p&gt;You can now view all your cases with us, and check on the status&lt;/p&gt;&lt;/li&gt;&lt;li level="1" type="ul"&gt;&lt;p&gt;You can choose to make cases private or public--knowing that we will respond to both regardless of who can see them.&lt;/p&gt;&lt;/li&gt;&lt;/ul&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;There are some things to be aware of regarding the new processes:&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h3&gt;&lt;span&gt;What About my Existing Open Cases?&lt;/span&gt;&lt;/h3&gt;&lt;p&gt;All emails sent into Jive will be created as new cases--this will be the primary point for the case moving forward, although we will ensure that your cases' history is maintained so that we do not lose any context when solving your issue.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h3&gt;&lt;span&gt;Your "Personal" Community&lt;/span&gt;&lt;/h3&gt;&lt;p&gt;&lt;span&gt;When you log into Jive Community (this site), assuming you have an active support contract, and email address, you will now see a new community under the Support Community named after your company.&amp;nbsp; This is a community that only members of your company, and Jive can see.&amp;nbsp; Everything created in here is private.&amp;nbsp; If you are not seeing your Personal Community, please email &lt;/span&gt;&lt;a class="jive-link-email-small" href="mailto:accountsupport@jivesoftware.com"&gt;accountsupport@jivesoftware.com&lt;/a&gt;&lt;span&gt;.&lt;/span&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h3&gt;&lt;span&gt;Email&lt;/span&gt;&lt;/h3&gt;&lt;p&gt;You can still send emails, and the system will automatically process and publish them online.&amp;nbsp; As long as you have an account with a valid email address, email will work just fine.&amp;nbsp; Additionally, assuming you have not disabled your watches, you will receive a watch update when we (or someone else if public) responds to your case.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h3&gt;&lt;span&gt;Keeping Track of Cases&lt;/span&gt;&lt;/h3&gt;&lt;p&gt;&lt;span&gt;After logging in, just navigate to your personal space (your company name).&amp;nbsp; If you don't see it, email &lt;/span&gt;&lt;a class="jive-link-email-small" href="mailto:accountsupport@jivesoftware.com"&gt;accountsupport@jivesoftware.com&lt;/a&gt;&lt;span&gt;.&amp;nbsp; Within your space, you will see all your open cases on the overview tab, and a complete history of all your cases on the cases tab.&amp;nbsp; Please note, that due to the new solution, cases processed using the email system will not show up.&lt;/span&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h3&gt;&lt;span&gt;How Can my Co-Workers Submit Cases?&lt;/span&gt;&lt;/h3&gt;&lt;p&gt;&lt;span&gt;Assuming we have a record of your coworker (if not, just email &lt;/span&gt;&lt;a class="jive-link-email-small" href="mailto:accountsupport@jivesoftware.com"&gt;accountsupport@jivesoftware.com&lt;/a&gt;&lt;span&gt;), all your coworker needs to do is create an account on jivesoftware.com/community using their work email address, and then they will also see your personal company space.&amp;nbsp; Additionally, your co-worker will also see all your cases, their status, and can create cases themselves.&lt;/span&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h3&gt;&lt;span&gt;What are Private and Public Cases?&lt;/span&gt;&lt;/h3&gt;&lt;p&gt;When you create a case, you have an option to make it public, and to select in which community you want to create the case.&amp;nbsp; The default however is private.&amp;nbsp; We have this set to protect your security, and to ensure that any public information is intentionally shared.&amp;nbsp; When a public case is created it shows up as a discussion in the community you chose.&amp;nbsp; Others can see and respond to your case just like a discussion--in fact they won't even know that it is a case!&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;When creating the case do not worry if you need to make it private later on.&amp;nbsp; You can make a case public or private at any point throughout the case's history.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Please give us your feedback and let us know what you think.&amp;nbsp; We are constantly striving to improve your experience with Jive Support!&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h3&gt;&lt;span&gt;How to set up/use your new space&lt;/span&gt;&lt;/h3&gt;&lt;p&gt;The attached document contains step by step instructions with screenshots on how to access your private community.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:34381b42-6710-4ec7-bb31-a9e87594e05d] --&gt;</description>
      <category domain="http://www.jivesoftware.com/jivespace/blogs/jivespace/tags">supportal</category>
      <category domain="http://www.jivesoftware.com/jivespace/blogs/jivespace/tags">customer_portal</category>
      <category domain="http://www.jivesoftware.com/jivespace/blogs/jivespace/tags">support_site</category>
      <category domain="http://www.jivesoftware.com/jivespace/blogs/jivespace/tags">support</category>
      <category domain="http://www.jivesoftware.com/jivespace/blogs/jivespace/tags">support_process</category>
      <category domain="http://www.jivesoftware.com/jivespace/blogs/jivespace/tags">case</category>
      <category domain="http://www.jivesoftware.com/jivespace/blogs/jivespace/tags">case_submission</category>
      <pubDate>Mon, 19 May 2008 22:00:26 GMT</pubDate>
      <author>kevin</author>
      <guid>http://www.jivesoftware.com/jivespace/blogs/jivespace/2008/05/19/improved-support-process</guid>
      <dc:date>2008-05-19T22:00:26Z</dc:date>
      <clearspace:dateToText>8 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>8</clearspace:replyCount>
      <wfw:comment>http://www.jivesoftware.com/jivespace/blogs/jivespace/comment/improved-support-process</wfw:comment>
      <wfw:commentRss>http://www.jivesoftware.com/jivespace/blogs/jivespace/feeds/comments?blogPost=1409</wfw:commentRss>
    </item>
    <item>
      <title>Jive Engineering's Release Process for Clearspace</title>
      <link>http://www.jivesoftware.com/jivespace/blogs/jivespace/2008/04/10/jive-engineerings-release-process-for-clearspace</link>
      <description>&lt;!-- [DocumentBodyStart:3970d1f3-0d56-4580-b90c-42608920ac27] --&gt;&lt;div class='jive-rendered-content'&gt;&lt;p&gt;As some of you might have already noticed, Marty Kagan, our VP of Engineering, recently blogged about &lt;a class="jive-link-external-small" href="http://www.jivesoftware.com/community/blogs/jivetalks/2008/01/18/clearspace-1x-2x-and-jives-new-release-train"&gt;what is going on with Clearspace&lt;/a&gt;.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;We really listened to our customers' feedback, and created what we believe is the best of both worlds, getting customers the latest features, while ensuring customers are on a supported version, with availability for patches.&amp;nbsp; This last bit is critical as it means that one-off patches for bugs will no longer be going out to a single customer.&amp;nbsp; Instead, fixes will be rolled into patch releases on a regular basis so that all customers can benefit from known reported bugs.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Let us know what you think!&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:3970d1f3-0d56-4580-b90c-42608920ac27] --&gt;</description>
      <category domain="http://www.jivesoftware.com/jivespace/blogs/jivespace/tags">release_cycle</category>
      <category domain="http://www.jivesoftware.com/jivespace/blogs/jivespace/tags">release_train</category>
      <category domain="http://www.jivesoftware.com/jivespace/blogs/jivespace/tags">clearspace</category>
      <category domain="http://www.jivesoftware.com/jivespace/blogs/jivespace/tags">releases</category>
      <category domain="http://www.jivesoftware.com/jivespace/blogs/jivespace/tags">patches</category>
      <category domain="http://www.jivesoftware.com/jivespace/blogs/jivespace/tags">support</category>
      <pubDate>Thu, 10 Apr 2008 23:01:59 GMT</pubDate>
      <author>kevin</author>
      <guid>http://www.jivesoftware.com/jivespace/blogs/jivespace/2008/04/10/jive-engineerings-release-process-for-clearspace</guid>
      <dc:date>2008-04-10T23:01:59Z</dc:date>
      <clearspace:dateToText>10 months, 3 days ago</clearspace:dateToText>
      <wfw:comment>http://www.jivesoftware.com/jivespace/blogs/jivespace/comment/jive-engineerings-release-process-for-clearspace</wfw:comment>
      <wfw:commentRss>http://www.jivesoftware.com/jivespace/blogs/jivespace/feeds/comments?blogPost=1374</wfw:commentRss>
    </item>
    <item>
      <title>Support Community joins Developer Community on ClearspaceX!</title>
      <link>http://www.jivesoftware.com/jivespace/blogs/jivespace/2008/01/09/support-community-joins-developer-community-on-clearspacex</link>
      <description>&lt;!-- [DocumentBodyStart:d61ac816-d31f-4944-b4b0-bff0ae6e258c] --&gt;&lt;div class='jive-rendered-content'&gt;&lt;p&gt;As many of you have already noticed our Jive Integrated support instance on jivesoftware.com/jive has joined the &lt;a class="jive-link-external-small" href="http://www.jivesoftware.com/community/community/developer"&gt;developer community&lt;/a&gt; on our Jive Community ClearspaceX instance at &lt;a class="jive-link-external-small" href="http://www.jivesoftware.com/community"&gt;http://www.jivesoftware.com/community&lt;/a&gt;.&amp;nbsp; Through user feedback, we re-integrated the &lt;a class="jive-link-external-small" href="http://www.jivesoftware.com/community/community/support"&gt;support&lt;/a&gt;and &lt;a class="jive-link-external-small" href="http://www.jivesoftware.com/community/community/developer"&gt;developer&lt;/a&gt;communities within a single site to improve your experience.&amp;nbsp; You should now have much less trouble deciding where to post--depending on whether the question is a developer related question or a support related question all on the same instance.&amp;nbsp; For users of our old instance, all information from our old site was migrated to this new location.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;With this move not only comes a better user interface and integrated user community but also provides Jive Support with the ability to create periodic blog posts.&amp;nbsp; Jive Support Engineers will be blogging on best practices we use ourselves when troubleshooting or improving our products' environments.&amp;nbsp; Please let us know if&amp;nbsp; &lt;/p&gt;&lt;p&gt;there is anything in particular you want to know more about!&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Thanks,&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Kevin Williams&lt;/p&gt;&lt;p&gt;Jive Support Manager&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:d61ac816-d31f-4944-b4b0-bff0ae6e258c] --&gt;</description>
      <category domain="http://www.jivesoftware.com/jivespace/blogs/jivespace/tags">support</category>
      <category domain="http://www.jivesoftware.com/jivespace/blogs/jivespace/tags">welcome</category>
      <category domain="http://www.jivesoftware.com/jivespace/blogs/jivespace/tags">clearspacex</category>
      <category domain="http://www.jivesoftware.com/jivespace/blogs/jivespace/tags">community</category>
      <pubDate>Wed, 09 Jan 2008 18:40:30 GMT</pubDate>
      <author>kevin</author>
      <guid>http://www.jivesoftware.com/jivespace/blogs/jivespace/2008/01/09/support-community-joins-developer-community-on-clearspacex</guid>
      <dc:date>2008-01-09T18:40:30Z</dc:date>
      <clearspace:dateToText>10 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
      <wfw:comment>http://www.jivesoftware.com/jivespace/blogs/jivespace/comment/support-community-joins-developer-community-on-clearspacex</wfw:comment>
      <wfw:commentRss>http://www.jivesoftware.com/jivespace/blogs/jivespace/feeds/comments?blogPost=1357</wfw:commentRss>
    </item>
  </channel>
</rss>

