Following Bug Fixes and enhancements were released this week,
1) Est Points field is not available on the Defects forms or Views: Estimated points field is now available on Add Defect and Edit Defect screens.
2) Moving Defects from a Release to a Sprint lost all point estimates.
3) % Full is Iteration – Participant tab show more that 2 digits after decimal point.
4) To Do Hours not editable on the Defects form when Timesheet is enabled.
5) Splitting the story and changing release of new split story in Split Story Screen does not change the release of tasks in story
6) Cannot edit and add iteration once all Burndown days checkboxes are turned off: Now you need to have at least one burndown day. AgileWrap gives error if all Burndown days checkbox are turned off.
7) Split story’s tasks do not get scheduled in the split story’s iteration.
1) Now comments display the date a comment was entered in addition to the number of days.
After we moved AgileWrap on Amazon EC 2 on August 22nd, many users reported slow down in AgileWrap. Our team finally tracked down it to some rouge batch processes and a missing index and fixed those on August 28th. Since then we were pleased to report that AgileWrap has been performing very well except for the User Story Page which is slow for some users. Our team is working on improving the performance User Story page.
Only Admin users can now view inactive team members in Setup >> Team Member list. Team members with non admin roles will not see inactive users in Setup >> Team Member list.
Following bugs were fixed,
1) Burndown: In some instances, the estimated hours shown in the table under the burndown was showing till 25 decimal places. Fixed to show only 1 decimal place.
2) Sometimes Edit Team Member screen defaulted the cached password from browser in password field. This stopped user from saving the changes to the team member. This has been fixed.
3) Filtering on story number in User Story page did not show the correct story. Fixed.
4) For time sheet enabled projects, Users could not edit To Do hours from Edit Defect screen. Fixed.
5) Search index was corrupted due to a configuration issue during migration to Amazon Ec2. This was fixed.
This weekend we moved AgileWrap to Amazon EC2 and Multi AZ RDS database.
1. Now we have hot standby synchronous replica of AgileWrap Database using Amazon’s Multi AZ feature. In case main DB fails, AgileWrap DB will automatically fail over to the standby database. This is in addition to daily full backups which are kept onsite and offsite.
2. We have added more servers. We can now increase our server capacity very quickly as load and number of users increase.
We are working many more enhancements. Please stay tuned for more announcements on this blog.
Today we launched enhanced Burndown chart. Enhancements are:
- Burndown chart now starts a day before the sprint start date. This provides the reference start point for the starting estimated effort.
- Scope change line: A new line is now displayed on chart which shows scope change.
- Forecast completion date: To Do line now extends as dashed line to show expected completion date. Forecast line is calculated based on assumption that team will burn ideal burn hours every day in future.
- View prioritized ToDo: Your ToDo will show all the open items (user stories, tasks and defects) assigned to you as owner (or reviewer) by the ascending order of due date. If you have not marked Due Date of an item then AgileWrap will use the end date of its iteration/release as item’s due date and will display it in the corresponding spot in your ToDo. Open items are the items that have status as New, In Progress, Defined and Reopen.
- View rank of an item in ToDo: If an item is scheduled in an iteration/release then this items will show its Rank as assigned in the iteration backlog or release backlog next to the item type icon. If you own an item that belongs to the product backlog then this item will show as one of the last items in your ToDo because product backlog does not have any end date. Since AgileWrap allows to rank only user stories and defects, your Task items will follow rank of their user stories as assigned within an iteration/release backlog. Parent user stories are usually not assigned to a member. But if a parent story is assigned to you then it will show in your ToDo as the last item. Here is the logic AgileWrap uses to determine the priority of an item in your ToDo -
- Items in the ascending order of given due date
- Items in the ascending order of the end date of iteration/release
- Items belonging to the product backlog
- Parent user stories if assigned (parent user stories do not belong to any iteration/release/product backlog.
- View items owned and to review in ToDo: Use checkboxes on top to view open items that are assigned to you as Owner, and . You can also view items, set to To Verify, that are assigned to you as Reviewer.
- Moving item on top of ToDo: You can personalize your ToDo by moving an item to the top of the ToDo list and moving it back to its original spot when required. Click on grey up arrow icon on the left most end of a row to move this item to the top. Once the item is moved up it will show arrow pointing downward. Click on the downward arrow and AgileWrap moves this item back to its original location.
- Overdue items in pink: Items that has passed current date show in pink color. Items that are due today show in light blue color.
- Ease of use: We removed Group By filter. We also reordered few columns for ease of use.
- How to enable TimeSheet for a Project
- How does TimeSheet work
- Create time entries for Spent Hours (of a task and defect) for different team members.
- View time sheet for a specific period for multiple team members for multiple projects.
- View time sheet of all the team members by projects.
- Print time sheet.
We have added “Print Views” for User Story, Task And Defect Detail pages. On Plan>>User Story page you can select the story on the grid and click on the “Print User Story”. This will open up a printer friendly view in separate browser window. You can print the printer friendly page using the browser’s print function.
Similarly, Print has been also added to Track>>Defects, Track>>Tasks and User Story, Task and Defect detail pages.
1. View user story along with its tasks
2. Importing user stories
We improved importing of user stories by removing few constraints in the preparation of the source file (.csv file). Now there are only three mandatory fields for a story row on the source file: story name, priority and status. Since owner field is no longer mandatory, you need not create team members before running the import process.
You can import many optional additional fields for user story: story description, owner, blocked status, URL to External document, estimated points, iteration and release. For more help – view detail information on importing user stories here.
Today in AgileWrap 3.4.1 release we launched few enhancements and many bug fixes.
- Now you can view all the audit events performed by a specific user. When you go to Analyze>>Reports>>Audit Log Report, you can select a user from Owner drop-down and see all the audit events for that user.
- Now you can maximize and minimize popup windows by clicking on max/min icon on top right of the window. This provides greater view area especially if item description is very long. This feature is implemented for all Add, Edit and View popup windows.
- You can now resize the Description (in rich text editor) field in Add and Edit User Story popup screens.
- On Home>>ToDo page, when you inline edit Due Date for a row, whole screen does not refresh. Instead, only edited row is refreshed.
- AgileWrap now does not allow an ‘Admin’ user to change his role if he is the only active user with ‘Admin’ role. Now you do not need to contact AgileWrap Support for help because you cannot change your Admin role accidently.
- You can now schedule (and un-schedule) a user story in a Release or iteration from Add and Edit User Story popup windows. This is allowed for only leaf level user stories. This enhancement was launched on 29th Jan.
- AgileWrap now does not give error when you enter 12/31/9999 as date for a Project, Sprint or Release.
- User Story Description now shows properly formatted in View User Story popup window.
- In IE, User Story Description now saves properly in Edit/Add User Story popup windows.
- When you edit a user story or defect on Plan>>Backlog page, then all the rows show on refresh.
- ‘My Alert’ widget on Home>>My Dashboard page now displays correct commentator name for a user story, task and defect.
- In Add/Edit/View popup windows for Task and Defect, Due Date now displays in current user’s preferred date format.
- Release and iteration for a user story (if given) are not reset when a user edits a user story using Edit User Story Popup.
- Audit Log Report now shows “Project” instead of “P” for project level audit events. You can access Audit Log Report from Analyze>>Reports tab.
AgileWrap is now available on iPad using Safari browser. Use the same website URL http://www.agilewrap.com or https://product.agilewrap.com/login that you use on desktop or laptop. There is no learning curve as it is exactly the same application. There is nothing to download or install.
Using iPad, you can now view status of your project, milestones and releases. You can see your own tasks and update status. You can create and edit Story, Defects and Tasks. You can pretty much do most of the things on AgileWrap on iPad as you can do on your computer with only a few exceptions.
AgileWrap for iPad supports all AgileWrap features except:
- Inline editing is not supported but you can edit using edit link. Most screens show you context specific links to edit. Click on edit link and pop up window appears. Edit using this window and save.
- You can view the product plan using Plan Product but you cannot do planning as Drag and Drop is not supported. But you can perform same function using the Add and Edit links. To schedule a Story or Defect in another iteration or release use edit.
- Drag and drop prioritization on Backlog Page and Plan Product page is not supported. To prioritize backlog you will need to access AgileWrap from a computer.
- You cannot import stories, defects and tasks from CSV files using iPad.
- You cannot upload files and attachments using iPad.
- You cannot add participants to an iteration using iPad.
Now while traveling or in meetings, just use AgileWrap on iPad to keep connected with your team and project.
AgileWrap now supports IE9. Earlier releases supported IE7 and IE8.
In order to use AgileWrap with IE9, we recommend that you download Google’s Chrome Frame for IE to get better performance and experience.
Known Performance Issues in IE 9
- User Story page loading can be slow especially when you are filtering the stories with tags. User Story page is accessed from Plan>>User Story and Track>>User Story tabs.
- Backlog page loading is slow (Plan>>Backlog tab).
- Charts performance is slow. You can access charts from Analyze>>Reports tab.
While we are working on performance improvements of AgileWrap for IE9, we recommend using Chrome (the best performance), Firefox and Safari (for good performance).