...
Once you have created a WLA and it appears in the list, the following operations are possible:
| Operation | Description | Remarks |
|---|---|---|
 | Assignments | Depending on the type of WLA ("ACTIVITY TYPE" or "PROJECT"), here you can create/edit the assignments (relations) of a WLA to either activity types or projects. For details, see below. |
 | Edit | Edit the WLA. For details, see below. |
 | Delete | You can delete a WLA if is is not used (has no assignments and no work logs with this WLA exist). If it is no longer possible to delete a WLA, you can still deactivate it (see below). |
Create & Edit WLA
To create a new WLA, click the respective button on top of the screen:
...
For the Field Type DROPDOWN, there are also additional and different options, depending on your choice for the data source:
| Field | Description | Remarks |
|---|---|---|
| Name (Internal) | An internal name for your purposes. |
| Label (Screen) | Name like it will appear on the "Log Work" screen. |
| Mapping ID | If you are connecting to an extrenal system to retrieve data for your WLA, you can use the external ID as mapping ID for the WLA (otherwise, the external system would need to use the ID of the WLA). |
| Field Type | Input text or dropdown. | Dropdowns have two different ways to get populated with data (see "Data Source").
| ||||
| RegEx (Field Check) | A regular expression that enforces a defined format for the user's input. | Not applicable to dropdowns. | ||||
| JNDI | If you want to manage dropdown values dynamically via a database query, you need to define your JNDI here. See http://en.wikipedia.org/wiki/Java_Naming_and_Directory_Interface and below. Here, you just enter the name of your JNDI. | Only applicable to dropdowns where dropdown values should be dynamically retrieved from a database. | ||||
| SQL Query | The query used to dynamically retrieve dropdown data from an (external) database. | Only applicable to dropdowns. | ||||
| WLA Type | There are two different types of WLA that distinguish as follows:
| For details, see below.
| ||||
| Assignments | The activity types or projects (depending on WLA Type) this WLA is assigned to. Assignments define if (under which conditions) the WLA appears on the "Log Work" mask. For more information, see below. |
| Order | If you define multiple WLA and multiple WLA might appear on the "Log Work" dialogue, you can define a sorting order for all WLA here. Sorting applies across all WLA, regardless of their type.
| Numerical, like 10, 20, 30 | ||
| Active | If the WLA is currently active. | It is not possible to delete a WLA that is in use. You can only deactivate it. If you deactivate a WLA, all data is kept, but the WLA is no longer available for new work logs (when editing a work log, you can either not save or need to clear/delete the data of this WLA). | ||
| Mandatory | If the WLA is a mandatoy field in the "Log Work" mask. |
| Global (All) | If the WLA is globally assigned to all activity types or all projects (depending on WLA Type). See below. | If you choose this option, it is not required to define individual assignments.
| ||
| Depend on Activity Type | By default, a WLA Type "PROJECT" is directly displayed in the "Log Work" mask for all projects this WLA has been assigned to. "Depend on Activity Type" changes this behaviour and the WLA will only be displayed (in the "Log Work" mask for all projects this WLA has been assigned to) after the user has selected (any) activity type.
| Only applicable for WLA Type "PROJECT". |
When you edit a WLA, the following fields can't be changed any longer:
...
| Note |
|---|
You can also work with a stored procedure. Keep in mind that in this case, ictime does not have any control over the kind queries that are executed, so it is up to you to ensure that you are not changing or deleting data. |
...
A few parameters available within a JIRA issue or from ictime can be used to parametrize your query:
| Field | Description | Remarks |
|---|---|---|
projectKey | Current JIRA project key (retrieved via the JIRA issue). |
| projectId | Current JIRA project ID (retrieved via the JIRA issue). |
| userKey | Current JIRA user. |
| activityTypeId | Activity type currently selected. | Available after the user has selected an activity type. |
| activityTypeExtMapId | External Mapping Id of the activity type currently selected. | Available after the user has selected an activity type. |
| issueId | Issue ID. | Available starting with ictime-5.2.15 |
| issueKey | Issue key. | Available starting with ictime-5.2.15 |
Example 1: Filter by Current Project
...
<Resource name="jdbc/TestName" auth="Container" type="javax.sql.DataSource" username="dbUsername" password="dbPassword" driverClassName="com.mysql.jdbc.Driver" url="jdbc:mysql://hostname:3306/databaseName" />
| Field | Description | Remarks | ||
|---|---|---|---|---|
| Resource name | individual name ("jdbc/" part is mandatory and must go first) |
| ||
| username | user name for this database |
| password | password for this database |
| diverClassName | class name for the driver of your database (example shows MySQL) |
| url | URL to your database |
There might be more parameters available (refer to the specification of your servlet container), you might set them according to your needs.
...
| Tip |
|---|
If such a non-valid field is empty (no content or no selection of a value), there will be no error, but on saving, the field will simply be deleted. |
...
Content Changes (Dropdown Only)
...
If you move issues in JIRA between different projects that have a different WLA configuration, and these issues have work logs with WLA data, these work logs are no longer consistent, because they contain WLA data from the original project that does not match with the WLA configuration of the target project. As a result, reports might generate incorrect data for accounting purposes. The same problems also affects Activity Types, Rounding Rules and Teams/Price Lists. For all known cases, this problem is addressed with a specific tool to fix such work logs, see Fix Work Logs (Warnings).