This app has been archived
You may still get support information and download previous versions of this app. Learn more.
Support
To check known issues (or if you want to file one), view this app's issue tracker.
To learn more about the app, you should:
- Read the documentation.
This is a supported app, so you may contact the vendor (or support contact) for help:
Description
Worklog Sheet integrates a work log sheet with Jira time tracking. With the Worklog Sheet you can more easily manage your work hours in Jira. It is organized to show a Worklog Sheet page with user specific work log data in a table like way where each row corresponds to a single work log entry. Each row contains the following information:
- Time spent: the time that has elapsed
- Date: date (and time) of the entry
- Issue: the code and name of the issue
- Description: a broad description about the entry
- Operations: delete the entry or open related issue
The different elements of the Worklog Sheet page are structured in the following way:
- At the top there is a drop down list that allows to select the user whose work log is to be viewed, edited or added.
- A table view that displays the previously added work log entries (10 entries per page) with a "Save" button and links for navigating to see more past entries below. Each row can be edited or deleted depeding on user permissions.
- A summary section that shows the work hours of current and previous week.
- At the bottom there are five rows for adding new entries with a save button below.
Time tracking is fully integrated with Jira's own time tracking and permission system. It means that worklog entry additions and changes are also reflected at:
- the issue's 'Time tracking' section
- the issue's 'Work Log'
- the 'Issue Navigator' in column 'Time Spent'
It is possible to configure group access, filtering and date formatting at the administration pages. Especially essential in Worklog Sheet is to configure a good issue filter. More information about Worklog Sheet is available at the Worklog Sheet home page. For inquiries regarding Worklog Sheet, use the e-mail address worklog.sheet@slotteconsulting.com.
Version history
1.2.7Jira Server 4.0 - 4.3.42011-03-18Minor fixes No release notes.1.2.6Jira Server 4.0 - 4.2.42010-12-22Minor fix No release notes.1.2.5Jira Server 4.0 - 4.2.42010-11-16Minor fix No release notes.1.2.4Jira Server 4.0 - 4.1.22010-10-13Minor fixes No release notes.1.2.3Jira Server 4.0 - 4.1.22010-10-05Minor fixes No release notes.1.2.2Jira Server 4.0 - 4.1.22010-09-03Fix 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.
1.2.1Jira Server 4.0 - 4.1.22010-08-24Fixes No release notes.1.2Jira Server 4.0 - 4.1.22010-08-06Usability No release notes.1.0.7Jira Server 3.12 - 4.0.22009-12-03Fix to SC-WS-56 and SC-WS-57 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.1.0.6Jira Server 4.0 - 4.0.22009-11-24Fix to issue SC-WS-56 (partly) Fixed for trial versions. Full version has still a minor issue.
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.1.0.5Jira Server 4.0 - 4.0.22009-10-21Fix to issue SC-WS-53 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.
1.0.4Jira Server 4.0 - 4.0.22009-10-13Fixes to issues SC-WS-45 and SC-WS-52 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.1.0.3.1Jira Server 3.13 - 3.13.52009-10-13Fix to issue SC-WS-52 Version 1.0.3.1 • Released 2009-10-13 • Supported By Slotte Consulting • Paid via Vendor • CommercialSC-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.1.0.2.1Jira Server 3.12 - 3.12.32009-10-13Fix to issue SC-WS-52 Version 1.0.2.1 • Released 2009-10-13 • Supported By Slotte Consulting • Paid via Vendor • CommercialSC-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.1.0.3Jira Server 3.13 - 3.13.52009-10-08Fix to issue SC-WS-51 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/tools-and-utilities/worklogsheet/workaround-for-jira-3-13/.
1.0.2Jira Server 3.12 - 3.12.32009-09-10Fix to issue SC-WS-46 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.21.0.1Jira Server 3.12 - 3.12.32009-09-04Fixes to issues SC-WS-38 to 41 SC-WS-41 Improve date validation and localization support
Problem: Date validation is simplistic and doesn't support languages other than English.
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.
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
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.
1.0Jira Server 3.12 - 3.12.32009-07-17First public stable release No release notes.