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

ASSIGN_ISSUE required when it should not

    XMLWordPrintable

Details

    • Bug
    • Resolution: Not a bug
    • Medium
    • None
    • 6.4
    • Java API

    Description

      During API driven issue creation using the IssueService and IssueInputParameters, when trying to workaround JRA-42827, by not setting setApplyDefaultValuesWhenParameterNotProvided(true) , JIRA is interpreting the lack of an assignee in the IIP, and the existence of a project default assignee, as requiring the Creating user to have the ASSIGN_ISSUE, resulting in _You do not have permission to assign issues and a failure to create issues.

      I think this is wrong, during creation.

      Attachments

        Issue Links

          is caused by

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-42827 IssueService IssueInputParameters setApplyDefaultValuesWhenParameterNotProvided

          • High - High priority issues
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-42609 Assignee permission check during IssueService validateUpdate uses the JIRA authentication context user not the supplied user

          • Low - Low priority issues
          • Closed

          Activity

            People

              Unassigned Unassigned
              cd3cc7134331 Andy Brook
              Votes:
              5 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: