30/Apr/2025 - two years since the last update and now we are going to get a new look and feel to move the navigation to the left from the top.  Please define the issue number that is older than 9 years AND has over 1000 votes to justify making that change while ignoring this one.

Hi All! How can the customer filter by country or so if this is not an option? Please add thiiisssss. Regards.

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.

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?

Jira do something omg

This is something that was requested more than 7 years ago, 7 years! Atlassian is definitely too busy counting money, instead of working on their users' requests

Best decision we made was switching from Atlassian to another service management product. No concern for bugs or release requests from real customers.

We're going to be fully transparent without, at all, being transparent.   How do you prioritize the needs of your clients?   You only have 4 items in "future consideration" and 94 items (all bugs and alll but one rated as low priority) marked as ready for development.   How is there no time to work on your most request feature?

We are in the same boat as Anthony and many others. 

We already purchase the instance, but this kind of issues, put into consideration the renewal...

How difficult can be add at least the same option that is in server/data server versions with the toolkit? (message for edit)

Would appreciate some transparency on how that prioritization is being done, as it is pretty stunning seeing this not done immediately, let alone demoted to the backlog.  As you said, this is a daily requested item, and a really high priority one for a lot of us.  It's the single largest problem with JSM, for us (~130 paid agents, ~1000 users).  It's also the primary reason we cannot consider using JSM as a customer-facing support ticket system, and look to alternatives that offer front-end customization.

Hello everyone,

Thank you for sharing your feedback. We have evaluated this ticket and understand that this is a dearly requested feature. However, we will not be able to prioritise this at the moment as there are other items in the short term roadmap which are currently higher priority. To be as transparent as possible, I'm moving this ticket from Reviewing to Future Consideration - and will review this ticket as soon as possible.

Please check out our public roadmap for more details on the coming soon and future items.

I understand that this may be disappointing, but it’s important for us to be open, honest, and transparent with our customers. Product feedback is collected from many different sources and is evaluated when planning the product roadmap. You can learn more about our process here.

Thank you,

Alex

Jira Service Management Data Center

+1

+1

Would like this feature

+1

Would love to see this feature!

Please expedite this process.

Have a business need to add custom fields to request view for customer that are view only.

Pleae add!

When you can did it?

Very much needed for us. Thank you

Much needed for our customers as well.

Thank you.

This feature would help my customer to keep track on issues better. 

How is this not already possiable!!!

Please add this. It would be very helpful to allow customer adoption of using the portal instead of email.

Hello,

Much needed for our customers as well.

Thank you.

Hi,

Can you please add this, it is a very helpfull for Jira customers

Thank you

Can we also add 'Components' to this Requests view in the Customer Portal - our customers are using Components to distinguish multiple groups.  They can add it when creating a new ticket through the portal, but can't see it or group by it on the requests screen.  Very much needed to be more flexible in the portal.

We need this urgently for our customers.

This feature will likely not make it into the server products given Atlassian's shift to cloud.

feature requested 5+ years ago ... would be good to be considered to help the community.

please add - it is crucial for service process 

Please expedite, feature missing since long.

+1!

Please allow us to display custom fields in the customer portal as we would like to show the release version and other information for the users.

+1

Please add this function as it will help a lot.

665 votes is a lot. Please consider this!

Any predictions for this?

We have a requirement to communicate the Fix Version/s to the user on the portal.  If I add to the screen they will start adding a Fix Version/s on create.  I really don't want them trying to add this at all.  A read only field would ensure this is maintained supplier side and not customer side.

My workaround is to add the field and then clear, via a post function, following create.

Ack, how can something have hundreds of votes (clearly indicating that it's a core requirement) and not be approved and added right away?  This is more important than most of the new features on the roadmap, let's get it done.

created in 2016... any chance on a basic feature?

+1

+1

+1

+1

I agree - Sometimes certain custom fields pertain to your business or business unit and they would like to be kept informed without trawling though comment updates.

This feature would be really useful

This is indeed an issue that needs resolution. Ideally, there'd be a toggle in the Request Form view for each field (similar to Required?) that sets "visibility on portal" even as r/o.

This seems like something basic that is needed for service desk. 

Very much needed.