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

JIRA quick edit Assignee fails with wrong message: User ... cannot be assigned issues

    XMLWordPrintable

Details

    Description

      When there is another field in an issue that is an invalid state, quick edit fails complaining that the user is not assignable.

      This is fails, the user is assignable, and the real failure is different.

      My case: I have a select one which was None and but didn't allow None as a value.

      Please fix this as our users are raising tickets regarding broken configuration when in fact, is JIRA that is displaying the wrong messages.

      If the user would use the Edit screen, they would be able to see the real error, but obviously they do not know this.

      Attachments

        Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-69289 Password is not correctly set when deploying Jira Data Center on Azure

          • Low - Low priority issues
          • Closed
          duplicates

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-40124 Assignable Users are no longer assignable for an issue if they don't belong to the Issue Security Level permissions

          • Medium - Medium priority issues
          • Closed
          is related to

          Suggestion - JRASERVER-38134 Warn when/prevent from, assigning issue to user who does not have appropriate security level

          • Gathering Interest

          Activity

            People

              Unassigned Unassigned
              73f0b2e75f82 Sorin Sbarnea (Citrix)
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: