Was anyone able to add the Priority field at least?

37a806b7cff0  Exactly! It's frustrating to see that despite consistent user feedback, Atlassian continues to ignore key features like this one. The platform's strength lies in its flexibility and customization, but it's disappointing when basic functionality is neglected in favor of paid plugins or third-party solutions. The communication gap between Atlassian and its user base is also a concern. Regular updates on feature requests would go a long way in maintaining trust, and if certain features aren't feasible, just be transparent about it. Users are investing both time and resources into the platform, and we expect a higher level of responsiveness to critical needs like this. Otherwise, as mentioned, the current pricing structure becomes hard to justify.

Yet another feature that Atlassian is ignoring.  How much more spoon feeding can this user base provide?  18 months since the last update and over 1000 votes.  I would say that this rates high enough that it is time to do the work.  I have been watching the updates since we signed up and anything that would really impact us (like this feature) is just not being pushed out.  

You post links on how you decide but something else is having impact as well.  Nothing should sit for years with over 1000 votes.  If you are not going to do it, say so.  Also, notify your sales about what can and cannot be done without extra (paid for) plug ins.  The longer we are on Jira, the more we are discovering that Atlassian has built a system for others to solve our issues.  If that is the case, please lower the license costs across the board so that we don't have to explain why the Atlassian quote is grossly under what it is actually costing monthly to use it along with all the plug ins where we are expected to pay extra.

Hello everyone!

I have created a plugin to fix this issue
https://marketplace.atlassian.com/apps/1235179/dachas-portal-utils-screens-and-fields?hosting=datacenter&tab=overview

screenshots are here
50a951b3-dd40-4489-a5a4-af1ce969350f (2560×1600) (atlassian.com)
0d691ee4-0fda-40f2-821b-ca1b437cbaa5 (1440×900) (atlassian.com)

It just brought some features from old Jira UI to portal.
If you have any questions, please contact me.

Please can we have a response to this request. This functionality is now major blocker in our service delivery. Customers' needs to have a view of important information and are struggling to map request without it. This is causing us to have to operate out of Jira.

In our companies drive to improve the customer's experience it is becoming critical that the client has sight of important data but not be allowed to edit such (as they can make mistakes).

As the original request JSDSERVER-1107 was submitted in Nov/2014 and this request in Sep/2016 with over 1000 votes, can you not review and adjust your roadmap.

JSM is notorious for little to almost no external customer's features and we are constantly being required to pay for extra add-on apps to give our customers any information at all.
Surely Atlassian should start considering improving the customer portal to give a more rounded experience?

We have recently gone to market to review current ticketing and service management systems and Atlassian's JSM is still one of the better more affordable options out there.
We have decided to remain with JSM but the gap items between it and its competitors are becoming larger and more obvious.

And I wont even get into customer reports, which is just non-existent.

1000 votes, do we need 1000 more? 🥲

Boo this man

Time Atlassian, também estamos esperando por esata melhoria.
Será muito importante ter esta possibilidade de personalizar o Portal, isso faz muita diferença para nossos clientes

How many more votes do we need to add to this issue in order to get your attention, Atlassian?