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

.timeZone smart value should return the user's timezone rather than the default user timezone for the Site.

XMLWordPrintable

    • 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.

      Problem Definition

      When using the .timeZone smart value in automation, such as assignee.timeZone, the Default user timezone for the Site is returned.

      Suggested Solution

      Have the user's personal timezone be returned instead.

      Workaround

      There is no reasonable workaround at this time, short of using some external source for the user's timezone, like Insight for JSM, or logging timezones in a Jira Issue. In other words, cumbersome workarounds.

            [AUTO-280] .timeZone smart value should return the user's timezone rather than the default user timezone for the Site.

            Grant Adkins added a comment -

            Closed due to low engagement!? When so many other things sit in gathering interest for literally more than a decade.  It's a bug, fix it! 

            Grant Adkins added a comment - Closed due to low engagement!? When so many other things sit in gathering interest for literally more than a decade.  It's a bug, fix it! 
            Charlie Gavey made changes -
            Resolution New: Low Engagement [ 10300 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]
            Samir made changes -
            Component/s Original: Automation - A4J [ 65590 ]
            Component/s New: Condition - Issue Fields [ 70305 ]
            Key Original: JSDCLOUD-11749 New: AUTO-280
            Project Original: Jira Service Management Cloud [ 18512 ] New: Automation for Cloud [ 22610 ]
            Payden Pringle made changes -
            Description Original: h3. Problem Definition

            When using the .timeZone smart value in automation, such as {{assignee.timeZone}}, the Default user timezone for the Site is returned.

            h3. Suggested Solution

            Have the user's personal timezone be returned instead.

            h3. Workaround

            There is no available workaround at this time, unless using some external source for the user's timezone, like Insight for JSM, or logging timezones in a Jira Issue. In other words, cumbersome workarounds.             		New: h3. Problem Definition

            When using the {{.timeZone}} smart value in automation, such as {{assignee.timeZone}}, the Default user timezone for the Site is returned.

            h3. Suggested Solution

            Have the user's personal timezone be returned instead.

            h3. Workaround

            There is no reasonable workaround at this time, short of using some external source for the user's timezone, like Insight for JSM, or logging timezones in a Jira Issue. In other words, cumbersome workarounds.
            Payden Pringle created issue -

              Unassigned Unassigned
              992127aa63ec Payden Pringle
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: