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 am investigating a solution design regarding the following problem:
I have a JIRA Service Desk instance running. I have some Customers tracking specific Tasks. Therefor they have Customer Accounts.
Now, I have these Tasks and I want to provide tasks to the public, so that everyone can assign themselves as a PLAYER to that specific task. It is not necessarily the "assigning" itself but I want to create the possibility, that people from all over the world can access these tasks via a website/App and transition them from open to done. I do not want to have a dedicated account management there, but I wanna have the Accounts generally managed by JIRA.
Inbetween these two Groups, there is a set of Agents, evaluating the tasks one by one and approving them.
I was thinking about one-Agent-license-per Player. But this makes the whole concept worthles, because I would need to pay Agent-Licenses 'til the end of my days.
I also thought about having one Agent-Account for ALL the players and transferring the account details via JSON - but then I would need to have some additional Account management, stored in a separate database, etc. etc.
Do you have any ideas, how to solve this?