• 9
    • 13
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.

      I would love to see an automation "THEN" function that allows specific fields to be edited as part of the automation process. Our customer workflow involves specific agents being assigned to specific customers. One example of how this feature would help would be if we could establish a rule that says "Upon creation, if reporter = customerXYZ, then edit "Agent" custom field to = "John Doe".

            [JSDSERVER-2015] Automation to edit issue fields using defined values

            Hello Server Customers,

            Good news - We have improved the Edit Field in Automation and made it more powerful. We have extended the list of fields you can edit to include Jira Custom fields.

            To find out more about this feature, check out our documentation here:

            https://confluence.atlassian.com/servicedesk/jira-service-desk-4-2-x-release-notes-967877779.html

            On behalf of JSD team, I want to thank you all for contributing to this ticket. Your comments, feedback and interviews have helped shape this feature.

             

            Ritesh Ranjan
            Product Manager, Jira Service Desk

            Ritesh Ranjan (Inactive) added a comment - Hello Server Customers, Good news - We have improved the Edit Field in Automation and made it more powerful. We have extended the list of fields you can edit to include Jira Custom fields. To find out more about this feature, check out our documentation here: https://confluence.atlassian.com/servicedesk/jira-service-desk-4-2-x-release-notes-967877779.html On behalf of JSD team, I want to thank you all for contributing to this ticket. Your comments, feedback and interviews have helped shape this feature.   Ritesh Ranjan Product Manager, Jira Service Desk

            Check out our free app which enables you to do this (Server only) - https://marketplace.atlassian.com/apps/1219584/edit-field-automation-for-jsd

            Nigel Rochford added a comment - Check out our free app which enables you to do this (Server only) - https://marketplace.atlassian.com/apps/1219584/edit-field-automation-for-jsd

            Depending on the priority and the component of the issue I would like to set a custom field which then can be used for selecting the right SLA. The only work-around so far is to create a post function. But since the automation rules exist, it would be much easier to use them instead of a script.

            Manuel Bähnisch added a comment - Depending on the priority and the component of the issue I would like to set a custom field which then can be used for selecting the right SLA. The only work-around so far is to create a post function. But since the automation rules exist, it would be much easier to use them instead of a script.

            Another use case. Allow an agent to take ownership of a ticket by responding to an email with specific text in the comment ie. replying with to an email with the string "I am taking ownership" will change the assignee to the sender of the email.

            Andrew Laden added a comment - Another use case. Allow an agent to take ownership of a ticket by responding to an email with specific text in the comment ie. replying with to an email with the string "I am taking ownership" will change the assignee to the sender of the email.

            We need this feature to prioritize alerts sent in to JIRA by our monitoring system (via email). Right now, we do it by checking the reporter (monitoring system) and then applying a request type. This is a problem because we can't hide request types for certain groups ( a la JSD-3665). We need to be able to set the priority of the issue rather than be limited by the current selections.

            Roger Birong added a comment - We need this feature to prioritize alerts sent in to JIRA by our monitoring system (via email). Right now, we do it by checking the reporter (monitoring system) and then applying a request type. This is a problem because we can't hide request types for certain groups ( a la JSD-3665 ). We need to be able to set the priority of the issue rather than be limited by the current selections.

              rranjan2 Ritesh Ranjan (Inactive)
              fbdfaea22dc7 Danny Coleman
              Votes:
              46 Vote for this issue
              Watchers:
              32 Start watching this issue

                Created:
                Updated:
                Resolved: