Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-65973

REGRESSION: Changing assignees in transition screen is taking into account the permission property of the CURRENT status, not the DESTINATION status

XMLWordPrintable

      Say you have two statuses, OPEN and START PROGRESS.
      OPEN has the jira.permission.assignable.projectrole property set to role_A.
      START PROGRESS has the jira.permission.assignable.projectrole property set to role_B.

      Transitioning from open to start progress, there is a transition screen with the Assignee field. If you try to assign to someone who is in role_B, the assign will fail with error "cannot be assigned issues". (despite the auto-complete manages to show the user as an assignable user!)

      This is not the intended behavior because in JIRA 6.3.4 or older, you can assign to a user in role_B without problems, since users in role_B matches the workflow property configured in the START PROGRESS status, which is the destination of the transition.

            [JRACLOUD-65973] REGRESSION: Changing assignees in transition screen is taking into account the permission property of the CURRENT status, not the DESTINATION status

            Dylan added a comment -

            Due to an extended period of inactivity and low interest this bug has been auto-closed. If you’re still experiencing this issue, please comment and we’ll re-open to triage.

            Cheers,

            Dylan - Service Enablement @ Atlassian

            Dylan added a comment - Due to an extended period of inactivity and low interest this bug has been auto-closed. If you’re still experiencing this issue, please comment and we’ll re-open to triage. Cheers, Dylan - Service Enablement @ Atlassian

            Matthew Hunter added a comment -

            I am indeed able to reproduce this problem in Cloud. Come see me if you want a demo.

            Matthew Hunter added a comment - I am indeed able to reproduce this problem in Cloud. Come see me if you want a demo.

            Andrew Pratt added a comment - - edited

            Still broke in our instance.

            We are using jira.permission.assignable.projectrole.1 and jira.permission.assignable.projectrole.2 and ...3 to limit the assignable users to members of one of 3 different project roles. i.e role_B, role_C and *role_D

            One thing I note in the description that is different from the issue in our instance is the "auto-complete doesn't show the user as an assignable user. That is, it doesn't show any of the users in role_C.

            Hope that helps.

            I'm going to have to put my workaround back in for my users.

            Andrew

            Andrew Pratt added a comment - - edited Still broke in our instance. We are using jira.permission.assignable.projectrole.1 and jira.permission.assignable.projectrole.2 and ...3 to limit the assignable users to members of one of 3 different project roles. i.e role_B , role_C and *role_D One thing I note in the description that is different from the issue in our instance is the "auto-complete doesn't show the user as an assignable user. That is, it doesn't show any of the users in role_C . Hope that helps. I'm going to have to put my workaround back in for my users. Andrew

            Andrew Pratt added a comment -

            I'll go back to our instance where I saw the issue (re-reported in JST-113456) and see if I can see it there.

            We were running 7.0.0-OD-01-193 when it showed up on Aug 17. Now up to 7.0.0-OD-02-247 so perhaps magic happened.

            Andrew

            Andrew Pratt added a comment - I'll go back to our instance where I saw the issue (re-reported in JST-113456) and see if I can see it there. We were running 7.0.0-OD-01-193 when it showed up on Aug 17. Now up to 7.0.0-OD-02-247 so perhaps magic happened. Andrew

            Oswaldo Hernandez (Inactive) added a comment -

            Hi dleng jsanchez@atlassian.com has tried to reproduce this and it was not possible.

            Cheers,
            Os.

            Oswaldo Hernandez (Inactive) added a comment - Hi dleng jsanchez@atlassian.com has tried to reproduce this and it was not possible. Cheers, Os.

              sjaju@atlassian.com Shubham Jaju
              dleng Daniel Leng (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: