Changing the way a component's Default Asignee is selected when an issue has multiple components

XMLWordPrintable

    • 1

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

      Hello

      This is what the Component's documentation states about defining a Default Assignee for a Component:

      If an issue has multiple components, and the default assignees of components clash, the assignee will be set to the default assignee of the component that is first alphabetically.

      Our users need a way to override this behavior and if the components clash when creating an issue they need the assignee to be the one corresponding to the first component they selected (not the first alphabetically).

      I can see that the database has a table called nodeassociation and it includes the relationship between JIRA issues/components. However there is no particular order on how the records are inserted in the table.

      Can this be considered as a feature in a JIRA future release?

            Assignee:
            Unassigned
            Reporter:
            Broadcom Support
            Votes:
            4 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: