CreateIssue without specifying reporter fails if the user has Modify Reporter privilege. This could be done better.

A Jelly CreateIssue without specifying the reporter fails, if the user has Modify Reporter privilege.

For example:

<JiraJelly xmlns:jira="jelly:com.atlassian.jira.jelly.JiraTagLib">
  <jira:CreateIssue project-key="TP" summary="Please help me" assignee="idaniel"/>
</JiraJelly>

The above Jelly script fails with the following error message:

<JiraJelly xmlns:jira='jelly:com.atlassian.jira.jelly.JiraTagLib'>
  <Error action='CreateIssueDetails'>
    <TagContents>(CreateIssue(summary=Please help me)(issuetype=3)(project-key=TP)(priority=3)(assignee=idaniel)(pid=10000))</TagContents>
    <ExecutedAs>user=idaniel</ExecutedAs>
    <ErrorMessage>
Result=input
Error for field &quot;reporter&quot; : Reporter is required.
</ErrorMessage>
  </Error>
</JiraJelly>

It succeeds if the user does not have Modify Reporter privilege.

Anton explained to me that this is because, if the user does not have Modify Reporter privilege, the only reporter that it makes sense to use if one is not specified is the logged in user. So it does that.

However, if Modify Reporter privilege is set, there are two options:
1. the current logged in user
2. an anonymous reporter

JIRA currently doesn't have the means of distinguishing between the two, so we fail with an error message.

Can we please improve this? For example, could we not have an extra attribute on the CreateIssue tag that indicated specifically that we wanted an anonymous reporter?

In the meantime, the documentation needs improving as all it says it that the default value for reporter is the currently logged in user. I will create a separate issue for this documentation task.

Cheers,
Ian