Atlassian Update - 21 July 2021

      Hi everyone,

      The Automatic option is now available in the assignee user picker in the new issue view. 

      Thanks

      Tha Atlassian Cloud team

      Currently, there is no "Automatic" option in assignee user picker even though there is in the old issue view.
      It would be nice to user can choose "Automatic" option like the old issue view.

      It's useful for the user who uses "components".
      https://confluence.atlassian.com/jirasoftwarecloud/organizing-work-with-components-764478279.html

            [JRACLOUD-73826] Add the "Automatic" option to assignee user picker in the new issue view

            Is auto-assignment to a component lead only a problem for manual entry from the new View screen?  I.e., does 'automatic' still work from the API?  We use an SFDC <> Jira connector that uses 'automatic' for assignee when a new bug is being filed from Salesforce.

            Dana Kreitter added a comment - Is auto-assignment to a component lead only a problem for manual entry from the new View screen?  I.e., does 'automatic' still work from the API?  We use an SFDC <> Jira connector that uses 'automatic' for assignee when a new bug is being filed from Salesforce.

            Echoing the comments of Fernando Montemayor above:  We have hundreds of users in Support and Eng who rely on auto-assignment of Jiras based on their components.  The product components are generally easy to identify based on the nature of a functional defect, but designated triagers are not only far more numerous but they vary week-to-week as well.  To not support the auto-assignment feature is to create extra work and a large delay in new issues getting to the right engineer.  

            Related:  What is the point of having a Default Assignee on the Components configuration page if the automatic assignment feature is not available?

            This issue will further delay our ability to move to the new View screen, even after the Phabricator/ external links gap is resolved.  

            Dana Kreitter added a comment - Echoing the comments of Fernando Montemayor above:  We have hundreds of users in Support and Eng who rely on auto-assignment of Jiras based on their components.  The product components are generally easy to identify based on the nature of a functional defect, but designated triagers are not only far more numerous but they vary week-to-week as well.  To not support the auto-assignment feature is to create extra work and a large delay in new issues getting to the right engineer.   Related:  What is the point of having a Default Assignee on the Components configuration page if the automatic assignment feature is not available? This issue will further delay our ability to move to the new View screen, even after the Phabricator/ external links gap is resolved.  

            Thanks for highlight this challenge in new view! Our team is looking at a range of improvement opportunities and and decided to investigate this after we started migrating people to new issue view starting March 31 2021. If this is a blocker for you to move to the new issue view, you can let us know by commenting on this page.

            Yuan Jiang added a comment - Thanks for highlight this challenge in new view! Our team is looking at a range of improvement opportunities and and decided to investigate this after we started migrating people to new issue view starting March 31 2021. If this is a blocker for you to move to the new issue view, you can let us know by commenting on this page.

            At our organization, we have a standard process for routing requests to other support teams through the use of components. A critical step in this process is changing the assignee to "Automatic" to trigger auto-assign to component leads. We heavily rely on this process in our company service desk, specifically with our applications support teams. I'm trying to get people get used to the change in issue view that was done recently but this is one of the reasons why they are reluctant to change at the moment. This is extremely important in the success of our service desk processes in our organization and it is leading to increased support times and tickets being lost in the dark.

            Fernando Montemayor added a comment - At our organization, we have a standard process for routing requests to other support teams through the use of components. A critical step in this process is changing the assignee to "Automatic" to trigger auto-assign to component leads. We heavily rely on this process in our company service desk, specifically with our applications support teams. I'm trying to get people get used to the change in issue view that was done recently but this is one of the reasons why they are reluctant to change at the moment. This is extremely important in the success of our service desk processes in our organization and it is leading to increased support times and tickets being lost in the dark.

              190b4dd3c5b7 Loretta Brunette
              jsakurai@atlassian.com J. Sakurai
              Votes:
              13 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: