Page tree

This documentation describes all functionality of the latest ictime version (5.x for JIRA 7 and 4.x for JIRA 6.x ) for administrators and users. For documentation of older versions, please refer to Documentation History.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Work Log Attributes (WLA) are en easy and powerful way to enhance your work logs with any kind of additional data you require. You can place one or more WLA on your "Log Work" mask, and can have a different set of WLA (or no WLA at all) depending on project and/or an Activity Type selected by the user.

This feature is going to be part of ictime version 4.2, to be released second half of November 2014. This documentation is work in progress.

 


What Is a Work Log Attribute

A Work Log Attribute (WLA) is a kind of "custom field" for work logs that can be placed on the ictime "Log Work" mask to collect any kind of data that is not part of the ictime default "Log Work" mask. At this moment, we support input text fields and dropdowns as field types, and for dropdowns, data (key-value-pairs) can be managed as static data or can be retrieved from a database with a dynamic query. A WLA can either be related to an Activity Type and/or a JIRA project, so it only appears for certain projects and/or after a user has selected an activity type. Data collected with a WLA is available via the export functionality of ictime Reporting.

At this moment, Work Log Attributes are neither searchable nor displayed in the details of a report, their values can only be exported (or used via an API; see API).

Some typical use cases for a WLA are:

  • If you do not (or do not only) need information about time spent to charge your work, but have other quantity-based criteria, like pages written, hard disks erased, images converted, disks burnt, ..., you can use a WLA. This way, ictime does not work as a mere time tracking solution any longer, but becomes a kind of general service recording tool.
  • If you need aditional criteria like travel expenses, km travelled or fixed cost for a certain job, you can use a WLA.
  • If Activity Types are not detailed enough for your purposes and you would need another hierachy level below, you can do that with a WLA.
  • If you need accounting information that needs to be tracked on the level of single work logs (so that you can't use a custom field on issue level), you can use a WLA.
  • ...

Create & Configure Work Log Attributes

Log Work with Work Log Attributes

Limitations & Known Issues

 

  • No labels