Uploaded image for project: 'Automation for Cloud'
  1. Automation for Cloud
  2. AUTO-547

Automation - Ability to parse dates from strings

XMLWordPrintable

    • 0

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Service Desk Cloud.

      Problem Definition

      Currently, the toDate have limited strings option in the following formats:

      yyyy-MM-dd
yyyy-MM-dd'T'HH:mm:ss.SZ
yyyy-MM-dd'T'HH:mm:ssZ
dd/MMM/yy hh:mm a
dd/MMM/yy

      Suggest Resolution

      Would be nice to have the option/ability to parse dates from strings via Automation(For example MM/DD/YYYY to set as the due date).

            [AUTO-547] Automation - Ability to parse dates from strings

            Charlie Gavey made changes -
            Resolution New: Low Engagement [ 10300 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]
            Anusha Rutnam made changes -
            Component/s Original: Automation [ 46695 ]
            Key Original: JSDCLOUD-10688 New: AUTO-547
            Support reference count Original: 10
            Project Original: Jira Service Management Cloud [ 18512 ] New: Automation for Cloud [ 22610 ]
            SET Analytics Bot made changes -
            UIS Original: 11 New: 0
            Charles Trilha (Inactive) made changes -
            Description Original: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Service Desk Cloud*.
              {panel}

            h3. Problem Definition
            Currently, there are limited options

            The *toDate* must have the strings in one of the following formats:
            yyyy-MM-dd
            yyyy-MM-dd'T'HH:mm:ss.SZ
            yyyy-MM-dd'T'HH:mm:ssZ
            dd/MMM/yy hh:mm a
            dd/MMM/yy



            to pick the date from the description(IE: MM/DD/YYYY) to set that as the due date:

            h3. Suggest Resolution
            The options on Edit Issue action should include all the fields configure in Screen, including Labels, Issue Security Level, Resolution, Organization, custom fields and etc.

            Would be nice to have the option/ability to parse dates from strings via Automation.             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Service Desk Cloud*.
              {panel}

            h3. Problem Definition
            Currently, the *toDate* have limited strings option in the following formats:
            {code}yyyy-MM-dd
            yyyy-MM-dd'T'HH:mm:ss.SZ
            yyyy-MM-dd'T'HH:mm:ssZ
            dd/MMM/yy hh:mm a
            dd/MMM/yy{code}

            h3. Suggest Resolution
            Would be nice to have the option/ability to parse dates from strings via Automation(For example MM/DD/YYYY to set as the due date).
            Charles Trilha (Inactive) made changes -
            Description Original: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Service Desk Cloud*.
              {panel}

            h3. Problem Definition
            Currently, there are limited options

            The {code}toDate{code} must have the strings in one of the following formats:
            yyyy-MM-dd
            yyyy-MM-dd'T'HH:mm:ss.SZ
            yyyy-MM-dd'T'HH:mm:ssZ
            dd/MMM/yy hh:mm a
            dd/MMM/yy



            to pick the date from the description(IE: MM/DD/YYYY) to set that as the due date:

            h3. Suggest Resolution
            The options on Edit Issue action should include all the fields configure in Screen, including Labels, Issue Security Level, Resolution, Organization, custom fields and etc.

            Would be nice to have the option/ability to parse dates from strings via Automation.             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Service Desk Cloud*.
              {panel}

            h3. Problem Definition
            Currently, there are limited options

            The *toDate* must have the strings in one of the following formats:
            yyyy-MM-dd
            yyyy-MM-dd'T'HH:mm:ss.SZ
            yyyy-MM-dd'T'HH:mm:ssZ
            dd/MMM/yy hh:mm a
            dd/MMM/yy



            to pick the date from the description(IE: MM/DD/YYYY) to set that as the due date:

            h3. Suggest Resolution
            The options on Edit Issue action should include all the fields configure in Screen, including Labels, Issue Security Level, Resolution, Organization, custom fields and etc.

            Would be nice to have the option/ability to parse dates from strings via Automation.
            Charles Trilha (Inactive) made changes -
            Description Original: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Service Desk Cloud*.
              {panel}

            h3. Problem Definition
            Currently, there are limited options to pick the date from the description(IE: MM/DD/YYYY) to set that as the due date:

            h3. Suggest Resolution
            The options on Edit Issue action should include all the fields configure in Screen, including Labels, Issue Security Level, Resolution, Organization, custom fields and etc.

            Would be nice to have the option to             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Service Desk Cloud*.
              {panel}

            h3. Problem Definition
            Currently, there are limited options

            The {code}toDate{code} must have the strings in one of the following formats:
            yyyy-MM-dd
            yyyy-MM-dd'T'HH:mm:ss.SZ
            yyyy-MM-dd'T'HH:mm:ssZ
            dd/MMM/yy hh:mm a
            dd/MMM/yy



            to pick the date from the description(IE: MM/DD/YYYY) to set that as the due date:

            h3. Suggest Resolution
            The options on Edit Issue action should include all the fields configure in Screen, including Labels, Issue Security Level, Resolution, Organization, custom fields and etc.

            Would be nice to have the option/ability to parse dates from strings via Automation.
            Charles Trilha (Inactive) made changes -
            Summary Original: Automation - Ability to parse dates from strings New: Automation - Ability to parse dates from strings
            Charles Trilha (Inactive) made changes -
            Description Original: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Service Desk Cloud*.
              {panel}

            h3. Problem Definition
            Currently, there are limited options for Edit Issue action. Only the following fields can be edited during the automation:
            * Assignee
            * Linked issues
            * Priority
            * Description
            * Summary
            * Due Date

            h3. Suggest Resolution
            The options on Edit Issue action should include all the fields configure in Screen, including Labels, Issue Security Level, Resolution, Organization, custom fields and etc.             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Service Desk Cloud*.
              {panel}

            h3. Problem Definition
            Currently, there are limited options to pick the date from the description(IE: MM/DD/YYYY) to set that as the due date:

            h3. Suggest Resolution
            The options on Edit Issue action should include all the fields configure in Screen, including Labels, Issue Security Level, Resolution, Organization, custom fields and etc.

            Would be nice to have the option to
            Charles Trilha (Inactive) made changes -
            Description Original: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Service Desk Cloud*. Using *JIRA Service Desk Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDSERVER-4258].
              {panel}

            h3. Problem Definition
            Currently, there are limited options for Edit Issue action. Only the following fields can be edited during the automation:
            * Assignee
            * Linked issues
            * Priority
            * Description
            * Summary
            * Due Date

            h3. Suggest Resolution
            The options on Edit Issue action should include all the fields configure in Screen, including Labels, Issue Security Level, Resolution, Organization, custom fields and etc.             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Service Desk Cloud*.
              {panel}

            h3. Problem Definition
            Currently, there are limited options for Edit Issue action. Only the following fields can be edited during the automation:
            * Assignee
            * Linked issues
            * Priority
            * Description
            * Summary
            * Due Date

            h3. Suggest Resolution
            The options on Edit Issue action should include all the fields configure in Screen, including Labels, Issue Security Level, Resolution, Organization, custom fields and etc.
            Charles Trilha (Inactive) made changes -
            Reporter Original: Ting [ cteh ] New: Charles Trilha [ ctrilha@atlassian.com ]

              Unassigned Unassigned
              ctrilha@atlassian.com Charles Trilha (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: