Serena Software, Inc.
March 2011
If this is the first time you have installed Agile on the server, follow the detailed instructions in the Serena Agile Deployment Guide.
If you are upgrading to this release, you must first upgrade the application and then migrate the database. The steps needed to migrate your database depend on the version of the application that you are currently using. Performing a migration using tools that don’t match your version can result in database corruption. It is critical that you follow the correct upgrade and migration path. Detailed installation steps for each path can be found on the KB:
We STRONGLY RECOMMEND that Customers deploy all service releases, service packs and patches to a test environment before deploying to a production environment. A test environment should have:
After deploying to the test environment, testing should be performed on all user activities prior to deployment in production. Proper industry practice is to always complete a backup before deploying software, including new installs or updates of any kind. Thus, before deploying this release, the host environment should be prepared as follows:
Serena Agile has been rebranded to Serena Agile Planner. Rebranding a product is never an easy decision but we feel that this better aligns with the complementary nature of our Agile product within the broader Application Lifecycle Management (ALM) set of solutions that Serena offers. Along with rebranding the product we have also changed the version numbering moving away from year versions (2010 R2) back to standard numbering (2.3). This allows us to better designate major versus minor releases reducing customer confusion.
You can now attach documents to user stories and all other work item types including custom types you have set up. This functionality is in addition to the ability to attach documents to projects, releases, and sprints. Finding and opening documents is easy using Serena Agile Planner's search functionality. Documents can also be versioned and categorized into folders.
We have enhanced the ability to display and share URLs for user stories and all other work item types including custom types you have setup. You can right-click and copy a URL for a user story or copy it from the user story details view and then paste it into an email. Work item URL's can also be listed in reports and then exported to excel.
Development teams who use Atlassian Jira to manage day-to-day activities can now synchronize user stories, defects, and tasks between Agile Planner and Jira. This rich bi-directional integration for on-premise deployments of Agile Planner allows stakeholders to plan and monitor releases without requiring developers to leave their native development tools to provide progress updates.
For a complete list of fixes in Serena Agile Planner 2.3, refer to this query in the Serena Support Knowledgebase.
Notifications from private queues in Microsoft Message Queueing (MSMQ) fail on Windows 2003 R2 servers. To work around this issue, enable all permissions for all users of the MS Message Queue. Please see the following Knowledgebase article for more information: http://knowledgebase.serena.com/InfoCenter/index?page=content&id=S130946
Copyright © 2011 Serena Software, Inc. All rights reserved.