Versions Compared

Key

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


UI Text Box
sizemedium
typeinfo

This function returns the time a text field has had a specific value

The field's value in referenced with %{seed.text} in the logical condition. 


Code Block
languagebash
titleSyntax
linenumberstrue
timeInValue(textField, condition) #Output: Number


UI Expand
titleExamples


Parser expressionDescription


Code Block
languagebash
linenumberstrue
timeInValue(%{issue.summary}, %{seed.text} ~~ "ERROR" OR %{seed.text} ~~ "WARNING") / {HOUR}


This example returns the number of hours the field summary of the current issue contained any of the words "ERROR" or "WARNING", ignoring the case.

UI Text Box
typeinfo

{HOUR} is a time macro used to convert the output to hours.



Code Block
languagebash
linenumberstrue
timeInValue(%{issue.components}, count(toStringList(%{seed.text}, ",")) > 1
Page properties
hiddentrue
StatusTech review

Status
titletodo

Style guide

Status
titletodo

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

Page properties
hiddentrue
Short description

Returns the time an issue field has had a specific value.

Output

Status
subtletrue
titlenumber

Available since StatussubtletruecolourRedtitleneeds lookup
UI Text Box
sizemedium
typeinfo

This function returns the time a text field has had a specific value

The value check (a boolean condition) is being initialized with ^%. 

Code Block
languagebash
titleSyntax
linenumberstrue
timeInValue(textField, condition) #Output: Number
UI Expand
titleExamples
Parser expressionDescription
Code Block
languagebash
linenumberstrue
timeInValue(%{issue.summary}, ^% ~~ "ERROR" OR ^% ~~ "WARNING") / {HOUR}


This example This example returns the number of hours the field summarycomponents of the current issue contained any of the words "ERROR" or "WARNING", ignoring the case. more than one selected component.

UI Text Box
typeinfo

{HOUR} is a time macro used to convert the output to hours.

To achieve this, the following functions are used:


Code Block
language
Code Block
languagebash
linenumberstrue
timeInValue(%{issue.componentspriority}, count(toStringList(^% %{seed.text} in ["Critical", ",High")]) > 1) / {HOUR}


This example returns the This example returns the number of hours hours the field componentsfield priority of the current issue contained more than one selected component.had a value of Critical or High.

This example uses these functions:

  • count()
  • toString()code
    UI Text Box
    typeinfo
    Info

    {HOUR} is a time macro used to convert the output to hours.




    language

    This example returns the number of hours the field priority of the current issue had a value of Critical or High.

    UI Expand
    title
    bash
    linenumberstrue
    timeInValue(%{issue.priority}, ^% in ["Critical", "High"]) / {HOUR}
    Info

    {HOUR} is a time macro used to convert the output to hours.

    UI Expand
    titleAdditional information
    Additional information

    Parameters used in this function

    ParameterInput (data type)Description

    Parameters used in this function

    ParameterInput (data type)Description
    textField

    Status
    subtletrue
    titletext

    The input has to be a valid text field represented by a field code.
    condition

    Status
    subtletrue
    titletext

    The calculation will only be performed if the boolean logical condition is being met.



    UI Expand
    titleOutput

    This function returns a

    Status
    subtletrue
    titlenumber




    UI Text Box
    sizemedium
    typeinfo

    Variant for number or date-time fields.


    Code Block
    languagebash
    titleSyntax
    linenumberstrue
    timeInValue(numberField, condition) #Output: Number


    expandtitle information
    UI Expand
    titleExamples


    Parser expressionDescription


    Code Block
    languagebash
    linenumberstrue
    timeInValue({issue.dueDate}, ^{seed.number} != null) / {HOUR}


    This example returns the number of hours the of the  the field Due date of the current issue that had a value.


    Code Block
    languagebash
    linenumberstrue
    timeInValue({10001issue.cf10001}, ^{seed.number} >= 5 AND ^{seed.number} <= 10)


    This example returns the number of milliseconds of a hypothetical numeric field called Passengers (field code {10001}) of the current issue that remained between 5 and 10.


    Code Block
    languagebash
    linenumberstrue
    timeInValue({10001issue.cf10001}, modulus(^{seed.number}, 2) = 0)


    This example returns the number of milliseconds of a hypothetical numeric field called Passengers called Passengers (field code {10001}) of the current issue that has had an even value (2, 4, 6,...).

    To achieve this, the following functions are used:

    ui-text-
    box
    type
    tip

    Additional

    useful functions can be found here: Numbers




    UI Expand
    titleAdditional information

    Parameters used in this function

    ParameterInput (data type)Description
    xxxnumberField

    Status
    subtletrue
    titledata type

    Parameter description.

    text

    The input has to be a valid number field represented by a field code.
    conditionxxx

    Status
    subtletrue
    titledata typetext

    The calculation will only be performed if the logical condition is being metParameter description.



    UI Expand
    titleOutput

    This function returns a

    Status
    subtletrue
    titlenumber




    UI Text Box
    sizemedium
    typeinfo

    The function returns the sum of milliseconds of a string field with code %{nnnnn} of the current issue that has a value satisfying a boolean expression predicate in distinct issues.

    Where the string value of the field with code %{nnnnn} is represented by ^%Variant for text fields where you can additional specify an issue list instead taking the field from the current issue. The function returns the sum of milliseconds of each issue in the given list.


    Code Block
    languagebash
    titleSyntax
    linenumberstrue
    timeInValue(stringtextField, field field, issue list issues, boolean expression predicateissueList, condition) #Output: Number


    UI Expand
    titleExamples


    Parser expressionDescription


    Code Block
    languagebash
    titleSyntax
    linenumberstrue
    timeInValue(%{00000issue.summary}, subtasks(), ^%%{seed.text} ~~ "ERROR" OR ^%%{seed.text} ~~ "WARNING") / {MINUTE}


    This example returns number representing the sum of milliseconds  of the field summary (field code %{00000}) of all the number of minutes the sub-tasks' summaries contained any of the current issue that contained any of the words "ERROR" or "WARNING" , ignoring the case.

    To achieve this, the following functions are used:


    Code Block
    languagebash
    titleSyntax
    linenumberstrue
    timeInValue(%{00094issue.components}, epic(), count(toStringList(^%%{seed.text}, ",")) > 1)


    This example returns the number of milliseconds of the field components (field code %{00094}) in a linked Epic issue that contained epic's field components contained more than one selected component.

    To achieve this, the following functions are used:


    Code Block
    Code Block
    languagebash
    titleSyntax
    linenumberstrue
    timeInValue(%{00017issue.priority}, filterByIssueType(linkedIssues(), "Bug, New Feature"), ^%%{seed.text} in ["Critical", "High"]) / {HOUR}


    This example returns a number representing the sum of milliseconds of all the number of hours the linked Bugs and New features of the current issue that had a priority (field code %{00017}) value of Critical of Critical or High.

    To achieve this, the following functions are used:



    UI Expand
    title
    UI Expand
    titleAdditional information

    Parameters used in this function

    ParameterInput (data type)Description
    xxxtextField

    Status
    subtletrue
    titledata typetext

    Any given text fieldParameter description.
    xxxissueList

    Status
    subtletrue
    titledata typeIssue list

    Any given issue list. Usually this value is retrieved from a function (e.g. linkedIssues() or subtasks()).

    condition

    Parameter description.

    xxx

    Status
    subtletrue
    titledata typetext

    The calculation will only be performed if the logical condition is being met

    Parameter description

    .



    UI Expand
    titleOutput

    This function returns a

    Status
    subtletrue
    titlenumber




    UI Text Box
    sizemedium
    typeinfo

    The function returns the sum of milliseconds of a number or date-time field with code {nnnnn}of the current issue that has a value satisfying a boolean expression predicate in distinct issues.

    Where the string value of the field with code {nnnnn} is represented by ^.

    Variant of number or date-time fields.


    Code Block
    Code Block
    languagebash
    titleSyntax
    linenumberstrue
    timeInValue(numberField, issueList, condition) #Output: Number


    UI Expand
    titleExamples


    Parser expressionDescription


    Code Block
    languagebash
    linenumberstrue
    timeInValue({00012issue.dueDate}, subtasks(), ^{seed.number} != null


    This example returns the number of milliseconds of the field  the sub-tasks' Due Date ( field code {00012}) of all sub-tasks of the current issue that had a value.

    To achieve this, the following functions are used:


    Code Block
    languagebash
    linenumberstrue
    timeInValue({10001issue.cf10001}, epic(), ^{seed.number} >= 5 AND ^{seed.number} <= 10)


    This example returns the number of milliseconds of a hypothetical  the epic's numeric field called Passengers (field code {10001}) of an Epic issue that had a value between 5 and 10.

    To achieve this, the following functions are used:


    Code Block
    languagebash
    linenumberstrue
    timeInValue({10001issue.cf10001}, filterByIssueType(linkedIssues(), "Bug, New Feature"), modulus(^{seed.number}, 2) = 0)


    This example returns the number  of milliseconds of a hypothetical numeric field called Passengers (field code {10001}) that number of milliseconds the linked Bugs' and New features' numeric field Passengers had an even value in any linked Bug or New Feature...

    To achieve this, the following functions are used:

    UI Text Box
    typetip

    Additional useful functions can be found here: Numbers




    Parameter description
    UI Expand
    titleAdditional information

    Parameters used in this function

    ParameterInput (data type)Description
    numberField

    Status
    subtletrue
    title

    data type

    text

    Any given number field.
    xxx
    issueList

    Status
    subtletrue
    title

    data type

    Parameter description.

    xxx

    issue list

    Any given issue list. Usually this value is retrieved from a function (e.g. linkedIssues() or subtasks()).

    condition

    Status
    subtletrue
    title

    data typeParameter description

    text

    The calculation will only be performed if the boolean condition is being met.



    UI Expand
    titleOutput

    This function returns a

    Status
    subtletrue
    titlenumber




    UI Text Box
    sizemedium
    typeinfo

    The function returns the number of milliseconds of a string field with code %{nnnnn}of the current issue that had a value satisfying a boolean expression predicate.

    Where the string value of the field with code %{nnnnn} is represented by ^%.

    The time being calculated by this function is only counted during a defined schedule with a name "schedule_name" in a certain time_zone

    Variant where you additionally can define a custom calendar and time zone.

    The field's value in referenced with ^% in the boolean condition. 


    Code Block
    language
    Code Block
    languagebash
    titleSyntax
    linenumberstrue
    timeInValue(string field fieldtextField, boolean expression predicatecondition, string schedule_namecalendar, timeZone time_zone) #Output: Number


    UI Expand
    titleExamples


    Parser expressionDescription


    Code Block
    languagebash
    linenumberstrue
    timeInValue(%{00094issue.components}, count(toStringList(^%%{seed.text}, ",")) > 1, "my_schedulecalendar", LOCAL) 


    This example returns the number of milliseconds of the  the field components (field code %{00094}) of the current issue that contained more than one selected component, within a schedule named calendar named "my_schedulecalendar" in  in the server's default time _ zone.

    To achieve this, the following functions are used:


    Code Block
    languagebash
    linenumberstrue
    timeInValue(%{00017issue.priority}, ^%%{seed.text} in ["Critical", "High"], "my_schedulecalendar", LOCAL)


    The function returns the number of milliseconds of the  the current issue that had a priority value of Critical or High (field code %{00017})High, within a schedule named calendar named "my_schedulecalendar" in  in the server's default time _ zone.


    Code Block
    languagebash
    linenumberstrue
    timeInValue(%{00000issue.summary}, ^%%{seed.text} ~~ "ERROR" OR ^%%{seed.text} ~~ "WARNING", "my_schedulecalendar", LOCAL)
    


    The function returns the number of milliseconds the field summary (field code %{00000}) of the current issue that contained any of the words "ERROR" or "WARNING", ignoring the case, within a schedule calendar named "my_schedulecalendar" in the server's default time _ zone.



    UI Expand
    titleAdditional information

    Parameters used in this function

    ParameterInput (data type)Description
    xxxtextField

    Status
    subtletrue
    titledata typetext

    Any given text fieldParameter description.
    xxxcondition

    Status
    subtletrue
    titledata typetext

    The calculation will only be performed if the boolean condition is being met.

    calendarParameter description.xxx

    Status
    subtletrue
    titledata typetext

    A valid calendar nameParameter description.
    timeZone

    Status
    subtletrue
    titletimezone

    The time zone used for the calculation. 

    Expand
    titleLearn more about timezones
    Excerpt Include
    Dates, times and time zonesDates, times and time zones
    nopaneltrue


    UI Text Box
    typetip

    Work days might depend on the time zone - it might be Sunday on the west coast of the US while at the same time it's already Monday in Australia. 



    UI Expand
    titleOutput

    This function returns a

    Status
    subtletrue
    titlenumber




    UI Text Box
    sizemedium
    typeinfo

    The function returns the number of milliseconds of a number or date-time field with code {nnnnn} of the current issue that had a value satisfying a boolean expression predicate.

    Where the numeric value of the field with code {nnnnn} is represented by ^.

    The time being calculated by this function is only counted during a defined schedule with name "schedule_name" in a certain time_zone.

    Variant of number or date-time fields.


    Code Block
    languagebash
    titleSyntax
    linenumberstrue
    timeInValue(number field fieldnumberField, boolean expression predicatecondition, string schedule_namecalendar, timeZone time_zone) #Output: Number


    UI Expand
    titleExamples


    Parser expressionDescription


    Code Block
    languagebash
    linenumberstrue
    timeInValue({00012issue.dueDate}, ^{seed.number} != null, "my_schedulecalendar", LOCAL)


    This example returns the number of milliseconds the field Due Date (field code {00012}) of the current issue that had a value,  ignoring the case, within a schedule calendar named "my_schedulecalendar" in the server's default time _ zone.


    Code Block
    languagebash
    linenumberstrue
    timeInValue({10001issue.cf10001}, ^{seed.number} >= 5 AND ^{seed.number} <= 10, "my_schedulecalendar", LOCAL)


    This example returns the number of milliseconds of a hypothetical the numeric field called Passengers (field code {10001}) of the current issue that had a value between 5 and 10, within a schedule calendar named "my_schedulecalendar" in the server's default time _ zone.


    Code Block
    languagebash
    linenumberstrue
    timeInValue({10001issue.cf10001}, modulus(^{seed.number}, 2) = 0, "my_schedulecalendar", LOCAL)


    This example returns the number of milliseconds a hypothetical the numeric field called Passengers (field code{10001}) in current issue that had an even value, within a schedule calendar named "my_schedulecalendar" in the server's default time _ zone.

    To achieve this, the following functions are used:

    ui-text-box
    typetip

    Additional useful functions can be found here: Numbers




    expand
    UI Expand
    titleAdditional information

    Parameters used in this function

    ParameterInput (data type)Description
    xxxnumberField

    Status
    subtletrue
    titledata typetext

    Any given number fieldParameter description.
    xxxcondition

    Status
    subtletrue
    titledata typetext

    The calculation will only be performed if the boolean condition is being met.
    calendarParameter description.xxx

    Status
    subtletrue
    titledata typetext

    A valid calendar nameParameter description.
    timeZone

    Status
    subtletrue
    titletimezone

    The time zone used for the calculation. 

    Expand
    titleLearn more about timezones
    Excerpt Include
    Dates, times and time zonesDates, times and time zones
    nopaneltrue


    UI Text Box
    type
    UI Text Box
    typetip

    Work days might depend on the time zone - it might be Sunday on the west coast of the US while at the same time it's already Monday in Australia. 



    UI Expand
    titleOutput

    This function returns a

    Status
    subtletrue
    titlenumber




    UI Text Box
    sizemedium
    typeinfo

    The function returns the sum of milliseconds of a string field with code %{nnnnn} that had a value satisfying a boolean expression predicate in distinct issues.

    Where the value of the field with code %{nnnnn} is represented by ^%

    The time being calculated by this function is only counted during a defined schedule with name "schedule_name" in a certain time_zone.

    Variant where you can additionally specify an issue list.


    Code Block
    languagebash
    titleSyntax
    linenumberstrue
    timeInValue(textField, issueList, condition, calendar, timeZone
    Code Block
    languagebash
    titleSyntax
    linenumberstrue
    timeInValue(string field field, issue list issues, boolean expression predicate, string schedule_name, timeZone time_zone) #Output: Number


    UI Expand
    titleExamples


    Parser expressionDescription


    Code Block
    languagebash
    linenumberstrue
    timeInValue(%{00000issue.summary}, subtasks(), ^%%{seed.text} ~~ "ERROR" OR ^%%{seed.text} ~~ "WARNING", "my_schedulecalendar", LOCAL)


    This example returns the sum of milliseconds of the fields summary (field code %{00000}) of all sub-tasks of the current issue that contained any  the sub-tasks' fields summary contained any of the words "ERROR" or "WARNING", ignoring the case, within a schedule named calendar named "my_schedulecalendar" in the server's default time _ zone.

    To achieve this, the following functions are used:


    Code Block
    languagebash
    linenumberstrue
    timeInValue(%{00094issue.components}, epic(), count(toStringList(^%%{seed.text}, ",")) > 1, "my_schedulecalendar", LOCAL)


    This example returns the number of milliseconds of the field components (field code %{00094}) in the linked Epic issue that contained more than one selected epic's field components contained more than one selected component, within a schedule named calendar named "my_schedulecalendar" in the server's default time _ zone. .

    To achieve this, the following functions are used:


    Code Block
    languagebash
    linenumberstrue
    timeInValue(%{00017issue.priority}, filterByIssueType(linkedIssues(), "Bug, New Feature"), ^%%{seed.text} in ["Critical", "High"], "my_schedulecalendar", LOCAL)


    This example returns the sum of milliseconds of all linked Bugs and New Features of the current issue that had a priority (field code %{00017}) value of Critical or High, within a schedule named "my_schedule the linked Bugs' and New Features' field priority had a value of Critical or High, within a calendar named "my_calendar" in the server's default time _ zone

    To achieve this, the following functions are used:



    UI Expand
    titleAdditional information

    Parameters used in this function

    ParameterInput (data type)Description
    xxxtextField

    Status
    subtletrue
    titledata typetext

    Any given text fieldParameter description.
    xxxissueList

    Status
    subtletrue
    titledata typeissue list

    Any given issue list. Usually this value is retrieved from a function (e.g. linkedIssues() or subtasks()).
    conditionParameter description.xxx

    Status
    subtletrue
    titledata typetext

    The calculation will only be performed if the boolean condition is being met.
    calendarParameter description.xxx

    Status
    subtletrue
    titledata typetext

    A valid calendar nameParameter description.
    timeZone

    Status
    subtletrue
    titletimezone

    The time zone used for the calculation. 

    Expand
    titleLearn more about timezones
    Excerpt Include
    Dates, times and time zonesDates, times and time zones
    nopaneltrue


    UI Text Box
    typetip
    UI Text Box
    typetip

    Work days might depend on the time zone - it might be Sunday on the west coast of the US while at the same time it's already Monday in Australia. 



    UI Expand
    titleOutput

    This function returns a

    Status
    subtletrue
    titlenumber




    UI Text Box
    sizemedium
    typeinfo

    the function returns the sum of milliseconds of a Variant with number or date-time field with code {nnnnn} has had a value satisfying a boolean expression predicate in distinct issues, where the numeric value of the field with code {nnnnn} is represented by ^

    The time being calculated by this function is only counted during a defined schedule with name "schedule_name" in a certain time_zone.

    fields.


    Code Block
    languagebash
    title
    Code Block
    languagebash
    titleSyntax
    linenumberstrue
    timeInValue(number field field, issue list issues, boolean expression predicate, string schedule_name, timeZone time_zonenumberField, issueList, condition, calendar, timeZone) #Output: Number


    UI Expand
    titleExamples


    Parser expressionDescription


    Code Block
    languagebash
    linenumberstrue
    timeInValue({00012issue.dueDate}, subtasks(), ^{seed.number} != null, "my_schedulecalendar", LOCAL)


    This example returns the number the sum of milliseconds the field Due date (field code {00012}) of all sub-tasks of the current issue that ' fields Due date had a value, within a schedule named calendar named "my_schedulecalendar" in the server's default time _ zone

    To achieve this, the following functions are used:


    Code Block
    languagebash
    linenumberstrue
    timeInValue({10001issue.cf10001}, epic(), ^{seed.number} >= 5 AND ^{seed.number} <= 10, "my_schedulecalendar", LOCAL)


    This example returns the number of milliseconds a hypothetical numeric field called Passengers (field code {10001}) in the linked Epic issue has the epic's field Passengers had a value between 5 and 10, within a schedule named calendar named "my_schedule" in the server's default time_zone

    Code Block
    languagebash
    linenumberstrue
    timeInValue({10001}, filterByIssueType(linkedIssues(), "Bug, New Feature"), modulus(^, 2) = 0, "my_schedule", LOCAL)

    This example returns the number of milliseconds a hypothetical numeric field called Passengers (field code {10001}) that had an even value in any linked Bug or New Feature, within a schedule named "my_schedule" in the server's default time_zone

    calendar" in the server's default time zone

    To achieve this, the following functions are used:


    Code Block
    languagebash
    linenumberstrue
    timeInValue({issue.cf10001}, filterByIssueType(linkedIssues(), "Bug, New Feature"), modulus({seed.number}, 2) = 0, "my_calendar", LOCAL)


    This example returns the sum of milliseconds the linked Epics' and New Features' numeric field Passengers had an even value, within a calendar named "my_calendar" in the server's default time zone

    To achieve this, the following functions are used:

    UI Text Box
    typetip

    Additional useful functions can be found here: Numbers




    UI Expand
    titleAdditional information

    Parameters used in this function

    ParameterInput (data type)Description
    numberField

    Status
    subtletrue
    titletext

    Any given number field.
    issueList

    Status
    subtletrue
    titleissue list

    Any given issue list. Usually this value is retrieved from a function (e.g. linkedIssues() or subtasks()).
    condition

    Status
    subtletrue
    titletext

    The calculation will only be performed if the boolean condition is being met.
    calendar

    Status
    subtletrue
    titletext

    A valid calendar name.
    timeZone

    Status
    subtletrue
    titletimezone

    The time zone used for the calculation. 


    UI Text Box
    typetip

    Work days might depend on the time zone - it might be Sunday on the west coast of the US while at the same time it's already Monday in Australia. 



    UI Expand
    titleOutput

    This function returns a

    Status
    subtletrue
    titlenumber



    Image AddedUse cases and examples

    Page properties report
    firstcolumnUse case
    headingsJWT feature, Workflow function, Field type, Automated action, Parser functions
    cqllabel = "parser_func_timeinvalue" and space = currentSpace()


    Page properties
    hiddentrue
    id1


    Parser function cloud
    Map(error)
    NotesNot possible because that kind of information is not available.




    Page properties
    hiddentrue



    Status
    Tech review

    Status
    colourGreen
    titledone

    Style guide

    Status
    colourGreen
    titledone

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



    Parameters used in this function

    The time zone used for the calculation. 

    Page properties
    hiddentrue


    Short description

    Returns the time an issue field has had a specific value.

    Output

    Status
    subtletrue
    titlenumber

    Available since

    Status
    subtletrue
    colourRed
    titleneeds lookup

    Label

    Status
    colourRed
    titlestaff pick

    UI Expand
    titleAdditional information
    ParameterInput (data type)Description
    xxx
    Status
    subtletrue
    titledata type
    Parameter description.xxx
    Status
    subtletrue
    titledata type
    Parameter description.xxx
    Status
    subtletrue
    titledata type
    Parameter description.xxx
    Status
    subtletrue
    titledata type
    Parameter description.timeZone
    Status
    subtletrue
    titletimezone
    Expand
    titleLearn more about timezones
    Excerpt Include
    Dates, times and time zonesDates, times and time zones
    nopaneltrue
    UI Text Box
    typetip

    Work days might depend on the time zone - it might be Sunday on the west coast of the US while at the same time it's already Monday in Australia. 

    UI Expand
    titleOutput
    This function returns a Statussubtletruetitlenumber