You do not have permission to assign issues

Owned by Aiden Long (Deactivated)
Sept 08, 2017
2 min read

Problem

WHY: After 5years of using the IssueManager to create issues, JEMH 1.7.x finally resolved JEMH-280 by a large internal change to use the JIRA IssueService (simply, to set most issue properties, including custom fields, and to support more custom fields in doing so, during the ISSUE_CREATION workflow step).  This change requires the use of IssueInputParameters to describe the issue fields for creation and update.  That descriptor is also used by JIRA to validate the properties, which should (in theory) reduce the redundant checking that JEMH was previously doing, however, it also means JEMH is entirely dependant on JIRA and its validation.  Despite IssueService being used for 5years there appear to be a number of cracks that are still present, some can be worked around (https://jira.atlassian.com/browse/JRA-42609) some cannot, so easily:

 WHAT: In order to create issues with JIRA default values for custom fields present, JEMH uses a method on the IssueInputParmeters to say 'hey, fill in the blanks' ( setApplyDefaultValuesWhenParameterNotProvided(true)  ) how awesome!  Yes, it does exactly that, but also causes JRA-42827, which is not awesome.  Unfortunately, NOT setting that, stops JIRA custom fields from being initialised with default values, but also introduced the You do not have permission to assign issues errors that are showing up in 1.7.13

Solution

NEXT STEPS:

In order to impact the least users, the only option I have is to revert to setApplyDefaultValuesWhenParameterNotProvided(true) which will fix You do not have permission to assign issues errors but re-break any users wanting to make use of the empty Resolution date, which affects two common cases:

  • JEMH Thread Matching limits, which uses the Resolution date (empty) to determine the issue is not resolved, outcome, new issues created all the time

  • JEMH Regexp field processor also uses the same approach when locating an issue to 'thread' to via an external system KEY, outcome, new issues created all the time.

FIXED IN: JEMH 1.7.14 will use setApplyDefaultValuesWhenParameterNotProvided(true) If you are not dependant on the Thread location, then upgrade at will, otherwise, don't, as it will create issues rather than comment.

Please vote for: