|
18th March 2011: Release of version 1.2.7 for JIRA 4.0, 4.1, 4.2 and 4.3
SC-WS-87 Change comment field default appearance
Task: Change comment field default appearance to be "one long row" instead of "two long rows".
SC-WS-86 Past Active Entries Summary rendering problem
Problem: A bug affected by the change of year in the middle of week causes the Past Active Entries Summary section to be rendered improperly.
Solution: Fix rendering so that the year change is detected properly.
22nd December 2010: Release of version 1.2.6 for JIRA 4.0, 4.1 and 4.2
SC-WS-84 Week summary sum is not calculated correctly
Problem: A bug in the week summary sum calculation may cause incorrect sums to be displayed in the Summary of Past Active Entries section.
Solution: Summary calculation logic is not in line with the paging logic in certain situations, which causes adding of duplicate entries. Fix sum calculation so that duplicate entries don't break the sum.
17th December 2010: Release of version 1.2.5 for JIRA 4.2
16th November 2010: Release of version 1.2.5 for JIRA 4.0 and JIRA 4.1
SC-WS-83 Inconsistencies in JIRA authenticated user retrieval logic cause session time-out related exceptions
Problem: Inconsistencies in the way how JIRA authenticated user is instantiated potentially cause exceptions in situations where session has been timed out. Resulting in inconsistent behaviour where authenticated user is instantiated in one call and null in other.
Solution: Change logic behaviour so that the authenticated user is always fetched from JIRA API instead of locally instantiated instance.
13th October 2010: Release of version 1.2.4 for JIRA 4.0 and 4.1
SC-WS-82 Improve session time out handling
Problem: There are still unresolved issues with the session time out handling resulting to NPEs.
Solution: Fix JSP execution order so that certain areas of code are entered if and only if session is OK.
SC-WS-81 User interface date formatting logic bypasses date format pattern translation
Problem: Date formatting fails in user interface as the date formatting logic in the user interface uses Java date formatting directly instead of using it through Worklog Sheet time and date formatting utilities.
Solution: Fix the logic to use the time and date formatting utilities.
5th October 2010: Release of version 1.2.3 for JIRA 4.0 and 4.1
SC-WS-80 Misleading paging-related text in user interface
Problem: The user interface texts related to work log entry display period are misleading, because the customizable future entries limit is not taken into account.
Solution: Fix the texts so that the future entries limit is summed out from the period day count.
SC-WS-79 Date picker doesn't work in certain situations
Problem: A bug in date picker first day of week configuration causes the date picker not to work with certain JIRA languages.
Solution Fix the bug in the configuration. It appears that the configuration parameter value is not read correctly.
3rd September 2010: Release of version 1.2.2 for JIRA 4.0 and 4.1
SC-WS-74 Bug in summary logic causes NPE for users with small amount of entries
Problem: A bug in summary logic causes NullPointerException when displaying entries of users that have little or no entries.
Solution: Fix the bug.
24th August 2010: Release of version 1.2.1 for JIRA 4.0 and 4.1
SC-WS-73 NullPointerException in summary logic
Problem: A bug in summary logic causes NullPointerException when making actions on very old entries (possibly entries from last year).
Solution: Fix the bug.
SC-WS-72 Customized past and future limits cause issues with summary calculation
Problem: Summaries are built based on time limits set in the past and future entry limit settings which can be set larger than the built-in limits for fetching work log entries. This obviously causes differences in the summary total vs. actual time spent amounts because work log entry data beyond the built-in work log entry fetching limits is incomplete.
Solution: Change summary logic to use the default limits instead of customized limits.
SC-WS-71 Issues with Past Active Entries Summary
Problem: Past Active Entries Summary is not displayed properly in all situations. Gaps in entries cause problems.
Solution: Enhance summary implementation.
6th August 2010: Release of version 1.2.0 for JIRA 4.0 and 4.1
SC-WS-65 Add clear operation for entries in Add New Entries section
Problem: There is no way to clear the rows in Add New Entries section.
Solution: Add such operation.
SC-WS-64 Add options to change comment field size and visibility
Problem: The comment field is fixed to the size of 3 rows of text. This takes up unnecessary screen space if shorter comment or no comments at all policies is used for work log entry adding.
Solution: Add to administration pages options to change comment field. In main page add option to view and hide comments. The options are:
- don't show comment row
- one short comment row in-lined
- one long comment row
- two long comment rows
- three long comment rows
SC-WS-63 Integrate Worklog Sheet with JIRA licensing API
Problem: Worklog Sheet licensing compared to JIRA licensing is not well defined.
Solution: Integrate Worklog Sheet to JIRA licensing API on source code level also.
SC-WS-62 Prevent logic from fetching more entries when saving entries
Problem: When entries are saved Worklog Sheet logic fetches more entries from the past. This might be confusing for the user.
Solution: Prevent logic from fetching entries in save situation.
SC-WS-61 Improve UI choices when Past Active Entries is in "Search for more..." mode
Problem: When Past Active Entries is in "Search for more..." mode, "Older Entries" link is inactive although it was originally planned that it should be linked the same way as the "Search for more...".
Solution: Fix the logic so that "Older Entries" is rendered as link.
SC-WS-60 Display user name in user selection list
Problem: Currently only the full name is visible in the user selection list. This makes it hard to differentiate between users with the same full name.
Solution: Append username to the selectable item: Kim Slotte => Kim Slotte (kslotte).
SC-WS-55 New operation named 'Open' that opens the issue for past entries
Add a new operation that opens an issue for past entries. Operation link name: Open Operation link tool tip: Open selected issue Note, that a user may recently have changed the issue. How to figure out the exact logical procedures in such cases.
SC-WS-54 Add option to keep user session alive
Task: Add option to keep user session alive for specified amount of hours, default being 10.
SC-WS-50 Improve issue sorting
Problem: The values in the issue drop-down list are treated as strings which leads to incorrect issue key order in the list. I.e. issue key SC-IT-10 gets a postion lesser than SC-IT-2 although it should be the otherwise around.
Solution: Change sorting algorithm to acknowledge the issue key number as a number.
SC-WS-48 Add options to limit entry date range
Problem: Adding entries entries to future and far away to the past can make them "disappear" as they are put outside the limits of the "past active entries" filter used to display the entries in Worklog Sheet.
Solution: Add options to Worklog Sheet administration page that allow to set the limits to how much in the past or future users can date the entries. The future limit should also determine the "high-end" limit of the entry filter so that items in future are visible.
SC-WS-47 Add an option to restrict the amount of users visible in the "Select user" combo list
Problem: On the Worklog Sheet panel, the "Select user" combo list contains every single user, even those with no group assigned to. This is a problem as JIRA does not allow to delete users safely, and do recommend to remove all groups assigned to a user, in order to deactivate him.
Solution: Currently Worklog Sheet outputs all users. This could be restricted by group selection/filtering. We should still take into consideration that an "admin" may want to check the past work hours for an deactivated user. So, depending on how JIRA is used this needs the be configurable through the administration panel.
SC-WS-44 More informative Past Active Entries section
Problem: Entries belonging to a certain date may be hard to see.
Solution: Add information about the total hours per date within the Past Active Entries section. The existing day and week summary data structures can be used in the implementation.
3rd December 2009: Release of version 1.0.7 for JIRA 3.12, 3.12 and 4.0
SC-WS-57 NullPointerException in save action
Problem: There's an issue in Worklog Sheet save action that causes NullPointerException when saving if session has timed out.
Solution: Improve the session timeout checks in the save function.
SC-WS-56 Worklog Sheet pages don't compile in JIRA 4 standalone installation
Problem: The Apache Tomcat application server that is coupled with the standalone version of JIRA 4 has been updated to a newer version (5.5.28) that had changed its compliance to the JSP specification to a stricter direction. Worklog Sheet JSP source code is designed to adhere the looser compliance level regarding JSP attribute quote escaping, which results in this kind of issues. The issue affects Apache Tomcat versions 5.5.27 and later.
Workaround: As a workaround to this issue, it is possible to configure the application server to use looser requirements for escaping quotes in JSP attributes by adding the following line to the end of the application server configuration file catalina.properties: org.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING = false. The configuration file is located in the folder conf under JIRA installation folder. The configuration change will be in effect after JIRA is restarted.
Solution: As permanent solution, the JSP tags that are affected by the strict quote escaping are changed so that quotes inside quotes are escaped with Java escape character in order to ensure Worklog Sheet compatibility with standalone JIRA in the future.
21st October 2009: Release of version 1.0.5
SC-WS-53 Work log entries became lost when adding new entries or updating existing in JIRA 4
Problem: A delay in JIRA 4 issue change history update mechanisms causes the work log entries of issues that have been updated due to recent work log data change made by Worklog Sheet to became invisible in the Worklog Sheet past active entries and summary sections. In other words Worklog Sheet refreshes its caches faster than JIRA updates the issue change history. The invisible entries reappear once system time passes the JIRA issue change history update time. The effect is similar to that of SC-WS-48.
Solution: Push the high-end limit of the issue filter to be near the end of current day instead of now.
Workaround: Wait for about a minute after adding or updating entries and click the Worklog Sheet link in the JIRA top navigation bar. The invisible entries should reappear.
13th October 2009: Release of version 1.0.4 for JIRA 4.0
13th October 2009: Release of version 1.0.3.1 for JIRA 3.13
13th October 2009: Release of version 1.0.2.1 for JIRA 3.12
SC-WS-52 Hour of day and minute fields are omitted when updating a work log entry in Date only format
Problem: An error in work log entry saving logic causes hour of day and minute fields being omitted in an updated work log entry's date field when Date only format is in use. The normal behaviour is to append the current hour of day and minute values to the date in order to keep the work log entry dates consistent in JIRA.
Solution: Fix the problem in work log entry logic.
SC-WS-45 Make plug-in JIRA 4 compatible (version 1.0.4 only)
Task: The plug-in will made compatible with JIRA 4.0.
8th October 2009: Release of version 1.0.3 for JIRA 3.13
SC-WS-51 Worklog Sheet has issues with filters in JIRA 3.13
Problem: The current way how Worklog Sheet attempts to determine whether a filter is globally shared doesn't guarantee that the sharing status is interpreted correctly.
Solution: Fix the problematic areas of source code to be more JIRA 3.13 compatible. Make Worklog Sheet versions after 1.0.2 only JIRA 3.13 compatible.
Workaround: See http://www.slotteconsulting.com/en/solutions-and-utilities/worklogsheet/workaround-for-jira-3-13/.
10th September 2009: Release of version 1.0.2
SC-WS-46 Date parsing fails with JIRA users that use locale other than the default
Problem: The issue appears to relate to the French locale date parsing. Worklog Sheet currently supports fully only the default English locale of JIRA.
Workaround: Change this JIRA user specific locale setting to the default "English (United States) [default]".
Solution: Improve Worklog Sheet time and date formatting utilities to handle all the locales available in JIRA properly.
Fixed for: 1.0.2
4th September 2009: Release of version 1.0.1
SC-WS-41 Improve date validation and localization support
Problem: Date validation is simplistic and doesn't support languages other than English.
Fixed for: 1.0.1
SC-WS-40 Add a read me file to the release package
Problem: The release package lacks easy-to-access documentation.
Solution: Write installation, configuration and license information to a read me file(s) and include them in the release package.
Fixed for: 1.0.1
SC-WS-39 Properties file location causes problems in certain environments
Problem: The current properties file location, default working directory, can be unwritable in certain environments. This renders Worklog Sheet unusable in these certain environments.
Solution: Explore other alternatives for properties file location. Selected solution: A configuration file location through JIRA API
Fixed for: 1.0.1
SC-WS-38 A bug in JIRA duration handling causes time spent hours to split
Problem: A bug in JIRA duration handling causes time spent hours to seemingly split. The logic does not honor the hours per day and days per week limits set in JIRA time tracking settings, thus causing incorrect values to be displayed.
Solution: A fix to the duration handling mechanism.
Fixed for: 1.0.1
27th July 2009: Release of version 1.0.0
For beta development history, i.e. development history prior to version 1.0.0 click here.
|
