We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

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

      Currently, JIRA does not support a "Lead" status within a Group. This is weird because when an issue gets to a certain state, it often has to be auto-assigned the The Guy In Charge first who will decide what to do next. (E.g. if an issue gets to "To Be Regressed", it should be assigned to QA Lead first (automatically), and then reassigned by the lead to a particular resource.)

      What would be nice to have from this standpoint is:

      • Capability to define a "Default Member" / "Lead" of a Group
      • A post-function to auto-assign issue to a Lead of specified Group (selected from a dropdown list)

      The "Assign to Group" plugin does not qualify because it requires explicitly specifying the Group Lead in transition properties which's a maintenance problem. Defining users and groups must be located entirely in User Management section, else evey time a group lead is hired/fired, the admin would have to swicth workflows (which may take up to hours if the databse is big enough) and modify every certain transition to change the user defined there.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

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

                Currently, JIRA does not support a "Lead" status within a Group. This is weird because when an issue gets to a certain state, it often has to be auto-assigned the The Guy In Charge first who will decide what to do next. (E.g. if an issue gets to "To Be Regressed", it should be assigned to QA Lead first (automatically), and then reassigned by the lead to a particular resource.)

                What would be nice to have from this standpoint is:

                • Capability to define a "Default Member" / "Lead" of a Group
                • A post-function to auto-assign issue to a Lead of specified Group (selected from a dropdown list)

                The "Assign to Group" plugin does not qualify because it requires explicitly specifying the Group Lead in transition properties which's a maintenance problem. Defining users and groups must be located entirely in User Management section, else evey time a group lead is hired/fired, the admin would have to swicth workflows (which may take up to hours if the databse is big enough) and modify every certain transition to change the user defined there.

                        Unassigned Unassigned
                        60b7eae8a171 Nikolay Gorbunov
                        Votes:
                        8 Vote for this issue
                        Watchers:
                        7 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            60b7eae8a171 Nikolay Gorbunov
                            Votes:
                            8 Vote for this issue
                            Watchers:
                            7 Start watching this issue

                              Created:
                              Updated:
                              Resolved: