Hi everyone,

I should have created this right when Adam told me, but I just put in this suggestion to maintain these parameters across the service desk:  https://jira.atlassian.com/browse/JSDCLOUD-9270

Feel free to vote on that one if you are interested.  We need to be able to maintain details about our customers that we already know about them as they navigate around our portals.  Huge thanks to Adam for getting us started and giving us what we have today for single request types!  Hopefully we can get this followup portion implemented to make customers lives better.

I agree, Dmitry.  That definitely is a huge bummer.  Adam Hynes implemented a wonderful change that plugged a hole in a widespread deficiency and we are truly thankful.   A true Engineer for the people.  If anyone else sees this, carry on the torch and make simple changes like this that have a huge impact.  Iterate quickly.  Listen to your power users and don't chase the things that look shiny to attract unsophisticated users (that leads to a lot of churn in customers).  I somehow missed his last message to me on March 18th and I truly appreciate the response.

It's sooo sad to see that Adam Hynes is inactive =( 
You made a great job, thanks a lot. I hope you'll see my message, bro

Hi greg.draper310998593,

Unfortunately, implementing this would require us to preserve URL parameters as a user navigates the portal. Some pages, like the My Requests page, have their own URL parameters that are used for pagination or result filtering, so we would have to make sure we don't interfere with existing parameters if we implemented this.

Because of this complication, while it's possible, implementing what you ask for would require some extra work than just preserving URL parameters across all pages. Unfortunately I won't have time to implement this myself. If you feel you need it, then go ahead and create a new Suggestion ticket.

Thanks,

Adam

Hello again, Adam.  Still very very happy with this.  Is there any way to maintain the URL parameters through navigation from the top level of a portal?

e.g.  atlassian.net/servicedesk/customer/portal/2?summary=test  will then go to atlassian.net/servicedesk/customer/portal/2/group/37?summary=test and then to atlassian.net/servicedesk/customer/portal/2/group/37/create/140?summary=test as a user clicks through the portal

Was hoping we could do that somehow to maintain values as users navigate between multiple different request types.  I know this is generally possible to do, but it is currently not setup to do this in Jira Service Desk from what I am seeing.  Thanks!

This goes to the production right away. Thank you sooo much!