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

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

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Won't Fix
    • None
    • Administration - Others
    • None
    • JIRA Standalone 3.9.2 on Ubuntu Linux, JDK 1.6.0
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      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

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-12985 Jelly doco for Create Issue tag says that default value of reporter tag is the current logged in user. But it ain't that simple.

          • Medium - Medium priority issues
          • Closed

          Suggestion - JRASERVER-25308 CreateIssueDetails URL does not fill in default value for Reporter field when user has Modify Reporter permissions

          • Gathering Interest
          relates to

          Bug - A problem which impairs or prevents the functions of the product. CONFSERVER-25405 Insert JIRA Issue does not set reporter correctly in JIRA 5.0.3 and later

          • Medium - Medium priority issues
          • Closed

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

          • Closed

          Suggestion - JRASERVER-12982 Jelly CreateIssue tag with invalid project-key attribute fails, but with a not very useful error message

          • Closed

          Activity

            People

              Unassigned Unassigned
              idaniel Ian Daniel [Atlassian]
              Votes:
              2 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: