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

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

      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.

            [JRASERVER-20361] XML view for filters containing user picker fields should return both userid and user full name

            Mark Symons added a comment -

            I believe that this issue is a defect and not a suggestion and should be re-opened. I have tested that it is still relevant for JIRA v6.4.6

            As mentioned in the issue description, the omission of full name from the XML impacts display in Confluence when using JIRA Issue Macro,

            For me, this is a security issue, because it reveals usernames in PDF page exports provided to customers.

            Additionally, it's a compliance issue (of sorts) because I need to produce reports as PDF pages exports for certification organizations who demand to know the proper name of who approved test results where "Approved by" uses the "Transition Caller" field from JIRA Miscellaneous Custom Fields plugin. I can produce reports directly from JIRA itself - but the form would not be what I am seeking.

            Mark Symons added a comment - I believe that this issue is a defect and not a suggestion and should be re-opened. I have tested that it is still relevant for JIRA v6.4.6 As mentioned in the issue description, the omission of full name from the XML impacts display in Confluence when using JIRA Issue Macro, For me, this is a security issue, because it reveals usernames in PDF page exports provided to customers. Additionally, it's a compliance issue (of sorts) because I need to produce reports as PDF pages exports for certification organizations who demand to know the proper name of who approved test results where "Approved by" uses the "Transition Caller" field from JIRA Miscellaneous Custom Fields plugin. I can produce reports directly from JIRA itself - but the form would not be what I am seeking.

            Roy Krishna (Inactive) added a comment -

            We don't anticipate adding this in the foreseeable future.

            I'll close this in the mean time to keep things tidy on our end.
            If we ever look into your request again I'll be sure to reopen this issue.
            Thanks for your suggestion.

            Cheers,
            Roy

            Roy Krishna (Inactive) added a comment - We don't anticipate adding this in the foreseeable future. I'll close this in the mean time to keep things tidy on our end. If we ever look into your request again I'll be sure to reopen this issue. Thanks for your suggestion. Cheers, Roy

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

                Created:
                Updated:
                Resolved: