You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I recently got frustrated with JSDSERVER-357 and this feature request not being implemented for four year, so I've decided to hack around it.
Disclaimer: this is not a general solution, but a highly tailored to our needs.
Our customer portal is not public and I very well know each customer as they are explicitly allowed for a SD project.
Customers want to sort by columns, nothing more. I've hacked a solution using scriptrunner's REST and a userscript which loads all issues and renders a datatable - sortable, filterable, searchable.
I want to ask the community for a feedback regarding security consideration, other considerations., general feedback. Maybe you can join and help improve the "solution" and make it more general.
This is the REST groovy: https://gist.github.com/weboholic/bf5aa4f6242389033859498f11e8889f
And this is the userscript: https://gist.github.com/weboholic/e2d7d0d190bcf0839aa950dc9040b01f
Edit: this is how it looks
I have no idea. Unfortunately I cannot test it either. Just go ahead and try it out.
Made some additional improvements on the styling front. Userscript is updated. however hardcoded stuff which binds it exclusively on my use case is increasing.
I would love to have some support from the community, maybe we could together implement something more generic.
Well, it's a good solution for JIRA app-users. But for customers created through the portal, they cannot reach a custom REST-endpoint.
Unfortunately no. As I said it is currently tailored to my use case. I've shared it because they might be other people with the same use case.
- grap the jsonPayload element, which contains unparsed json data
- grab the page and load everything in the background
- prase every page's jsonPayload
- init a datatable