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

XML view for filters containing user picker fields should return both userid and user full name

    XMLWordPrintable

Details

    • 32
    • 5
    • 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.

      At the moment, the XML view of a filter containing user picker custom fields only shows the user ids. For instance:

      ...
      <customfield id="customfield_10000" key="com.atlassian.jira.plugin.system.customfieldtypes:multiuserpicker">
          <customfieldname>Authors</customfieldname>
              <customfieldvalues>
                  <customfieldvalue>userone</customfieldvalue>
                  <customfieldvalue>usertwo</customfieldvalue>
              </customfieldvalues>
          </customfield>
      ...
      

      In a way, this makes sense, because the user id is the unique identifier of a user. However, there are other applications that use this information and present it to the end customer. For instance, the confluence jiraissue macro uses the XML view to present the data in the Confluence page. That results in a macro that only shows the user id, which most of the times is not meaningful to the end user.

      I would be good if the customfieldvalue could be improved to return userid, username, and user profile url, so the macro could present more meaningful view to the end user.

      Of course, this should not break backwards compatibility of the XML view.

      Attachments

        Issue Links

          Activity

            People

              klopacinski Karol Lopacinski
              dalonso Diego Alonso [Atlassian]
              Votes:
              42 Vote for this issue
              Watchers:
              36 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: