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
Next: Root
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.
It would be useful to know where the customer sent the request from because I have set up the portal groups by identifying the various modules of the platform, eg. "Backoffice" "App Guest", "App Administrator"
thanks in advance for your help
There is no way to easily determine Portal group that an issue was raised from. However if you aren’t duplicating request types across groups then you can determine based on the request type which group it came from.
Hi, the problem is I want to use the same type request on multiple portal groups, for example:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Understood. Unfortunately you won’t be able to determine which group issue was raised from in that case. There may be some add on that provides a means of doing this but I am unfamiliar with them.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the answer @Jack Brickey
However, I don't understand the logic behind it. Why there's a "grouping" or "filtering" feature while it actually doesn't exist? What are the use cases of "Portal Groups" then?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Simply presentation to the users. I believe there are suggestions to improve the accessibility of groups in JQL.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Have you tried clicking the History button next to the Comments button?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, yes I have already tried but there is only this info:
created the IssueMay 25, 2021, 5:16 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I misunderstood, I thought you wanted to know the original request type after someone changed it.
Anyway, as @Jack Brickey said, there is no tracking that I know of for this.
The work around I suggest is to create a custom field where the user selects the group they are in, such as Backoffice, App guest and the like. This could be a Radial button that is required before the form is submitted.
If it's the same request type but different groups, I don't know how this could be automated even with the few 3rd party apps I have used/tried.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Have the same issue. Instead of having 1 "Report bug" issue and then attaching it to 5 different groups and getting some info back which portal was picked when bug has been registered, it seems I have to create 5 identical bug forms for each group.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.