• 1,352
    • 141
    • 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.

      Problem Definition

      Currently, the new JIRA issue view does not offer a way of hiding fields from third party apps.

      Suggested Solution

      Add the ability to hide these fields.

            [JRACLOUD-75009] Ability to hide third-party app fields

            Nick Christesson added a comment - - edited

            Great, no photos.

            We have tempo, on a new project and 50% of this screen is taken up by Tempo, an app that no one will use in this project. There's no way to collapse it and no way to hide it.  We have users that only log time in certain projects, but they see this in every other project. Between description and Comments.

            On the right, under the additional fields there is also the button to Log time in the collapsible box.

            There's also a button on the top in the apps section that says "Add Tempo to plan and track time"

            The issue is, we have THREE options to log time. In a project, that they aren't logging time.
            I would like the option, or let the user have the option, of hiding those

            Nick Christesson added a comment - - edited Great, no photos. We have tempo, on a new project and 50% of this screen is taken up by Tempo, an app that no one will use in this project. There's no way to collapse it and no way to hide it.  We have users that only log time in certain projects, but they see this in every other project. Between description and Comments. On the right, under the additional fields there is also the button to Log time in the collapsible box. There's also a button on the top in the apps section that says "Add Tempo to plan and track time" The issue is, we have THREE options to log time. In a project, that they aren't logging time. I would like the option, or let the user have the option, of hiding those

            It would be really useful to make us able to hide and show certain apps on view screen.

            Duzmath Lajos added a comment - It would be really useful to make us able to hide and show certain apps on view screen.

            Putting another vote on this. It's pretty wild that something like this is still a problem. 

            D'Ontre Hudson added a comment - Putting another vote on this. It's pretty wild that something like this is still a problem. 

            This would greatly improve the user experience for our non-technical teams and reduce overall clutter.

            Tyler Rountree added a comment - This would greatly improve the user experience for our non-technical teams and reduce overall clutter.

            please implement. long overdue.

            Alicia Kirkland added a comment - please implement. long overdue.

            3727d1a8d5c8 makes a very good point. Non-technical teams are overwhelmed by the custom fields related to apps they don't use that clutter the UI for Jira issues. Being able to hide any/all third-party app custom fields from a Jira project would go a long way towards helping promote Jira adoption with business teams.

            Monica Brazelton added a comment - 3727d1a8d5c8 makes a very good point. Non-technical teams are overwhelmed by the custom fields related to apps they don't use that clutter the UI for Jira issues. Being able to hide any/all third-party app custom fields from a Jira project would go a long way towards helping promote Jira adoption with business teams.

            This is the biggest thing stopping non-technical teams from using it. Pure information overload

             

            Stefan Menssink added a comment - This is the biggest thing stopping non-technical teams from using it. Pure information overload  

            You're telling me you haven dozens of comments dating back almost FOUR YEARS and you're claiming to need to "better understand the problem"? 

            That's absurd. 

            It's a simple issue. If you want your products to be used by the entire company, you have to know that not all teams will be using the same 3rd party apps. 

            Forcing the fields upon every other team in an organization that uses the service makes us not want to use your tools to the full capability. If everything I use will then be in the way for everyone else in my company, then it will not take long for that to become an unfathomable burden. 

            This is an immature response from a company like yours. Give us substance and don't pretend to be listening if you aren't. 

            If you need to "better understand the problem" then read. All of it. Look down. 

            Kevin Morelli added a comment - You're telling me you haven  dozens of comments dating back almost FOUR YEARS  and you're claiming to need to "better understand the problem"?  That's absurd.  It's a simple issue. If you want your products to be used by the entire company, you have to know that not all teams will be using the same 3rd party apps.  Forcing the fields upon every other team in an organization that uses the service makes us not want to use your tools to the full capability. If everything I use will then be  in the way for everyone else in my company, then it will not take long for that to become an unfathomable burden.  This is an immature response from a company like yours. Give us substance and don't pretend to be listening if you aren't.  If you need to "better understand the problem" then read. All of it. Look down. 

            The fields are getting more an more. 

            We need to choose 

            • on which issuetypes  or better requesttypes an app is shown
            • for which uswergroup an app is shown 
            • or to hide if there are no entries
            • etc. 

            In this example,

            • the automations can be hidden for agents and shown only for administrators
            • Smart Checklist is empty and can be hidden until an agent activates it
            • Better PDF is not needed
            • Statuspage is only used by our two incident managers and could be hidden
            • etc.

             

            Christof Hurst added a comment - The fields are getting more an more.  We need to choose  on which issuetypes  or better requesttypes an app is shown for which uswergroup an app is shown  or to hide if there are no entries etc.  In this example, the automations can be hidden for agents and shown only for administrators Smart Checklist is empty and can be hidden until an agent activates it Better PDF is not needed Statuspage is only used by our two incident managers and could be hidden etc.  

            Hey Everyone,

            Thank you for sharing your feedback on this feature request. While this feature isn’t currently on our immediate roadmap, understanding the problem in more detail will help us assess its impact and potential value. I’d love to hear about your specific use cases and challenges—feel free to book a meeting with me through my calendly link

            I encourage commenters to share screenshots or provide additional context about the issue. A clearer understanding of your workflows and pain points will help us gather the insights needed to explore meaningful solutions.

            Your input is invaluable—thank you for contributing!

            Thanks
            Ahmud 

            Ahmud Auleear added a comment - Hey Everyone, Thank you for sharing your feedback on this feature request. While this feature isn’t currently on our immediate roadmap, understanding the problem in more detail will help us assess its impact and potential value. I’d love to hear about your specific use cases and challenges—feel free to book a meeting with me through my calendly link .  I encourage commenters to share screenshots or provide additional context about the issue. A clearer understanding of your workflows and pain points will help us gather the insights needed to explore meaningful solutions. Your input is invaluable—thank you for contributing! Thanks Ahmud 

              2239430e27fb Ahmud Auleear
              dwoo@atlassian.com Daniel Woo
              Votes:
              659 Vote for this issue
              Watchers:
              319 Start watching this issue

                Created:
                Updated: