Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-77046

Have the field "Log Work.authorDisplayName.accountId" available to be searched by Jira Cloud for Sheets

    • 1
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Issue Summary

      There isn't an account ID for the log work(author) field to be accessed via Jira Cloud for Sheets. The only fields available at the moment with accounts ids are:

      • Approvers.accountId,
      • Reporter.accountId,
      • Assignee.accountId and
      • Request participants.accountId

      It would be useful to have the Log Work.authorDisplayName.accountId as part of the fields available.

      Steps to Reproduce

      1. When creating a search from Jira Cloud for Sheets and setting the fields we currently don't have a field to return the Log Work.authorDisplayName.accountId

      Expected Results

      Have the Log Work.authorDisplayName.accountId as part of the fields available.

      Actual Results

      At the moment, the Log Work.authorDisplayName.accountId is not an available field when searching the field on Jira Cloud for Sheets.

      Workaround

      As the field is not available, there isn't a known workaround at the moment. 

            [JRACLOUD-77046] Have the field "Log Work.authorDisplayName.accountId" available to be searched by Jira Cloud for Sheets

            Atlassian Update - January 2024

            Hi everyone,

            Thank you for bringing this suggestion to our attention.

            As explained in our new features policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team!

            Anusha Rutnam added a comment - Atlassian Update - January 2024 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new features policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team!

              Unassigned Unassigned
              e29672569488 Ricardo N
              Votes:
              3 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: