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
we use Servicedesk Server. Our Customers can submit issues through a portal where they are registered portal users. The issues usually are only visible for the reporter and request participants (specific Jira feature) if applicable.
We want to minimize duplicate reported bug issues by giving some degree of transparency to the entirety of the registered portal users so that they can see what's already been reported.
Currently we communicate to these users through confluence posts in a section which they are subscribed to.
We already had an attempt by splitting our system with issue security schemes that we had set up to be selectable by the reporter upon issue creation. We then wanted to present a Jira filter results table on that mentioned Confluence page.
However, the external users weren't able to view that table at all. We also had to discover that the request participant functionality is fully incompatible with the use of issue security schemes.
Now my questions:
1. Is this possible at all? How?
1.1 if so: to which degree? Can only be everything public to all portal users or nothing OR can it be differentiated?
Which other pitfalls exist?
Thanks for quick reply.