Versions Compared

Old Version 91

changes.mady.by.user Smadoa GmbH

Saved on

compared with

New Version Current

changes.mady.by.user Smadoa GmbH

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

Apart from the places mentioned above (where you can open the "Log Work" dialogue), the log work option might also appear as part of other screens during workflow transitions. By default, this is the case e.g. for the "Resolve Issue" screen. See Custom Field Log Work Field for ictime for more information.

Log Work (ictime) Screen

...

The following table describes all fields, including the ones that you already know from the JIRA default "Log Work" screen:

FieldDescriptionConfigurableRemarks
UserCurrent user or user picker (if you respective permissions).
 

If you have the ictime permission "Log work for others" (see ictime Permissions), you can pick/change the user here and this way, can create work logs for other users.
Issue

Issue picker. If you are calling the "Log Work" screen from an issue (JIRA issue screen or JIRA Issue Navigator), the issue will be pre-populated.

If you call the "Log Work" screen from the JIRA navigation, your timesheet etc., you will be required to select an issue first. To select/change an issue, start to type part of the issue description or key in the "Issue" field. The JIRA issue picker will return suggestions:

Image Modified

 


Info

Please note that the issue is required for others options to work properly. The issue determines the project and this way determines teams & price lists (if applicable) and activity types (if applicable).

DateDate, shows today's date (and current time) for new work logs.
 

You can change the date into the past or future, too. The field expects date & time (as this is the default in JIRA, JIRA writes a complete timestamp for the creation date/time into all work logs).

Info

ictime provides separate fields for start and end time of a work log, so usually, the time component of this field is not used by ictimeand ictime only uses the date component. However, there might be use cases where (e.g. another plugin) is using this data from the JIRA work log

Info

If using the calendar, the date you have chosen will be inserted and as time, system will take the current time. To define a different time, you can manually edit the field. In this case, make sure that you enter date & time exactly like it has been defined in your JIRA date & time settings (see Time & Date Settings), otherwise you will get an error when saving.

Time

Log work/time as a time span/period "from-to" (start-end time).

Use the icon

Image Modified

to enter your current system time for "from" and "to".

 


Available yes/no, see General Configuration.

Force time tracking without overlapping work logs, see General Configuration.

You log e.g. from 12:34 to 14:56, and ictime calculates the

result

resulting time spent for you (displayed as read-only field behind the time fields).

Image Modified

Tip

The

result

resulting time spent of from/to has to be > 0 as JIRA does not allow saving work logs with a

result

resulting time spent of 0. If you use the clock icons to insert the current time in from/to, they will automatically create an offset of 1 minute so that your entry won't be 0.

Tip

If you (only) use this way to log work, you can force users to log work without having overlapping start/end times (see General Configuration). Depending on your configurationen, users will just get a warning or won't be able to log work if start and/or end time of one work log overlaps with the start/end time of an existing work log of the same user.

Info

Possible time format is taken from your individual JIRA time and date configuration (see Time & Date Settings); that means that we support all time & date formats you can define in JIRA. However, the defined format is the only format you can use to enter time/date (we can't support multiple different formats at a time).

Time SpentLog work/time as a result. This is the default way you log work in JIRA.Available yes/no, see General Configuration.e.g. as 12 or 12h, according to your JIRA time tracking configuration. You can find this configuration in JIRA under: Administration - System - Issue Features - Time Tracking (time estimates & default unit for time tracking)
Corrected Time Spent (Corrected Result)You can enter a time value that is different from the "time spent" value or the calculated
result
time spent of logging work with a start and end time.Available yes/no, see General Configuration.

Used to charge more or less time than the time that had been spent.

In the summary of a report, the corrected

result

time spent will be taken instead of "time spent" or the calculated

result

time spent of logging work with a start and end time (see Reports: Summary & Analysis). Rounding rules (see Project Rounding Rule) are ignored in this case, the time value is taken exactly like entered by the user.

Remaining EstimateVarious (JIRA) options to set or calculate the remaining estimate, if a work estimate has been done for the issue.

Available yes/no, see General Configuration.

If "no", ictime will always calculate the remaining estimate automatically. If there is no original estimate, nothing will be done.

See Work Estimates, Remaining Estimate.

No ChargeMark a work log as not to be charged and enter an optional comment/reason.Available yes/no, see General Configuration.

In the summary of a report, the work log would be considered in the "No Charge" section of the report (see Reports: Summary & Analysis).

An administrative user can change this setting when editing work logs, e.g. during the process of charing work logs in the Reporting section. See Reports: Work Log Details.
Activity

Choose an activity type to categorise your work.

If activity types are activated in ictime (see Activity Types), this interface will offer the activity type dropdown. This dropdown will be empty as long as you did not select an issue, as the activity types available for this issue might depend on your project configuration in ictime (see Project Activity Types).

Available yes /no, see Activity Types and Project Activity Types
Info

This is only available and mandatory if you have not globally deactivated activity types (see Activity Types) or have deactivated activity types for the current project (see Project Activity Types).

If your current project has exactly one activity type configured, the dropdown will be pre-populated with this activity type.

Work DescriptionDescription of your work.
 

Mandatory.
Tip

It is up to you whether you log work as a result ("time spent") or a time span ("from-to"). You can use both methods for the same issue and can also change this for a work log when editing or resuming a work log. If you switch from "span/period" to "resultTime Spent" and save, of course you will loose start and end time for this work log. If you switch from result "Time Spent" to "span/period", of course you will need to set a suitable start and end time.

Logging work as time span has the following advantages:

  • If it is about being exact, and about strictly avoiding that people start to make notes on time spent on paper or in files and register the (rough) result later on in JIRA, the proper way is to register time "from" and "to".
  • This also includes the option to register exactly, but to apply a rounding rule for invoicing purposes (you won't charge 6 minutes for support, but probably 15 or 30 minutes as minimum - but it is still nice that you can see that only 6 minutes had been required to solve the issue).
  • Finally logging work as time span gives you the oportunity to force time tracking without overlapping work logs (see General Configuration).

...

Note

Work Log Attributes (Work Log Attributes (WLA)) are currently not properly supported when resuming work logs.

...


Manage Work Logs (Edit & Delete)

...

If you are entering a start and end time for a work log ("from/to") and the result resulting time spent is not calculated, this can have two reasons.

...

First possible reason is that - like in the screenshot above - you have (accidentiallyaccidentally) entered an end time which is before the start time. In this case, of course there is not no result. You will get an error when trying to save.

...

For more information on date & time settings in JIRA, please refer to Time & Date Settings.