Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-10891

Ability to auto assign an issue depending on value of defined custom field

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Issue - Fields
    • 2
    • 7
    • We collect Jira 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 Server. Using JIRA Cloud? See the corresponding suggestion.

      We require the ability to have an issue automatically assigned to a user based on the value of custom field. It would be useful to define this via the workflow operations so that if the custom field is left blank, or multiple selection made, the issue can be assigned to a default assignee such as the Project lead, or the component leads.

      This needs to part of Jira so that we can safely take all the upgrades tha Jira supply - it is not an option for us to implement the code provided on Jira Extension site

          Form Name

            [JRASERVER-10891] Ability to auto assign an issue depending on value of defined custom field

            Lucas Schiochet added a comment -

            Hi,

            Does anyone find a solution to use Custom Fields to auto - assign ?

            Lucas Schiochet added a comment - Hi, Does anyone find a solution to use Custom Fields to auto - assign ?

            VenugopalY added a comment -

            Hi All,

            We are looking for the same requirement. am wondering I did not seen this option in my current version 5.2.2? This is very old query.

            VenugopalY added a comment - Hi All, We are looking for the same requirement. am wondering I did not seen this option in my current version 5.2.2? This is very old query.

            Andreas added a comment -

            Voted for this.

            Our helpdesk is using Jira and would like entered Service request-issues to be automatically assigned to a role member based on a custom field where the user presents their problem type, ie Windows, VPN, Network connectivity etc.

            Andreas added a comment - Voted for this. Our helpdesk is using Jira and would like entered Service request-issues to be automatically assigned to a role member based on a custom field where the user presents their problem type, ie Windows, VPN, Network connectivity etc.

            Explorer0331 added a comment -

            The feature would be greatly beneficial for us. We plan to utilize the feature multiple ways

            => During the workflow, we plan to custom assign to a specific QA resource depending on which component the issue belongs to
            => We plan to assign it to original assignee (http://jira.atlassian.com/browse/JRA-5496) based on certain conditions
            => Change the assignee based on the issue originator (a custom-field) like Customer Support or UAT, but not initially when it is logged, but through the workflow, say moving from support teams to Development teams etc

            Explorer0331 added a comment - The feature would be greatly beneficial for us. We plan to utilize the feature multiple ways => During the workflow, we plan to custom assign to a specific QA resource depending on which component the issue belongs to => We plan to assign it to original assignee ( http://jira.atlassian.com/browse/JRA-5496 ) based on certain conditions => Change the assignee based on the issue originator (a custom-field) like Customer Support or UAT, but not initially when it is logged, but through the workflow, say moving from support teams to Development teams etc

            Adam Monty added a comment -

            This would be useful here as well. We'd like to auto-assign to custom fields called 'Developer' and 'QA' on transitions like Resolved and Reopened.

            Adam Monty added a comment - This would be useful here as well. We'd like to auto-assign to custom fields called 'Developer' and 'QA' on transitions like Resolved and Reopened.

            Jeff Fry added a comment -

            This would make a big difference for us as well. We want to be able to set a field based on component. Currently, it's a custom 'Verifier' field, but we'd be very happy to migrate that to a 'QA component lead' if that was added.

            Jeff Fry added a comment - This would make a big difference for us as well. We want to be able to set a field based on component. Currently, it's a custom 'Verifier' field, but we'd be very happy to migrate that to a 'QA component lead' if that was added.

            David Fecker added a comment -

            This looks like what we're looking for. We'd like to see auto assignment to a QA component lead on creation, to a Devloper component lead on issue acceptance, back to QA component lead on issue resolution, and a potential Developer component lead on re-open. I see the above solution fixing our problem, or possibly more than one component lead role (1 for QA and 1 for Dev)

            David Fecker added a comment - This looks like what we're looking for. We'd like to see auto assignment to a QA component lead on creation, to a Devloper component lead on issue acceptance, back to QA component lead on issue resolution, and a potential Developer component lead on re-open. I see the above solution fixing our problem, or possibly more than one component lead role (1 for QA and 1 for Dev)

            Dylan Etkin [Atlassian] added a comment -

            Hi Michael,
            This is not going to make it into JIRA 3.7. We have already solidified the feature set that is going into 3.7 and are working quite hard at getting a beta ready within the next month or two. If this improvement does make it into a release cycle then we will set the fix version of the issue. As the reporter of this issue you should receive an email notification when the status of this issue changes.
            Thanks,
            Dylan

            Dylan Etkin [Atlassian] added a comment - Hi Michael, This is not going to make it into JIRA 3.7. We have already solidified the feature set that is going into 3.7 and are working quite hard at getting a beta ready within the next month or two. If this improvement does make it into a release cycle then we will set the fix version of the issue. As the reporter of this issue you should receive an email notification when the status of this issue changes. Thanks, Dylan

            Michael Calleja added a comment -

            Hi
            Just wanted to follow up on whether this functionality was going to be included in any of the next version of Jira as standard

            Michael Calleja added a comment - Hi Just wanted to follow up on whether this functionality was going to be included in any of the next version of Jira as standard

            Michael Calleja added a comment -

            The 'Assign From Customfield Plugin' would appear to meet this requirement, however i would need this as a plugin that requires no code modification ie can it all be setup from within Jira.

            My exact requirements are as follows:
            Custom field of type Multipl-select called 'Environment' ->two available values either; Production or UAT.
            If the custom field has been populated at the time of issue created (ie new issue only) then the issue should not be autoassigned to the Project lead. If Production is chosen it shold be autoassigned to out Production support manager (me) or is UAT is chosen it should be auto assigned to the UAT/Implementation lead.

            This only needs to occur on the issues creation stage

            Michael Calleja added a comment - The 'Assign From Customfield Plugin' would appear to meet this requirement, however i would need this as a plugin that requires no code modification ie can it all be setup from within Jira. My exact requirements are as follows: Custom field of type Multipl-select called 'Environment' ->two available values either; Production or UAT. If the custom field has been populated at the time of issue created (ie new issue only) then the issue should not be autoassigned to the Project lead. If Production is chosen it shold be autoassigned to out Production support manager (me) or is UAT is chosen it should be auto assigned to the UAT/Implementation lead. This only needs to occur on the issues creation stage

              Unassigned Unassigned
              e9f15460bf7a Michael Calleja
              Votes:
              37 Vote for this issue
              Watchers:
              23 Start watching this issue

                Created:
                Updated: