Open issues

Order by Priority
  1. Suggestion
    AUTO-1712Improve scheduled trigger: Include timezone support for Cron jobs
  2. Suggestion
    AUTO-1471Automation email limits also apply to Sandboxes
  3. Suggestion
    AUTO-1699Official REST API to check the current Jira automation usage per product
  4. Suggestion
    AUTO-1769Ability to know the result of "send email" action in Automation rules
  5. Suggestion
    AUTO-1130Ability to include ticket attachments and image attachments using Send Mail function
  6. Suggestion
    AUTO-549New trigger for "Issue moved to project" and new action for "Move issue between projects"
  7. Suggestion
    AUTO-592Enterprise / admin controls for Automation - provide a specific permission for editing automation rules, option to restrict external URLs / integrations, manage which actions send emails
  8. Suggestion
    AUTO-131The Select List (cascading) field type is currently not supported in Automation for Jira for multiple operations
  9. Suggestion
    AUTO-130More ways to work with smart-values on Automation rules - ability to filter, reorder / sort, nest smart values
  10. Suggestion
    AUTO-32Rule orchestration - allow switch between parallel and sequential execution of Automation Rules, e.g. via wait/delay step
  11. Suggestion
    AUTO-2143Please consider changing the Field value changed trigger "change type" behavior
  12. Suggestion
    AUTO-602Option to suppress in-product / in-app notifications caused by Automation for Jira actions
  13. Suggestion
    AUTO-739Make it easier to work with JQL / issue search - add autocomplete or syntax suggestions, allow Lookup issues actions to look for more than 100 issues, ability to specify max number of issues
  14. Suggestion
    AUTO-187Labels not supported in automation imports/exports (exporting the Automation rule gives the ID of the labels and groups assigned to it but not the name)
  15. Suggestion
    AUTO-1129Option to export rules for a single project or based on labels selected etc (Not only all rules)
  16. Suggestion
    AUTO-971When using BusinessDays, we should be able to define the non-working days and public holidays
  17. Suggestion
    AUTO-2058Project admins are unable to update Multi-Project Automation rules (read-only)
  18. Suggestion
    AUTO-2142Ability to have smart values get Zoom Link URL of a Incident
  19. Suggestion
    AUTO-2141Ability to control add teammate to jira
  20. Suggestion
    AUTO-468Support for field IDs instead of just field names in Automation, so rules don't break when fields are renamed, and to support custom fields with the same name
  21. Suggestion
    AUTO-744Improve "Manual trigger from issue" to support more ways to capture user input - custom issue fields, user picker field type, ability to access fields via smart values, multi-select fields, date/time fields
  22. Suggestion
    AUTO-1958Improvement in audit log for typo with input/output variable when using advance component.
  23. Suggestion
    AUTO-2139Ability to use Scope based API tokens for automation rest API.
  24. Suggestion
    AUTO-2138Automation UI to filter out disabled field options for JPD when retrieving options for select or multi-select fields
  25. Suggestion
    AUTO-1370Improve sort / search / filter options on Automation Rule List
  26. Suggestion
    AUTO-108More ways to loop/branch in Automation - add While block condition, Ability to repeat/loop on a branch for a given number of times
  27. Suggestion
    AUTO-65Rule versioning / rule history for Automation - register changes made on Automation rules to support auditing and rollback/restore, and auditing of changes made to global config
  28. Suggestion
    AUTO-44Make it easier to work within Automation Service Limits, e.g. increase Daily processing time and Hourly processing time, option to reset/increase limits, show how many components a rule has, option to manage notifications of % service limit reached
  29. Suggestion
    AUTO-51Official REST API to manage rules, export/import and access automation audit logs
  30. Suggestion
    AUTO-2037Add the "Send customized email" automation component to HIPAA enabled sites
  31. Suggestion
    AUTO-1269Log meaningful information in Audit Log when Automation Rules get Rate Limited in the backend
  32. Suggestion
    AUTO-1632Include Automation Rules during the process of copying to the sandbox environment
  33. Suggestion
    AUTO-1766Add the ability to Hide Custom Data in Send Web Request Action
  34. Suggestion
    AUTO-1007More flexible/Separate billing options for Automation limits, e.g. ability to purchase automation runs as an add-on, ability to pool limits across products, minimum allowance for Premium customers with <5 users
  35. Suggestion
    AUTO-1956Block users from accessing automation if they do not have permissions to create/save rules
  36. Suggestion
    AUTO-19Ability to define a global variable or lookup table that can be used in automation
  37. Suggestion
    AUTO-1365Add support for secret storage
  38. Suggestion
    AUTO-1255Ability to split automation rules export JSON due to import limitation size
  39. Suggestion
    AUTO-2008Ability to add Service Accounts as actors for Jira & Confluence Automation
  40. Suggestion
    AUTO-455Automation support for taking actions on issues from other Jira sites/instances, e.g. support for remote issue links
  41. Suggestion
    AUTO-2136Support rendering of checkboxes in the Rich text fields via Jira Automation
  42. Suggestion
    AUTO-143Add "Automation for Jira" User to Permission Helper
  43. Suggestion
    AUTO-36Improve Automation audit log - include more info, option to include additional detail in audit logs / issue history, keep history for more than 90 days
  44. Suggestion
    AUTO-2102Allow option to hide Automation Components
  45. Suggestion
    AUTO-992Product changes may cause Automation Rules to count towards the Wrong Product Limit
  46. Suggestion
    AUTO-2135Please provide a smart Value option to Retrieve User's Location from OKTA
  47. Suggestion
    AUTO-525Support for Teams field in Automation, e.g. Company-Managed Projects
  48. Suggestion
    AUTO-76Add support for custom email domains to Send Email action, to support customising the "from" and "reply-to" addresses
  49. Suggestion
    AUTO-2066Exclude the Rovo agent's processing time from automation's service limit
  50. Suggestion
    AUTO-109Improve notifications for Automation admins - ability to select other recipients to receive notifications, notify of missing rule Owners on my site/instance, notify the user if the scheduled rule gets disabled after 10 consecutive failures
Refresh results
1 of 699
Uploaded image for project: 'Automation for Cloud'
  1. Automation for Cloud
  2. AUTO-1712

Improve scheduled trigger: Include timezone support for Cron jobs

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

    • Jira Software, Jira Service Management, Jira Work Management, Jira Product Discovery, Confluence, Bitbucket

      Problem Description

      Currently, cron jobs CRON expressions are scheduled in UTC only that has the same time all the year. UTC or GMT time are not impacted by Daylight saving changes.

      Suggested Resolution

      It would be nice if the cron jobs follow the timezone specified in the Jira instance.

      Why this is important?

      This is important as when the Daylight savings start the admins have to change the time manually every six months. Also, support team receives tickets for scheduled trigger not executing at the specified time when the DST time starts.

      Workaround (if any) 

      No workaround available as of now

            No work has yet been logged on this issue.

              Unassigned Unassigned
              615ff5e1b75f Samriddhi Saumya
              Votes:
              3 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: