|
SC-WS-8 Main page is rendered prematurely
Problem: Poorly implemented redirection logic causes main page to be rendered prematurely which results in null-valued request parameters being evaluated prematurely, thus causing a Null Pointer Exception. Behaviour of the application server, Caucho Resin, used in our environments masqueraded the error. The error was revealed when Worklog Sheet was run in Apache Tomcat.
Fixed for: 0.2.2
SC-WS-7 JIRA API change between 3.12 and 3.13 for search requests
Problem: A significant change in the public interface of class SearchRequest between JIRA 3.12 and 3.13 caused Worklog Sheet not to function in 3.13.
Solution: Changed the way how search requests are retrieved.
Fixed for: 0.2.2
SC-WS-11 More compact issue list for past entries
Problem: Currently Worklog Sheet logic populates the issue drop-down list for past entries with all available user-specific issues. However in systems where there are many (hundreds) of issues this causes large drop-down lists that can cause performance issues.
Solution: Past entry retreival logic re-written.
Fixed for version: 0.2.4
SC-WS-10 User interface fixes
Tasks:
1. Header for past entries table
2. Page navigation links to top and bottom of past entries table
3. Integrate new entries table as a part of the main table
4. Hide "Select user" drop-down list if user has no permission to use user picker
Fixed for: 0.2.4
SC-WS-9 JIRA API change in search request manager
Problem: A significant change in the public interface of class SearchRequestManager between JIRA 3.12 and 3.13 caused Worklog Sheet not to function in 3.13 when fetching available filters in JIRA.
Solution: Changed the way how they are retrieved. Improved also plug-in build procedure to take version differences into account.
Fixed for: 0.2.4
SC-WS-13 Performance enhancements
Problem: In certain situations in systems with large amounts of issues per user, Worklog Sheet suffers from poor performance.
Solution: Enhancing performance by code optimization and by introducing more efficient algorithms.
Fixed for: 0.2.6
SC-WS-12 Null Pointer Exception in past entry retrieval logic
Problem: Lack of good null value detection caused unnecessary Null Pointer Exception in past entry retrieval logic.
Fixed for: 0.2.6
SC-WS-18 Peculiarity in validation behaviour causes empty fields to show in red
Task: Changed validation implementation in the way that empty fields in new entries are skipped altogether.
Fixed for: 0.2.10
SC-WS-17 JavaScript-based validation of fields prior to saving
Solution: Added content validation for the input fields in past and new entries lists.
Fixed for: 0.2.10
SC-WS-16 Informative text about filters to Worklog Sheet administration page
Task: Added an informative text to the administration page that helps in selecting an issue filter for Worklog Sheet.
Fixed for: 0.2.10
SC-WS-15 Refactoring of the new work log entry retrieval logic
Solution: Making the new work log entry retrieval logic to be more efficient and intuitive from user's point of view.
Fixed for: 0.2.10
SC-WS-14 Refactoring of work log entry retrieval logic for performance
Worklog Sheet suffers from poor performance when the JIRA instance contains large amounts of issues and/or work log entries. The work log entry retrieval logic is refactored in order to increase performance.
Fixed for: 0.2.10
SC-WS-24 Modifications in JIRA not visible in Worklog Sheet when session is active
Problem: Navigating to other parts of JIRA (i.e. away from Worklog Sheet) during a session leaves the Worklog Sheet session object bound to it. If changes are made to JIRA (e.g. issues are added) the chages are not visible in Worklog Sheet as the Worklog Sheet cache remains unchanged.
Solution: Added functionality that will refresh the cache if Worklog Sheet is left and returned.
Fixed for: 0.2.12
SC-WS-22 Improvements to permission checking
Task:
1. Hide issues from the issue list if the selected user has no permission to work on the issue
* Hide "Add New Entries" section altogether if the resulting issue list is empty for the selected user
2. Make past work log entry 'visible but disabled' instead of 'hidden' if selected user has no permission to edit it
Fixed for: 0.2.12
SC-WS-21 Bug in caching logic causes seemingly infinite caching loop when saving
Problem: If user has a large gap in entries and/or less than page full of them over a long period of time, the caching logic hangs in a seemingly infinite loop as it tries to fill the cache after saving has completed. This is a programmatical error in the logic and the logic needs to be corrected to take the above mentioned cases into account.
Work around: Work around is to test Worklog Sheet with a user that has more than one page worth of entries (10 entries from past 14 days). If the text "No entries found within the period of N days! Search for more... " is visible for a user, DO NOT press save or delete for that user. Go back and do testing with another users. If you in accident click you have to restart your server instance.
Solution: The post-save cache filling logic was redesigned completely to be more simplistic.
Fixed for: 0.2.12
SC-WS-20 Description field should not be mandatory
Problem: Worklog Sheet treats the work log entry description as a required field. JIRA treats the corresponding field as not mandatory and fills empty field with text "<No comments>".
Solution: Worklog Sheet should be changed to behave in similar fashion.
Fixed for: 0.2.12
SC-WS-19 Summary section
Task: Redesign and implementation of summaries as a section between past and new entries that displays the summary for past two weeks.
Fixed for: 0.2.12
SC-WS-27 User interface improvements
Problem:
* Administration page texts are too technical
* Worklog Sheet page user selection list looks awkward
Solution: Fixed the UI.
Fixed for: 0.2.14
SC-WS-26 Further performance enhancements
Problem: Worklog Sheet page rendering is still rather sluggish.
Solution: Improved the rendering speed by enhancing caching and by optimizing the source code. Also added performance indicators in the form of HTML comments and log messages.
Fixed for: 0.2.14
SC-WS-25 Bug in administration page causes the configured filter not to be displayed as selected
Problem: A bug in the administration page results in the configured filter not to be displayed as selected in the "Filter" drop-down list. This causes confusion as the filter displayed as selected in the list may not match the configured filter.
Solution: Fixed bug in value comparison logic.
Fixed for: 0.2.14
SC-WS-23 Current user filter abnormal behavior
Problem: Abnormal behavior when "current user" specific filter is used as active issue filter. As result user don't see other users work log, instead sees his own work done on other user's issues.
Solution: Change plug-in logic to cache user specific issue list with the user selected in pick user select box.
Fixed for: 0.2.14
SC-WS-2 JIRA date and time format
Task:
1. Option to use the same time format as found on issue "Log work done" page.
2. The summary field take into account the time tracking settings found at Administration pages
3. Configurable to select between "only date" and "date and time" (JIRA standard) for start date.
Fixed for: 0.2.16
SC-WS-32 NullPointerException in administration page (fresh installation)
Problem: A bug in properties file loading logic causes administration page when entering the administration page of a fresh (non-upgrade) Worklog Sheet installation. As result Worklog Sheet plug-in is completely unusable.
Fixed for: 0.2.18
SC-WS-33 Date only option does not work in Internet Explorer
Problem: When you select the 'Date Only' (not date/time) option, the calendar java popup does not work in Windows/IE (works in Firefox).
Solution : Preliminary investigations indicate that there is an extraneous comma in the enum structure that is used to initialize the calendar. The stricter JavaScript engine of IE interpretes this as a syntax error. Correcting this "typo" is a good course of action.
Fixed for: 0.2.18
SC-WS-35 JavaScript validation is not fully compatible with Internet Explorer
Problem: Internet Explorer does not like the way how the validation script handles "undefined" (null) field values.
Solution: Fix the validation script to be more cross-browser compatible.
Fixed for: 0.2.18
SC-WS-34 Date's day of month field is formatted in a wrong way by the calendar
Problem: When you select the 'Date/Time (default)' option, the calendar popup works, but when you select a Single Digit date, like Jun 3, etc... it fills it in as '3/Jun'... when JIRA wants '03/Jun'... so you get an error from the auto filled Calendar date...
Solution: Since this seems to be an JIRA issue, instructions about the issue is written at the configurations pages.
Fixed for: 0.2.18
27th July 2009: Release of version 1.0.0
Version 0.2.18 was stable. Only versioning number changed.
|
