Get started

Use case library

JWT expression editor

JWT expression parser functions

JWT workflow functions

JWT remote actions

JWT automation rules

JWT calculated fields

JWT calendars

JWT properties

JWT JQL functions

Cloud migration hub

Additional product info

Versions Compared

Old Version 5

changes.mady.by.user Iheb Kharab

Saved on

compared with

New Version Current

changes.mady.by.user Iheb Kharab

Saved on

Key

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


Panel

On this page

Table of Contents
exclude(On this page|Filter by field value|Remaining estimate).*
stylecircle
typeflat
separatorpipe

UI Text Box
sizemedium
typeinfo

The Log work post function allows creating automatic work logs when triggering transitions. Math expressions as complex as needed can be used to calculate the time to be logged, and custom parsed texts can be used for the comment.

This post function automatically creates worklogs for one or multiple issues.


Image AddedConfiguration

UI Expand
titleTarget issue
UI Text Box
typenote

In this documentation and the post function configuration you will notice the symbol ( * ) next to some parameters, it means that this field is mandatory and shall not be left empty. Fields without the symbol are optional.

Basic configuration*

Below you will find a detailed description of each parameter of the basic configuration of the function.

Target issue*

Info
iconfalse

Select the issue(s) to log work on. The following options are available:

OptionDescription
Current issueWork will be logged on the current issue.
Parent issueWork will be logged on the current issue's parent.
Sub-tasksWork will be logged on the current issue's sub-tasks. If you choose this option you can further filter your selection (e.g. by issue type or status). Only useful for standard issues. 
Sibling sub-tasksWork will be logged on the current issue's sibling sub-tasks. Only useful if the current issue is a sub-task. 
Linked issuesWork will be logged on linked issues. If you choose this option you can further filter your selection (e.g. by issue type or status). 
Linked epicWork will be logged on the related epic.
Issues under epicWork will be logged on all issues related to the same epic. If you choose this option you can further filter your selection (e.g. by issue type or status). 
Sibling issues under epicWork will be logged on all sibling issues related to the same epic. If you choose this option you can further filter your selection (e.g. by issue type or status). 
Set target issue manually (parser expression)

Time*

false

Define the issues that work will be logged on by defining an expression. The JQL mode and Issue list mode are available.

UI Text Box
typenote
Info
icon

The expression must return

the logged time in minutes.

either a valid JQL expression or an issue list with issue keys.




UI Expand
titleTime

You can either enter the number of minutes or calculate the value in the Numeric mode. The result should be the number of minutes to be logged.


UI Expand
titleStarting date-time
Info
iconfalse

The expression must return Specify the starting date-time of for the work time log entry. In case no expression is entered. Since a timestamp is always represented by a number you must specify the expression in the Numeric mode. 

If leaving this field blank, the currentdate-time is used.


UI Expand
titleWork description
Info
iconfalse

Enter This parameter adds a standard description to your work log. You can either enter plain text and optionally use field codes to insert field values .

UI Text Box
typetip

You can try your expression by clicking on the play button on the top right of the JQL expression boxusing the mixed parsing mode.


UI Expand
expandedtrue
titleAdditional options

Remaining estimate

You can decide how to proceed with the remaining estimate of the issues. You have the two following options:

OptionDescription
Auto adjustment
-

The issues' remaining estimate will be reduced by the amount of work logged.

retain
Retain remaining estimate
-

The issues' remaining estimate will not be updated.



Enter a condition (Logical / boolean condition) using the JWT expression parser functions syntax.

You can even logically link and gather conditions in expressions as you like in order to map more complex conditions.

UI Expand
iconfalse
titleConditional execution
UI Text Box
typenote

The post function will only be executed if the condition is met (returns true).

Include Page
DECADIS:_snip_condExecution_Server
DECADIS:_snip_condExecution_Server


Choose which user* will be able to execute this post function. By default, it is set to the Current user.
UI Expand
iconfalse
titleRun as

Include Page
DECADIS:_snip_runAs_Server_postFunction
DECADIS:_snip_runAs_Server_postFunction



Image AddedUse cases and examples

Page properties report
firstcolumnUse case
headingsJWT feature, Workflow function, Parser functions, Label
cqllabel = "use-case-workflow" and parent = currentContent()

Excerpt Include
DECADIS:Contact support
DECADIS:Contact support
nopaneltrue


Page properties
hiddentrue


Tech review

Status
colourGreen
titledone

Style guide

Status
colourGreen
titledone

Status
titletodo
Status
colourYellow
titleReady for review
Status
colourGreen
titledone
Status
colourRed
titleflagged


Page properties
hiddentrue


Short descriptionLog work on one or multiple issues.
Label