• Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • AgileBoard
    • None
    • Hide
      Atlassian Status as at 30th October 2012

      Hi All,

      The main reason for the inclusion of the auto assign feature in GreenHopper Classic is a condition in the JIRA default workflow on the transition from 'Open' to 'In Progress' that allows only the assignee to perform the transition. The auto assign feature was never a good solution to this because it will only be effective in the GreenHopper screens (in the JIRA view issue screen a user would still be unable to transition the issue without manually assigning it to themselves).

      There are two more general solutions to this problem:

      • Remove the condition on the transition so that issues can be transitioned without needing to change the assignee
      • Alter the transition so that it automatically assigns the issue to the user performing the transition

      Both of these solutions can be achieved via the JIRA workflow configuration. Some screenshots are shown in the switching to GreenHopper 6 FAQ

      Since the workflow approach is more flexible we will not be reimplementing this functionality in the Rapid Board.

      Thank you.

      Regards,
      Shaun Clowes

      Show
      Atlassian Status as at 30th October 2012 Hi All, The main reason for the inclusion of the auto assign feature in GreenHopper Classic is a condition in the JIRA default workflow on the transition from 'Open' to 'In Progress' that allows only the assignee to perform the transition. The auto assign feature was never a good solution to this because it will only be effective in the GreenHopper screens (in the JIRA view issue screen a user would still be unable to transition the issue without manually assigning it to themselves). There are two more general solutions to this problem: Remove the condition on the transition so that issues can be transitioned without needing to change the assignee Alter the transition so that it automatically assigns the issue to the user performing the transition Both of these solutions can be achieved via the JIRA workflow configuration. Some screenshots are shown in the switching to GreenHopper 6 FAQ Since the workflow approach is more flexible we will not be reimplementing this functionality in the Rapid Board. Thank you. Regards, Shaun Clowes
    • 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.

      This feature request from: JST-24762:

      Why is not auto-assign included for the rapid board? And is it planned as a functionality in the future? And if so; when?

      Workaround

      Add the "Assign the issue to the current user" Post Function in "Start Progress" transition.
      https://confluence.atlassian.com/display/JIRA/Configuring+Workflow#ConfiguringWorkflow-postfunctions

          Form Name

            [JSWSERVER-3736] Auto-assign Feature for Rapid Board

            It is also worth noting that there are some other ways to get around this problem:

            1. Use the Simplified Workflow for your project/board to enable transitions to be unrestricted and not require any further input
            2. Use keyboard shortcuts such as "i" to automatically assign an issue to yourself before transitioning

            Michael Tokar added a comment - It is also worth noting that there are some other ways to get around this problem: Use the Simplified Workflow for your project/board to enable transitions to be unrestricted and not require any further input Use keyboard shortcuts such as "i" to automatically assign an issue to yourself before transitioning

            Hi allanchow,

            thanks for the hint. That provides a nice workaround! In total I made the following changes to the workflow

            • Removed the condition that only assigned users can execute the "Start Progress" transition
            • Added the condition that the user has to be assignable
            • Added (as you mentioned) the post action, to assign the issue to the current user.

            I did that for all the major transitions.

            Andreas Ebbert-Karroum added a comment - Hi allanchow , thanks for the hint. That provides a nice workaround! In total I made the following changes to the workflow Removed the condition that only assigned users can execute the "Start Progress" transition Added the condition that the user has to be assignable Added (as you mentioned) the post action, to assign the issue to the current user. I did that for all the major transitions.

            Allan Chow added a comment -

            We resolved this by adding the "Assign the issue to the current user" Post Function in our "Start Progress" transition.

            https://confluence.atlassian.com/display/JIRA/Configuring+Workflow#ConfiguringWorkflow-postfunctions

            Allan Chow added a comment - We resolved this by adding the "Assign the issue to the current user" Post Function in our "Start Progress" transition. https://confluence.atlassian.com/display/JIRA/Configuring+Workflow#ConfiguringWorkflow-postfunctions

            I was expecting this to work and just found out that it doesn't. That's really a regression from the classic boards!

            Andreas Ebbert-Karroum added a comment - I was expecting this to work and just found out that it doesn't. That's really a regression from the classic boards!

            Any estimate on when will this be adressed?

            Álvaro Sánchez-Mariscal [Salenda] added a comment - Any estimate on when will this be adressed?

            At my company, we also have this need.
            When working in "work mode" of the "Rapid Boards", we would like auto-assign an issue on the transitions.
            For example, when the default assignee of a project is the project leader, by default, all issues are assigned to him. In work mode, if another developer wants to transition an issue, can't do it and he has to modify and self-assign the issue manually and it usability loses

            Fátima Casaú Pérez added a comment - At my company, we also have this need. When working in "work mode" of the "Rapid Boards", we would like auto-assign an issue on the transitions. For example, when the default assignee of a project is the project leader, by default, all issues are assigned to him. In work mode, if another developer wants to transition an issue, can't do it and he has to modify and self-assign the issue manually and it usability loses

              Unassigned Unassigned
              mchin Min Yee Chin [Atlassian]
              Votes:
              22 Vote for this issue
              Watchers:
              19 Start watching this issue

                Created:
                Updated:
                Resolved: