Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Teams
, (opens new window)

One Appfire Support Knowledge Base
Results will update as you type.
  • License-related documentation
  • Product Categories
    • Administrative Tools
    • BI and Reporting Apps
    • Publishing
    • Agile
    • Document Management
    • ITSM
    • Developer Tools
    • Workflow & Automation
      • Jira Misc Custom Fields
      • JMWE for Jira Server and Data Center
      • JMWE for JIRA Cloud
      • Power Scripts for Confluence
      • Power Scripts Knowledge Base
      • JQL Search Extensions for Jira
      • JSU Automation Suite for Jira Workflows- Server / Data Center
        • Create a subtask with the JSU Linked Issue post function that has a different Summary for parent and sub-task
        • How to assign a newly created issue on post function "Create A Linked Issue (JSU)" to a specific user
        • How to set the sprint Id value on performing a transition using the JSU Automation Suite for Jira Workflows app
        • How to clear fix version field of the sub-task when the parent status is reopened.
        • How to use a Regular Expression validator for Custom Field - Select List (cascading) using the JSU Automation Suite app
        • How to validate the field Priority when the value is None
        • How to retrieve debug logs of the JSU Automation Suite for Jira Workflows app
        • How to get the JSU usage statistics for Jira workflows
        • How to prevent epic from closing until issues in the epic are closed
        • How post functions work with date compare precondition
        • How to make some fields mandatory in the transition, only when certain conditions hold true using JSU
        • How to clear field value of Resolution when the issue is reopened
        • How to validate input values in the text field that are separated by comma with regular expression
        • How to add regular expression check validator for IP address and host name
        • How to configure workflow transition differently for the projects that use the same workflow
        • How to capture JavaScript console logs for JSU app
        • How to copy the transition date and time to a custom field
        • How to set a field value only if assignee belongs to a particular group
        • Evaluate the usage of JSU post-functions, validators, and conditions considering only active Workflows
        • JSU transitions with the same name behave differently
      • JSU Automation Suite for Jira Workflows - Cloud
      • Autowatch for Jira
      • Power Database Fields PRO Knowledge Base
      • Scripting for Confluence (SCRP)
      • JIRA Command Line Interface (CLI) (JCLI)
      • Update on Transition for JIRA (CW)
      • UPM Command Line Interface (CLI) (UPMCLI)
      • Service Desk Command Line Interface (CLI)
      • Tempo Command Line Interface (CLI)
      • Bitbucket Command Line Interface (CLI)
      • Create on Transition for JIRA (CSOT)
      • Confluence Command Line Interface
      • Run CLI Actions in Confluence (CCLI)
      • Bamboo Command Line Interface (CLI) (BCLI)
      • Run CLI Actions in JIRA (JCLIP)
      • Clone Plus for JIRA (JCPP)
      • Run CLI Actions in Bamboo (BCLIP)
      • Atlassian Command Line Interface (CLI) (ACLI)
      • Agile Command Line Interface (CLI) (AGILECLI)
      • How to retrieve debug logs for Clone Plus for Jira, Create on Transition, and Update on Transition apps in Jira
    • Integrations KB's
  • Migration Support
  • General Articles
  • KB [KBS]
  • Mohami Support Knowledge Base [SUPPORTM]
  • Feedthree Support [SUPPORTFT]
  • KB : Articles
  • Bob Swift Support Knowledge Base [SUPPORTS]
  • Wittified Support Knowledge Base [SUPPORTW]
  • Digital Toucan Knowledge Base
    You‘re viewing this with anonymous access, so some content might be blocked.
    /
    How post functions work with date compare precondition
    Published Nov 21, 2022

    How post functions work with date compare precondition

    This article helps to understand how the post functions execute the action when the time part is included in the date compare precondition. In particular, when the dates within the date/date-time fields are of the same date then the date compare precondition will execute the action based on the time within the date/date-time fields.

    Use cases:

    • To execute post functions based on the date parts within the date fields using date compare precondition

    • To execute post functions based on the date and time within the date-time fields using date compare precondition

    • To update any field based on the date compare precondition

    Instructions

    Please note, the steps below are added on the Resolve transition, to compare the Due date and Resolved date, and to execute the action accordingly.

    1. Edit the workflow that is associated with your project.

    2. Select the Resolve transition.

    3. Select the Post Functions tab and click the Add post function.

    4. Select the Precondition: Date Compare(JSU) and click Add

    5. Select the parameters to add the condition as Resolved <= Due Date and click Add.

       

    6. This precondition checks only the date part and executes the action. If you want the precondition to check the time along with the date and perform the action, then select the Include time part checkbox option.

    7. Select the Update Any Issue Field (JSU) post function and click Add

    8. Precondition should be set to True and select the field to be updated with a preferred value and click Add


      In exceptional cases like the Sprint field, the Field Value should be the id of sprint instead of sprint name.

    9. Now, select the parameters to add the condition as Resolved > Due Date and click Add

       

    10. This precondition also checks only the date part and executes the action. If you want the precondition to check the time along with the date and perform the action then select the Include time part checkbox option.

    11. Select Update Any Issue Field (JSU) post function and click Add to update the field when the above precondition is true.

    12. The precondition should be marked as True and select the field to be updated with a preferred value and click Add

       

    13. Once all the preconditions and post functions are added, re-arrange the order of the configuration as shown below:

       

    14. Publish the workflow.

    15. In order to test this scenario:

      1. Create an issue by providing a value for the Due date field.

      2. Transition the issue to check if the fields are updated accordingly.

    For better results, make sure both the preconditions check either only the date part or Include the time part to execute the action correctly.

     

    {"serverDuration": 13, "requestCorrelationId": "e627f1d52b1148ac90ad01d588e36deb"}