Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-5291

Allow reuse of "Organizations" field for other issue types & projects

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Low Engagement
    • None
    • Customer Organisation
    • None
    • 0
    • We collect Jira Service Desk 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.

      categorizing service requests by organization of the customer in JIRA service desk is really helpful. 

      Occasionally, we need to create development tickets that are also linked to an organization. It would be incredibly helpful, if the organziations field could be used for other projects / issue types too.

      Current behavior:

      • Organizations field shows up for service request issues
      • Organzations field can be added to other issue types on other projects via admin / "add field". Field gets listed as having been added, but then the popup message appears:

      The field was added successfully, but you do not have edit permissions.

      * Consequently, the Organizations field does not show up on the issue type where it was added

      • It is not visible on the view  or edit screens, even though the "where is my field" function says that it would be present:

      The field 'Organizations' is present on the screen 'Default Screen' configured for this issue

      Desired behavior:

      Be able to use the Organizations field in all projects and issue types.

       

      Not sure if this is a bug or a suggestion...

          Form Name

            [JSDSERVER-5291] Allow reuse of "Organizations" field for other issue types & projects

            Charlie Marriott added a comment -
            Atlassian Update – 18 January 2022

            Hi,

            Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers).

            We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here, and how we prioritise what to implement here.

            To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues, and current work and future plans.

            Regards,

            Jira Service Management, Data Center & Server

            Charlie Marriott added a comment - Atlassian Update – 18 January 2022 Hi, Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers). We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here , and how we prioritise what to implement here . To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues , and current work and future plans . Regards, Jira Service Management, Data Center & Server

            Nick Gallant added a comment -

            Any updates on this? Can you confirm if it's a bug?

            Nick Gallant added a comment - Any updates on this? Can you confirm if it's a bug?

              Unassigned Unassigned
              6dd762b25a3a Jochen Neuhaus
              Votes:
              8 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: