<?xml version="1.0"?>
<rss version="2.0">
<channel>
  <title>The EGI blog - request tracker tag</title>
  <link>http://www.egi.eu/blog/tags/request tracker/</link>
  <description>Behind the scenes of EGI</description>
  <language>en</language>
  <copyright>Blog Owner</copyright>
  <lastBuildDate>Mon, 15 Apr 2013 15:57:00 GMT</lastBuildDate>
  <generator>Pebble (http://pebble.sourceforge.net)</generator>
  <docs>http://backend.userland.com/rss</docs>
  
  
  <item>
    <title>EGI user support requirements publicity</title>
    <link>http://www.egi.eu/blog/2012/02/22/egi_user_support_requirements_publicity.html</link>
    
      
      
        <description>
          In the beginning when the requirements tracking (RT) system was setup it was not publicly accessible, it required to have an EGI SSO (Single Sing-On) in order to submit new requests or to see the existing user support requirements. That led to many ...
        </description>
      
    
    
    
    <category>User Community</category>
    
    <comments>http://www.egi.eu/blog/2012/02/22/egi_user_support_requirements_publicity.html#comments</comments>
    <guid isPermaLink="true">http://www.egi.eu/blog/2012/02/22/egi_user_support_requirements_publicity.html</guid>
    <pubDate>Wed, 22 Feb 2012 15:24:00 GMT</pubDate>
  </item>
  
  </channel>
</rss>
